That's very risky! You should make a backup of the wallet file and save it in a flash drive, the easiest way (if it's GUI and running) is to use "File->Backup Wallet...";
If you're using bitcoin-cli: use backupwallet command.
If Bitcoin core isn't running, you can copy the wallet.dat file from the data directory.

Just make sure to save the backup file to a safe location, not any online/cloud storage.
Eg.: to a flash drive and store it in your safe or any safe location, and do not plug it if not needed.

---

Memory? You mean disk space?
So I think Bitcoin core automatically set it to prune since you have little disk space left; that left "rescan" out of your options for now.

After you bought your new PC, make sure that bitcoin core isn't set to prune the blockchain.
For the GUI, you can see the setting in "Settings->Options...->Prune block storage to", make sure that it's unchecked.
And to speed-up initial sync, you can increase "Size of database cache" to 1GB+ depending on how much RAM you want it to use.

I mean, if you have a backup of the wallet.dat from the old version, make a copy of it and do what I've instructed to the copy.
Not the wallet.dat that you've loaded to the latest Bitcoin core or other software like 'BTC Recover' if you used it.
That's is to check what's actually in the wallet since you've mentioned that it turned out with zero balance after the rescan.

For the rescan that started from 155,564 height, AFAIK, it will start from what's remembered by the wallet file, the last block since it was active.
You can force it to rescan from scratch using the command: rescanblockchain in the console (Window->Console) of GUI or through bitcoin-cli.
But make sure that your blockchain isn't pruned. That will take hours, BTW.

Yes, that's what the first part of my reply is all about: there's a client with freeze feature but it doesn't fit OP's use-case.

You can upload the images to imgur and link them here.
(wont be displayed as image for newbie accounts, just link)

For the wallet.dat file, you can just open a "virgin copy" of it using a good text editor and search (CTRL+F) for:
The next string should be an address, then check a multi-blockexplorer (eg.: https://blockchair.com/) to see if the results have bitcoins/altcoins.

---

Virgin copy: make a copy of the original file, not the ones already opened by Bitcoin core or any software.

Lastly, if the wallet file was bought, it's a scam.

Electrum has that function; but it's more of a "coin-control" feature than safety.
Because it's possible client side - freeze an address or UTXO from being spent (though that client) but it wont stop anyone who already got your private keys from spending your coins.

I don't think it's possible to freeze coins in the blockchain unless those are locked using a script that can be frozen/unfrozen any time which I don't think we have (please inform me if there's one).

That (the second suggestion) will work even if the transactions are weeks apart.

It happens because the description in the previous invoice concatenates with the new one if the "pay to" address is the same.
By deleting the previous invoice before proceeding to the next, the new transaction wont include the previous' description.

Note: If you already sent the transaction, now unconfirmed/confirmed in the 'history' tab, it's okay to delete the invoices in the 'send' tab.
The 'invoices' are the "send queue" below the send tab.

Check this if you've missed the first step: https://electrum.readthedocs.io/en/latest/gpg-check.html
I think the download page only shows the command for users who already have ThomasV's public key.

This is one of the hardcoded trampoline node for users who want to open a channel with "trampoline routing".

I can confirm this because it has the same NodeID as my channel's "Remote Node ID":

That's because SLIP39's "Master Secret" is equivalent to BIP39's "BIP39 seed" (below passphrase).
I don't know what's the motivation in using "0039" though, maybe because it's intended to replace BIP39.

In BIP39, the 'entropy' is used to generate the 'mnemonic sentence' (seed phrase), then the 'binary seed' (seed) is generated from the mnemonic sentence - (learmebitcoin - BIP39)
while in SLIP39, the 'binary seed' itself is used to generate the mnemonic sentences (slip-0039).

Now in iancoleman's tool, try to paste BIP39's "BIP39 seed" to SLIP39's "Master Secret" and it should generate the same set of addresses when restored.

He was talking about the old login option for blockchain.info, an "alias" instead of the WalletID.
Details are in the earlier replies.

Next time, please read some of the replies and the date when it was posted before replying.

I've tried it and it works as you described, however, it requires the signature itself when you need to sign the transaction.
For the supported hardware wallet cosigners, there will be no troubles.

If Electrum is required to sign the transaction (eg. for non-hardware wallet cosigner with Electrum seed):
You can select the method "Coldcard" so you can export a ".psbt" file that's supported by Electrum ("Download PSBT" button).
In Electrum, use "Tools->Load Transaction->from file", load and sign it.
Export to file and upload back to the tool if it requires more signatures or if you need to broadcast.

There's a workaround but it's not newbie friendly.

@AndresAA90 Yes, but you have to load the RAW transactions manually to Electrum so that you can use them as inputs to create a transaction while offline.
The tiring part is finding your wallet's unspent outputs (if you have many) and the troublesome part is getting their "RAW transaction" data.

He's an example workflow (some steps can be done in variety of ways):

• Let's say Electrum is offline, so when you restored your wallets the transaction history is empty.
• Now, enable "Address" and "Console" tab, you need to generate more addresses to a quantity based from your past transaction history.
  So, in the 'console' tab, type [wallet.create_new_address(False) for i in range(100)] and [wallet.create_new_address(True) for i in range(50)]
  The former is for your "receiving addresses" and the later is for the "change addresses", change 100 and 50 depending on how many addresses you think you've used.
• Go to Address tab and find a way to check the addresses' balances (eg. a blockexplorer), then take note of the TXIDs that contain your addresses as output that's still unspent.
• Find a way to get the "RAW Transaction" of the TXIDs that you've noted, (one example is to use a service like https://chainquery.com/bitcoin-cli/getrawtransaction)
• Back to Electrum, use the menu: "Tools->Load Transaction from text", paste one RAW transaction, click "Load" and then "Save"
  Note: "Save" wont be available if the transaction isn't related to the wallet or the address isn't generated yet; if it's the latter: generate more addresses.
  Do that to all of the RAW Transactions in your note one by one.
• Lastly you can now create an offline transaction and broadcast it using other wallets/service.
  If it's rejected when broadcast, you must have likely included a "spent output" in the mix (remove it/those from the history and create a transaction again).

Did all three the payments merged into one transaction?
Because that will happen if "Batch RBF transaction" and "Use replace-by-fee" are enabled in the settings,
then you created the second and third transactions while the others are still unconfirmed.

If not, and just the 'descriptions', you can use this workaround:

• After sending the first transaction, delete its associated invoice from the 'send' tab, then send the second transaction.
• Repeat what you just did for the third transaction.

---

For the already-created transactions, just edit their descriptions in the 'history' tab.

Can only import
Just like BIP39 seed phrase, Electrum can import but can't produce SLIP39 seed phrases.

That's the same directory posted in your reply, that shortcut will enable him to go there without changing the 'hidden folder' view setting.
If there'll be a warning, it will also pop-up upon manually browsing to the directory.

You should paste your logs to pastebin so users could see the possible issue.
You can delete the parts that you don't want to share like windows profile name from the default data directory.

Your logs is the file named "armorylog.txt" in Armory's data directory.

Thanks, without looking at the code, my initial guess was: it's because of the checksum: SHA256(mini-privKey + ?) =  0x00 first byte; and it includes the "p2pkh:" to hash.
Pretty close but it's the last (third) 'condition'.

So they've also included to check for "S" as the first character of what's actually pasted there.

That's when "advanced preview" in the setting is enabled or you've clicked "advanced" when creating a transaction.
By default, you don't have to go through those steps.

1 confirmation means that it's already included in a block, you can now spend it.
The consecutive confirmations are just for safety against double-spend attacks (not that it's usual), the higher the confirmation the safer your bitcoins are;
it'll take approximately 10minutes per confirmation.

But wait, you haven't read my other reply (don't you?),
figures because there's one confirmation, means that you've swept (sweep) it.
But there's no major issue as long as the recipient wallet isn't a "watching-only" wallet and you own the wallet where it was swept.
(the post also has some suggestions for the safety of your funds)

Yes there is.
In your data directory, there's a file named "debug.log", that's the log file.

Windows 10 - Bitcoin Core's default data directory is in: %appdata%/bitcoin
Appdata= Click 'Search' or 'Run' (WinKey+R), type %appdata% then press enter.