Next button is "not active" because the SEED isn't valid. There may be a typo or it was from a non-2FA wallet.

What was the result shown in the "Seed Type: ?"
Was your seed created using Electrum?

If you're 100% positive that it was from an Electrum 2FA wallet, then you might have entered a wrong word or two.
If it's from a standard wallet, use the options "Standard Wallet->I already have a seed".

Not in mempool means that it wasn't broadcast yet.
It might be: saved without broadcasting, rejected by your own node for some reason or just a connection issue of your node.

Try to check if that transaction was already confirmed using an online blockexplorer by pasting the "Transaction ID" to the search bar.
If there's a result, it's just your node/client; If there's no result, re-broadcast it to any blockexplorer and see if it will be accepted.

Steps for broadcasting using a blockexplorer: Right-click the transaction, select "Copy raw transaction",
paste it here: https://blockstream.info/tx/push or https://blockchair.com/broadcast (select bitcoin) and click Broadcast transaction.
If it resulted with an error message, paste it here.

The GUI does it for you, it's in the bottom part labeled as "Balance" and the history is listed in the "history".
I don't get why you need to query your balance using a third-party client/explorer.

If you're using the daemon, you can import your "master public key" to the GUI client to create a watch-only wallet for this purpose.

It's best if you can provide some info about your operating system, Electrum version and your goal.

Based from the keyword "PayServer", it might be Electrum's merchant website payment processor that previously can only be configured using Electrum daemon.

For the next release, it will be included or there will be an option to enable it in the user interface.

Hmm, the one that was detected was your selected server, AFAIK there are couple of similar reports in Electrum board;
that shouldn't be a problem specially that you're using a hardware wallet.
However, I suggest you to verify your Electrum's signature for a peace of mind:

Official Guide: https://electrum.readthedocs.io/en/latest/gpg-check.html
Unofficial Guide by AbdussamadA: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/

That '49' in the path is for P2WPKH-nested-in-P2SH "3-Segwit" account and the next '1' indicates that it's for testnet, not bitcoin.
But the webtool somehow set this path by default, if you select other coins then reselect "Bitcoin", it'll change into 49'/0'/0'/0/0.
The tool looks buggy to me.

BTW, for native Segwit, it should be: m/84'/0'/0'/0/0

If you need to sign using a Segwit address, follow their suggestions: use Electrum.

---

Try this fix: https://medium.com/@qertoip/ledger-electrum-error-failed-to-create-a-client-for-this-device-555a16b86fe8

Uhh, it starts with 'M' not 'W'  
Did it started with "W" addresses then changed to 'M' just like Bitcurrency?

Between 755 and 910..? you almost got it

The info is in this thread: Activity & new membergroup limits, it was linked as a quote in the unofficial rules thread.

Completely agree on the Hardware wallet part but this! There's no point in "testing" your paper wallet.
Plus you might be talking about import to an offline wallet, not sweep.
You'll only need to do the "import thing" during the creation to double-check if the key will generate the correct address.
And as long as it was created and kept offline, you can assure that your cold storage fund is safe.

I'm talking about all known blockexplorers in general, "most block explorer" isn't a name or brand.
Examples of those limits is: capped at x number of queries per hour or day which 'x' can be as high as 1000,
so if you plan on doing that locally, your PC's spec must be higher than the average.

Blockchain.com have a form if you want to bypass their "limiters": https://www.blockchain.com/api click "REQUEST API KEY".
That involves registration and providing them some information.

Internet speed will only be an issue during the sync process.
For fetching blockchain data which requires -txindex, you'll be needing fast drive, powerful processor and a quite huge RAM for huge cache size
since you're talking about a scale beyond the limit of most blockexplorer API.

Can you view the TXID of those unconfirmed transactions?
If so, copy and paste them to a multi-coin blockexplorer and see if you can get a result, try: https://multihash.net/en

If your W10 PC's Bitcoin Core isn't fully synced, there's a chance that the balance wont show.
But if it was synced, you can just proceed to send your Bitcoins after finishing rescan.
Based from your screenshot, it looks good and just a few blocks away.

If you want to useknow the "alternative" that I've mentioned above, it's about using dumpwallet command to get the "extended private master key" or private keys then import them to Electrum:

• Start 'Bitcoin-qt' as administrator, then open 'window->console'
• Enter dumpwallet keys.txt (you can change 'keys' into any name that you want)
• Go to the installation directory of your Bitcoin core and find "keys.txt", open it and find the addresses' private keys, list of strings that start with 'K' or 'L'.
• Download Electrum Windows Stand-alone Executable from electrum.org

|

• -snip- (can't restore hardened derivation path using xprv dump to Electrum)
• If your addresses starts with '3' or 'bc1', you'll need to import each prv keys to electrum using the option "Import Bitcoin addresses or private keys" by pasting each keys per line using:
  p2wpkh-p2sh:YOUR_Private_key if your addresses starts with '3'
  p2wpkh:YOUR_Private_key if your addresses starts with 'bc1'

Just let Bitcoin-qt sync (speed depending on your hardware and ISP)
and after that, you can send your fund using the "send" tab.

Alternatively, you can import those private keys / extended private master key (xprv...) to Electrum.
Use 'Import Bitcoin addresses or private keys' for prv keys | 'Standard wallet-> Use a master key' if you have the extended key to create the wallet.

Please read my reply above *2.

It will always say "false" for an active 2FA wallet because the SEED wasn't saved to the wallet file.
If it's available, then it defeats the purpose of using 2FA because when the user's PC/device and passphrase got hacked, the hacker can just get the seed using that option.

1. It's the 12-word backup that Electrum prompted you to write during the wallet creation.
2. A wallet with active 2FA wont save the SEED to the wallet file, that option will only be available "true" if you disable 2FA.
And the only way to disable it is to restore using the seed.

You have two options: find the seed (100% reliable) or contact TrustedCoin using the email that you've used to register.

From the looks of it, this can be considered as "solved". You can lock the topic whenever you want using the "lock" button below (lower-left).

You might have downloaded and installed that Electrum fork somewhere in the past as it's impossible for the official site to have a mix-up like that.

Will you use it exclusively for Bitcoin?
If yes, you can stick with Electrum; otherwise, install both for different purposes.
Ledger Live for multi-currency management and transactions.
Electrum for Bitcoin transactions with extra features like freezing addresses & UTXO.

Some aren't included in ASCII & extended ASCII characters... IDK if it's possible to use that as a passphrase for Trezor.
It will only accept ASCII as stated here: Passphrase - Trezor Wiki.

12+ Random case characters with numerics and punctuation is enough IMO.

Yes, that's one way.
If that watch-only wallet has a public key (wallet->pub key),  you might have a backup seed of it (12-word mnemonic).
If just labeled as "imported", the private keys are your main option.
Though your seed may contain those keys, so look for both seed and prv keys.