It may be an issue with the cache...
Try to clear Ledger Live cache to update its balance, follow this tutorial: support.ledger.com/hc/en-us/articles/4404381846929-Clear-cache-in-Ledger-Live

You may be looking at the fiat-equivalent amount since Bitcoin's price today is 2-3x its price 3 years ago (depending on the month).
Or are you talking about the balance in BTC?

Are you using the portable version?
If so and if you're using a flash drive (USB stick), it's permanently deleted because deleted files from flash drives wont be saved to recycle bin.
In that case, do not use the flash drive at the moment since you may be able to restore it using various file restoration tools.

You've switched to Electrum but this is never mentioned here, so it's worth mentioning:
The 3-dots menu will not show if the Android device itself has a physical menu button.
In that case, pressing the physical menu button will trigger the same menu as the 3-dots menu.

If it's not showing despite having no physical menu button,
then it's either an error in the app's part, android phone's firmware or combination of both.

Pathing guide says it's "e:\bitcoin\blocks" but "e:\bitcoin" works fine at my end.

Regarding the logs:
If you've set satoshi directory through the UI, "Satoshi BTC directory" will register in the logs as the default but it will launch armorydb with the set path anyways.
You can see it in the line - "ArmoryQt.py:1891 - Setting satoshi datadir = E:\bitcoin" and below it showing that it's included as a start parameter of armorydb.
If you set it using the config file, the correct "Satoshi BTC directory" should be in the log.
Either one should work (I haven't tried if both are set though).

Now, I think you just need to restart your PC in every attempt since most of the time, armorydb will stay running in the background after closing armoryqt keeping the old settings with it.
Alternatively, open "task manager", find armorydb and if it's still there, end its process.

"Descriptor" wallets do not support those commands.
Instead, it only allows the export of "parent descriptors" which contains either the master public or master private key.

@FullMetalCryptomist
You can do this workaround if exporting the prvKeys is the only option you have left: /index.php?topic=5351210.msg60007045#msg60007045

For now, use rescanblockchain <start_height> <stop_height> to scan for the latest transactions.
Since your blockchain is pruned, make sure to set the correct start_height since it can't scan the pruned blocks.
To get the unpruned block height, enter getblockchaininfo and look for "pruneheight" from the result,
use it (or higher) as the start_height and leave the stop_height empty.

example workflow:
-Let's assume that pruneheight is 734668
-It will take a while to scan depending on how many blocks you have.

Don't overthink it.
It's normal for hackers to keep the funds untouched until they gained enough balance.
Since the transfers aren't that large, it will be wasteful to spend those right away.

Do you still have the old computer where you did the 1st time GPG verification?
If so, you just have to download the file and signatures there and transfer the verified Electrum to the new PC.

Since you already did it once in the old PC, it's already set-up to do the verification,
you can skip to the last few steps of every tutorial out there (to the actual verification).
For example, if it's Windows, just download the Electrum and its 'signatures' file, then double-click the signatures ('.asc' file).
If Linux, then you'll only need one command to verify the file.

Take note that bitcoin-wallet's salvage command above will default to the 'wallets' folder of the data directory if the wallet's absolute path isn't provided.
So if it's in any other folder, provide the full path to the wallet.dat.

e.g.: -wallet="E:\AppData\bitcoin\test_wallet.dat"

Then it should work without any issue.
The video you linked is too old but the steps should be similar.

Basically, you need to create the transaction in the watching only wallet, then export it using "Export->Export to file".
Then transfer the .psbt file to the offline PC; Open cold-storage Electrum and use "Tools->Load transaction from file" then browse to the .psbt file's directory.
Load it, click "Sign" (type your password),
then export the signed transaction to the online PC (same menus as the first step).
load the signed transaction to the watching only Electrum (same menus as the second step)
Review the transation's details and click "Broadcast" to send it.

---

If you're thinking of "updating" the balance of the offline Electrum, then it's unnecessary since bitcoins aren't stored in Bitcoin wallets.
It's locked in the blockchain which is in every full node of the Bitcoin network, wallets do not receive bitcoins but only "watch" coins that they can spend.
Your offline Electrum has the necessary key to spend it while your watching-only wallet watches for the balance.

Both offline and online Electrum should at least be version 4.0.1 or higher.
If either one is an older version, the exported transactions wont be compatible.

To upgrade: Simply download the binaries from electrum.org, verify its signature (steps).
Then transfer it to the cold-storage machine via flash drive.

Coins.ph can't do anything about the missing transaction since it never existed in the first place.
Her deposit address haven't received any transactions on May12: https://www.blockchain.com/btc/address/3EvaziswFCRAcXAqt8VBQEgim3sjH6oAyF

On a side note, you might want to censor parts of the screenshot or remove it entirely because her Full name and mobile number are in full display.
(and her Nationality for those who can understand the set language of Gmail)

Could be an error in freebitco.in's part.

I can't seem to get a result with Kleopatra's server lookup either.
In the latest version of the website (btcarmory.com/docs/verify), the link to the signing key seems dead, to make it work, just add &op=index at the end of the link's url.
Then import goatpig's signing key from the result: 8c5211764922589a

Then do the rest of the tutorial.

I've searched for related Pull Requests after v22.0 and found this: https://github.com/bitcoin/bitcoin/pull/22839/files
Apparently, it's added as an improvement to "Address Manager" logging.

You should edit this since "...setup" is pertaining to the installer and not the executable.
Should be:

"....\bitcoin-qt.exe" -reindex

Must be outside the quotation marks, either --reindex or -reindex will work on shortcuts.

Also, "writable field" should be specified to "Target:" under 'Shortcut' tab since there are more than one writable fields there.

It is only optional in the image because it's a very old screenshot when Bitcoin transactions with 0 transaction fee were standard.
More info: https://en.bitcoin.it/wiki/Miner_fees#Priority_transactions
But now, although still valid, it's "non-standard" so mostly all nodes wont relay a tx without fee and miners will most likely reject it.

The target is just a number stored in the each block header and as you know it,
a miner who'll generate a hash of their candidate block's block header that's lower than the target will be able to include their block to the blockchain.

Target adjusts in every 2016 blocks which is roughly 2 weeks, the adjustment is based from how fast or slow the previous 2016 blocks were mined.
More info: learnmeabitcoin.com - How is the target calculated?
(you can use the search bar of the link above if you want to know more about Bitcoin)

Haven't you "get it" already in your previous thread where they mentioned that the reward is the block reward + transaction fee?
This: How miners gets rewards for their efforts after successfully mining a block.

In bitcoin-cli, you'll have to load all wallets that you want to work with,
then specify which wallet to use with each wallet command with -rpcwallet=
e.g.:
I don't know how to apply that to "python-bitcoinrpc" library though.

You can create 24-words Electrum seed via the console:

• Enable and open console: "View->Show Console" (needs to open/create a wallet to use)
• Type: make_seed(256) for Native SegWit or make_seed(256,"standard") for Standard
• Copy the result and use it to create a new wallet: "File->New/Restore->Standard wallet->I already have a seed"

But take note that Electrum's seed isn't BIP39 compatible.
It will only work in Electrum and some compatible wallets and tools.

Have you enabled debugging?
I have tested it and it shows in v23.0 with either -debug or -debug=addrman active but it's not showing in v22.0.
So it might be something new that's added in the latest version.

Also, by adding "connect=0", you have disabled "automatic connections" so it might have something to do with it.