I thought you're looking for a wallet where you can send your BSV? (the quoted part)
So, one of the safest option is to also send it to your Ledger, the will-be-created wallet in ElectrumSV will only work as an interface for the Hardware wallet.

You can also use your Ledger Nano, not using Ledger Live but ElectrumSV.
Ledger has an article about it in their support page: https://support.ledger.com/hc/en-us/articles/360012270054-Bitcoin-SV-BSV-?docs=true

Bitcoin SV first since you've already claimed your BCH from the fork.

Reason is BSV has no "replay protection" and attacker might use your previous BCH transaction to send it to the same recipient in the BSV network.
Anyways, if the recipient is also you and it's sent to a non-custodial wallet, then there's no major threat concerning that.
Bitcoin Gold in the other hand, has replay protection so, you can send it last.

Looks like you missed my reply in the first page (post #20) since you only replied to Bob's post.

To expand it, it's showing that your cmd is currently working in "C:\Users\Raini" which is the default cmd directory if you launch it using start or hotkeys.
It should be working in the directory where Bitcoin-qt.exe is located or indicate the absolute path when launching bitcoin-qt.

I don't have "Remitano" and there's no documentation about viewing the address list,
but there's should be a list of your previous deposit addresses since it's stated in their support page that "all are your wallet addresses".

What happens when you click "Dashboard->Wallets", then the (triple dots) menu of your Bitcoin wallet?
If there's an option to view your previous addresses, then there it is.

I could also be your connection to the Lightning Network, Electrum takes time to fully connect if you're not using "Trampoline Routing" in the setting.
You can check the progress by clicking the yellow lightning icon at the lower-right hand side.

I think you just forgot to point command prompt to the correct directory before executing the command.
cmd should be working in "C:\Program Files\Bitcoin" if you're using the default installation directory.

What do you mean? A customer service representative?
If it's support, he already got the best solutions in this thread, be it 'to export the keys' or 'to fully sync core', they've already got it covered.

It's just OP didn't responded and looks like he prematurely gave up in his last reply:
(I think he doesn't really got a wallet.dat file but the renamed "wallet" source code of Bitcoin Core)

The archived page of blockchian(dot)info from January 2014 recommended a 10-character password,
When you start to type it, it'll display how strong or weak your current password is; but there's no restriction in using only alpha-numeric characters.

Archived Link: web.archive.org/web/20140122233151/https://blockchain.info/wallet/new

If you exactly followed my instructions, the wallet will not be watching-only since it's the private key that you've imported.
If you pasted the address, it will be a watching only wallet since it' just an address which is already public.

You can check the title bar of Electrum to see what type of wallet it is, e.g: [standard, watching-only], [imported] or [imported, watching only]
If it says [imported] and the balance is there, then you can now use that wallet to spend the funds.

The 51 characters that starts with 'L' looks promising but it should be 52 characters.
The other can't be a WIF private key nor a ECDSA private keys simply because of the starting character.

BTW, since your address starts with '3', you need to add "p2wpkh-p2sh:" in front of the private key when importing to Electrum,
example:
Without it, Electrum will derive legacy address that starts with '1' instead.

That's called a bech32 Bitcoin address, aka "Native SegWit Address".
Aside from that, there are other Bitcoin address format, namely: legacy [P2PKH]: starts with "1" | and various scripts (can be Nested SegWit, MultiSig, etc.) [P2SH]: Starts with "3".

We do not need the actual address (for your privacy) and definitely not its private key, the info we need is the type of wallet/tool where it came from.

Here's the thing, the only way to spend it is to create another Electrum wallet using the menu:
"File->New/Restore", type a new wallet name, next; select "Import bitcoin addresses or private keys", then paste the address' 'private key' if you have it.
Finish the rest of the steps.

Private key starts with '5', 'K' or "L', without it, you wont be able to spend the coins from your watching-only wallet.
If you've used a tool to create the address, it should come with a private key.
If it came from a non-custodial wallet/service, there should be an option to export its private key, or spend it using that wallet instead.

Take note that Armory is currently only capable of exporting WIF private key in uncompressed format.
So if you ever need to export the addresses' keys, you'll have to encode the ECDSA key (HEX) into compressed WIF format for it to be compatible with other wallets.
Don't worry, it uses the compressed public key to generate the nested SegWit addresses so there wont be any issue when spending funds.

Anyways, it's the best option for now since Armory 0.96.5 can't generate "Native SegWit" and Taproot addresses.

The wallet is indeed legit,
But you missed the fact that a 'watching only' wallet is "watching only", means that you'll never be able to spend the funds you've sent to it.

You've been asked where did the address(es) you've used to create the watch-only wallet came from, but you seem be dodging the question.
Unfortunately, that's the only vital information to be able to tell if you have a chance to spent those funds.

FYI, Bitcoin has no central authority that you can contact to intermediate with the funds.

No, there's no private key in your default wallet.

That is totally normal for a watching-only wallet.
In the private key menu, there's no "import" option because you cannot add a private key to a wallet with only addresses in it (it is available for imported wallets).
You can only "sweep" because you can still send bitcoins to those imported addresses (but you cannot spend them using that wallet).
'Sweep' sends the pasted private key's entire balance to one of the wallet's address so it's available for all wallet types including watching only.
Lastly, "export" should be grayed-out too because there are no keys in that wallet.

The "named wallet" doesn't display the same transactions so I take that the keys for your default wallet aren't there.

That's a good news if the source of the address isn't an exchange, custodial service or some wallet with undisclosed non-standard derivation path.
Depending on where you got it, you may be able to spend those funds.

One important note when backing up using that method:
Make sure Bitcoin Core isn't running when copying the wallet.dat file because you might backup a corrupted copy (by a low chance).

That guide shouldn't be followed since it's not the correct way to set-up a MultiSig Electrum wallet using hardware devices.
But you already did and here we are.

The users don't need to create a standard wallet in order to get the hardware wallet's xpubs (master public key).
During the creation process, each cosigners should start creating a MultiSig wallet right from the start until the point when they'll be presented with their "Master Public Key".
Then send it to other cosigners (as that cosigner receive theirs) to finish their own MultiSig wallets.

"Descriptor Wallet" is just the new wallet type consisting of 'output descriptors' instead of private keys (aside from the master key),
it's still named 'wallet.dat'.

@SamuelDL  If you set a name for that descriptor wallet and it was created by the later version, the wallet.dat should be in the folder with the same name as that descriptor wallet.
Alternatively, in QT, just use "File->Backup Wallet" while that wallet is selected in the drop-down menu (if multiple wallets are open).

That happens to me most of the time.
After closing Armory-qt, there's always a lingering process of ArmoryDB.exe left in the Task Manager.

Maybe.
There's a chance that Bitcoin Core failed to scan the correct balance and kept the spent inputs in your wallet.
I've seen a couple of topics regarding that, usually those who replaced the wallet.dat file.

BTW, what error did you get when you tried to broadcast the transaction(s) via console?

In case you missed it:
Alternatively, if you want to send them no more: use testmempoolaccept instead.
e.g.:

---

Lastly, if it's just because of the "frequent wallet replacement", rescan might do the trick; open console, select the correct wallet: rescanblockchain