Password error / can't open XML / beginner issue

[humblenewbie]

I can't seem to type the password. I keep getting this message:
Password: error: unable to open output file: open backup.xml: Access is denied.

• Operating system: Windows 10 Pro
• Build version (signal-back --version): v0.1.7-alpha.2

Detailed description

Hi,

I would very much appreciate getting this to work. I am brand new to Github... hope you can help me out. It might be very basic, what I'm doing wrong.

I have my backup file, signal-2020-02-17-18-24-50.backup and signal-back_windows_amd64.exe in the same folder.

I hold shift and right-click in the folder and choose Open PowerShell window here
In the PowerShell window I type signal-back_windows_amd64.exe format -f XML -o backup.xml signal-2020-02-17-18-24-50.backup

I then get a line with this text:
Suggestion [3,General]: (...) If you trust this command, instead type: ".\signal-back_windows_amd64.exe". See "get-help about_Command_Precedence" for more details.

I follow the suggestion and instead type:
.\signal-back_windows_amd64.exe format -f XML -o backup.xml signal-2020-02-17-18-24-50.backup

I then get a Password: line but it doesn't respond to any inputs (*** stars or numbers don't show up when I type numbers). I try typing in my encryption key anyway but I always get the same response:
Password: error: unable to open output file: open backup.xml: Access is denied.

I tried typing in the 6x5 digit encryption key without spaces and with a single space in between each digit group.

Full relevant output

[pshem]

• Password characters will NOT appear in a secure command line input. Type the password in the prompt(after Password: ) and press enter. If you got it right, it'll work
• You can also decrypt the backup by passing the password in the invocation line, with --password '00000 00000 00000 0000'. Spaces are optional, single quotes are a good habit to make sure the program treats your password as a single argument
• However, your error seems like a file access problem - you might not have the right to write files in the location you're in. Or possibly the backup.xml file in that directory already exists and PowerShell is trying to protect you from overwriting it, so you should try calling the output file backup2.xml instead