So the cold machine is set to prune the blockchain in the first place.
Then since you set the hot machine to prune too, both machine work since nothing's different in the settings and contents of the datadir.

The downside is you'll never be able to load other wallet, otherwise you'll have to re-download the blockchain.

Ah, so it's you who spent it and it's successful in your last attempt.
Congrats.

You found the reason why it needed to re-download the blockchain.
Forgot to mention that prune setting is on by default and you said that you are in default settings, so if you haven't unchecked it in the welcome screen/settings, it must be on.
That setting will delete the older blocks until the set size has reached to save disk space.

The coin that you're trying to spend was already spent (just a few minutes ago): f6191eb2d49ae95ad4ca329aa928bc6eec625e95a668ff01b5e138cd6c460e54:0

If the file above doesn't work, get the 32-bit Windows binaries from the outdated armory website bitcoinarmory.com (but from its older version)

Link: https://web.archive.org/web/20130917140922/http://bitcoinarmory.com/download/ (click Windows icon, then "code.google.com download page").
It will redirect you to this archived page: https://web.archive.org/web/20130814045236/http://code.google.com/p/bitcoinarmory/downloads/list
The download links there are still working but it's archived by a third-party so I can't comment on the integrity of the files.

The simpler method is to just move the decimal point depending on the value of "e+number".

From your example:

	1.055	(e+06 = move by 6 decimal places)
	10.55	=  move by 1 place
	105.5	=  move by 2 places
	1055.	=  move by 3 places
	10550.	=  move by 4 places
	105500.	=  move by 5 places
	1055000.	=  move by 6 places

---

Other note: You can use your forum signature for off-topic messages.
You can access it in: "Profile->Forum Profile Information".

So the custom data directory was set in the GUI's "welcome screen" and no other settings are set.
Removing the wallet file shouldn't cause your node to re-download the blockchain,
so I think something is corrupted in the process of unplugging/transferring/plugging of the external SSD.

IDK what Cold-storage setup you are using that requires the blockchain in the cold-wallet,
but I'd also recommend you to just use the "cold machine" for signing purposes only, it doesn't need to sync to the network.

Since they are the one who'll co-sign the transaction for you, they should have a "master private key" in their server that's a pair of the "master public key" in your 2fa wallet.
It's unique to each TrustedCoin account (you register as you create the 2fa wallet).

trustedcoin.py: https://github.com/spesmilo/electrum/blob/master/electrum/plugins/trustedcoin/trustedcoin.py#L72-L77

It shouldn't do that if the datadir has the same path and files as before.
Have you properly closed Bitcoin Core in the Cold machine before unplugging the USB Disk? Because it should be.

Some questions:

• Are you using a bitcoin.conf file? If so, What did you set?
• Are you using any additional start parameters?
• If you're using Bitcoin-qt (GUI), what are the options that are ticked in the Settings?

If you do that, remove "settings.json" file as well so you wont get the "wallet path doesn't exist" error.

So you'll trust anything that they'll ask you, even your private keys?

Since you haven't explained the situation, most people will just assist you on the exact thing that you're asking even though it's not the best way to solve the issue.
Because with the current info, I see the whole "sign a transaction to get your money back" situation "weird" (as I explained in my previous reply).

It' would be nice if you can write the steps that you've done in order to import the funds to Electrum. (for others who are searching the web and to sum-up this thread)
Because a watching-only wallet doesn't have any keys that can be exported to another wallet.

BTW, the screenshot link doesn't work, you need to get the link from the image itself and not your imgur profile link.

You can use coinb.in's multisig tool to re-create the MultiSig address: coinb.in/#newMultiSig
Use "New->Transaction" to create a transaction using the redeem script; then the "Sign" tab to sign the RAW Transaction.
However, it only supports P2SH and not P2WSH (SegWit).

I'd recommend to use it offline during the part when you need to paste the private keys (e.g. when signing the transaction).
Run from the source: https://github.com/OutCast3k/coinbin/

---

But something tells me that you have the "master private keys" (Yprv / Zprv) instead of "private keys".
In which case, you'll have to get the address' private keys from the master keys first to be able to sign it (will add a few extra steps).
If not disregard this part.

Mine shows the full address after I pasted it; and just like larry, just the first and last 4 characters in the confirmation window.
Metamask version 10.10.1 | Monitor's resolution: 1920x1080 px
Images (test network):

	Send Window		Confirmation Window

Anyways, I think it's time to create another thread to continue the discussion about MetaMask.

Or they can use -blocksdir as a start parameter or in the config file (for those who can't/wont use symlink).
That will basically do the same, Bitcoin will use the default data directory for the chainstate and other data except the blockchain which will be saved in the specified blocks directory.

https://github.com/bitcoin/bitcoin/blob/master/src/init.cpp#L401

Ah, so they aren't looking for a signed message to confirm that you're the sender like the SOP for refunds (OP sounds like that).
The OP is vague, but the new reply has some inconsistencies because why would they need you to sign a transaction for them to return your money back?

The question is: who's "they"?
And please describe your goal/issue better since this turned out to be an "XY problem".

---

Anyways, you don't have to export any private key to sign a transaction.
Just load the unsigned transaction as described by pooya "Tools->Load transaction":
Click "Tools", point at "Load Transaction"; then select "From file" or "From text" depending on the format of the transaction that you need to sign.

Those versions are too old and wont be able to connect to the network.
If you need the binaries, try this: /index.php?topic=68121.0 (v0.1) | Read the latest replies for more info.
Or from the old commits: github.com/bitcoin/bitcoin/commits/master?before=25.... (before September 2011; click "<>" to view the repo's state at that time)

Reference for the Berkeley Database version upgrade: https://bitcoin.stackexchange.com/a/81583

Unfortunately, you can't sign a message with your 2-of-3 MultiSig address;
there's also a note that will pop-up if you try to sign a message using your multisig wallet:

---

What you can do is to explain them that it's a Multisig address and it's impossible to comply with their request.
Try to find alternative ways (ask them what they need aside from a signed message).

I missed this reply (posted 19sec before mine).
Then limiting your dbcache to reduce the 'page file' wont really do much because the data directory isn't in the same drive where the 'page file' will be.

"Internal" means that the HDD is inside the PC, while "External" is connected via USB or other external ports.

That's quite a low number of peers but 5 shouldn't be limiting the speed to 0.07%/hr so it must be the HDD or something else.
What I'm thinking is your RAM must not be enough for the dbcache that you've set together with the background processes of Windows10
That will use a lot of "page files" which will further stress your HDD.

Try to reduce your database cache into 512 instead (or lower); then, restart Bitcoin Core and check if it'll improve.

That's indeed slow considering the internet speed and it's a quite capable machine.
However, the most important factor to the initial block download's speed is the Drive which you haven't mentioned.
So, are you using an HDD/SSD, internal or external?

It can also be affected by your connection to the network, How many peers do you have in "Window->Peers"?

I can only guess based from Bitcoin Core's behavior in generating the keypool.

Those timestamps are date & time of each individual keys in your wallet.dat.
Upon creation of the wallet, it will immediately preload thousands of keys for receiving and change addresses to the wallet.dat,
Thus, all those keys' timestamp should be the similar (may differ in a few seconds) so your hypothesis may be correct about the "timestamp" of the unencrypted wallet.

After setting a passphrase, Core will drop the unused keys from the wallet, create a new 'HDSeed' and derive a new keypool from it.
Thus, the new keypool has an updated timestamp based from when the wallet is encrypted;
However, if you just changed the passphrase of an already-encrypted wallet, the 'HDSeed' will remain the same so the timestamp will stay the same for the already-derived keys.

Signing a transaction doesn't require the wallet to be connected, in fact it can be done in an Air-Gap computer.

I'm thinking that it may be more of a hardware wallet issue than Electrum's since it's the Ledger that can't sign.