You can't use that option anyway since Windows Bitcoin Core wont be able to serve the pruned blocks to the Bitcoin Core on your Mac.

The script type isn't important when recovering funds in Bitcoin core because it can look for all types when scanning for balance.
So if you've successfully imported the private key, it should be able to restore the previous balance once Bitcoin Core finished the rescan.

You shouldn't include the <> in "<my private key>";
but if you typed it correctly, then you've included invalid characters to your private key. It should start with K or L consisting of 52 characters.
example command:

Question: is your Bitcoin Core fully synced to the network after the reinstall? Have you disabled "prune" settings?

Unfortunately yes, aside from the file's timestamp itself, the only indication of a possible date is the block height in the dump file (dumpwallet) when it's last used
and since you've loaded it in 2017, it will show you a block height of 2017.

But since it's created on 2011~2013, one loose indicator that it's that old is if the wallet isn't "HD" (has a slash at the HD logo at the lower-right hand side of Bitcoin Core UI)
It will stay that way unless the wallet has been upgraded into HD by setting an 'HD Seed' through sethdseed command.
In comparison, wallets created by 2017 Bitcoin Core versions are HD.

Does the 30-character "password" looks similar to a "mini private key" as described in this topic:
[overview] Recover Bitcoin from any old storage format ?

If so, try to import it to Electrum (electrum.org) and see if it will restore the address listed in your paper.
[Take your time to verify Electrum's signature before using it for extra security | Select the option "Import bitcoin addresses or private keys" when creating a wallet]

Regardless of the date: if it's from versions lower than v0.31, then your seed phrase can't be used to recover the wallet to the later versions.

These are the "release notes" that came with Electrum v0.32 and some later versions:

TL;DR: It indicates that there were two updates that made the very old electrum wallets unrecoverable with the later versions,
seed should still work but it will generate a different set of keys hence will recover a 0 balance wallet.

Your option is to install v0.30 below, restore your seed phrase, then dump the private keys from the wallet file.
IDK if there are wallet tools that support it though, perhaps some old timer has some info.

This is just for the mentioned features;
but if you wish to get rid of the error, just install ecdsa package through pip: pypi.org/project/ecdsa

That indicates that the wallet.dat may be corrupted, also Bitcoin Core throws a similar error so that should confirm it.

---

I think you need to start your own thread in Bitcoin Technical Support board for corrupted wallet.dat recovery options.
Link to the board: http://bitcointalk.org/index.php?board=4.0

I'm sorry but you're in the wrong board to ask online wallet-related questions.

You can go to web wallets board, then create a new thread (click "new topic" at the right),
link to the Web-wallets: https://bitcointalk.org/index.php?board=222.0

In that case, do not use --datadir and put ".\" before "wallet.dat";
that will tell pywallet to look for the wallet.dat file in the working directory:

The config file should be in the default data directory which is the former.
The latter is the installation directory which wont be used as the datadir by Bitcoin Core, unless told to do so.

The line "datadir" in the config should tell Bitcoin Core to create the files into that folder so there may be something that's causing it to use "E:\" instead of "E:\Bitcoin".
It can be overridden by the -datadir start parameter so check if you're still using an old shortcut.

Or the config file may actually be "bitcoin.conf.txt" which is caused by Windows explorer not showing the extension (enabling "File name extensions" will do the trick).
In which case, it will use what's set in the GUI.

---

You can also try to use the old directory if you don't want to restart from scratch,
rename it into the folder name that you want and put the path into the datadir= line in the config file.

---

Do not forget to close Bitcoin Core to apply the new config.

That was odd, because AFAIK there's no official Windows binary of Electrum in 2011.
Have you somehow used BTCurious' non-official Windows binaries? (/index.php?topic=50936.msg641963#msg641963)

Anyways, there's no way to get into your wallet without those since Electrum isn't kind of a custodial service where your "account" is hosted in a server.
And even if you get the seed phrase, it will still be troublesome to recover the wallet since it suffers to a derivation bug and will generate different keys when restored to the latest version.

You can check if you have more than one wallet in Electrum in the menu: "File->Open" or "File->Recently open".
Sometimes, newbies tend to use another wallet for their "missing transactions".

If you only have one wallet, then it's most likely a clipboard-hijacking malware/virus that changes the address that you've copied or you installed a fake version of Electrum.
(see the other replies to check if you are infected with the malware | verify your downloaded Electrum to see if it's legit)
But neither of those can recover your lost bitcoins, that's to know the culprit.

Are the addresses' script type in the website the same as Electrum's?
In simple words, do the addresses start with 1, 3 or bc1 in both Electrum and website?

Because some merchant API can generate different script type if loaded with an "xpub" from electrum's legacy wallet.

It will be grayed-out in that 'Open Wallet' list if it's loaded
and the wallet should be selectable in the "Wallet:" drop-down menu at the right-hand side of Bitcoin Core:

---

If the PM is about sending the wallet.dat, please don't send it to anyone including me.

Problem is, OP didn't followed anything based from his last reply (which I replied to).
My reply has different goal, it is to cross-check the actual address that he typed in localbitcoins with his Electrum's receiving address.
Plus (in my reply's case) why would you have to go to a blockexplorer if you can already see the transaction's output in the app/website itself?

So you've withdrawn Bitcoins from localbitcoins?
It couldn't be the fee since 1sat/B is enough for now.

Check if it's sent to the correct address:
Go to your localbitcoin's wallet transaction history, look for the withdrawal transaction that you did and check its "receiving address".
Open your Electrum and see if that address is in your 'Addresses' tab, ("View->Show Addresses" to enable the tab).
If it's not there, you've sent it somewhere else.

I hope that you've closed Bitcoin Core when you're swapping the wallet.dat files or there will be issues during the scan process of those wallet files.
(you said you've watch video tutorials so they must have mentioned it)

---

The "wallet-test.dat" is in the "test wallet" folder so it won't be included to the open wallet selection menu, it should be outside that folder, but inside the 'wallets' folder.
The folders inside the 'wallets' folder are considered as 1 wallet (the wallet name is the folder's name) and it will use the wallet.dat file inside it.
If you want to use a renamed wallet.dat file, you should paste it in 'wallets' folder's root, not in the other folders inside it.

Only 1 wallet shows in the "Wallets:" drop-down menu because you've replaced the test wallet's wallet.dat with the old wallet, so the one's recognized by Bitcoin Core is the old wallet.
If there's no balance, it's either the wallet is empty or it there's an issue with the scan process.
Since you've disabled pruned settings (and have enough disk space?), you can use -rescanblockchain command to try to rescan for the wallet's balance but the current wallet may have issue already if you've swapped them while Bitcoin Core is open.

If you properly swapped them, you can enter rescanblockchain into the 'console' (Window->Console) and wait for it to finish (note: it will take a while to finish and may look like it's syncing but it's not actually downloading anything)

If you improperly swapped them, you can just do this instead:

• Close Bitcoin Core.
• Get a copy of the old wallet and rename the copy into "old_wallet.dat"
• Go to 'wallets' folder and copy old_wallet.dat into it (not inside test wallet folder).
• Open Bitcoin Core and it should be in the menu "File->Open wallet", select "old_wallet" and it will be loaded.
• Once it finished scanning, the correct balance should show-up.

The "legit" version in the official repository in Github: https://github.com/jackjack-jj/pywallet
There's an official thread posted here on Bitcointalk: Pywallet 2.2: manage your wallet [Update required]

But "up-to-date"? Not much.

That's normal since you just replaced the wallet.dat inside it.
This is why I'd suggested to rename the copy of the old wallet.dat and paste it inside the 'wallets' folder so Bitcoin Core would recognize both wallets when using the 'load wallet' menu.
Bitcoin-qt will be able to recognize renamed wallet.dat and 'folders with wallet.dat' in that folder using 'Open Wallet' menu.

Replacing the wallet.dat was good for the old version when there's no multi-wallet support, but now Bitcoin Core can handle multiple wallets at the same time.

This is also normal because Bitcoin Core will not create the data directory after being installed.
For the wallets folder, it will be created once you've created the first wallet.

It seems like you're watching some quite old video tutorials when Bitcoin Core automatically creates a "default wallet" when started the first time.

---

By the way, the dumpwallet command in my post above can be used even without downloading the blockchain.
You can immediately export the keys and addresses right after loading the wallet.dat.

You don't have to, if you really need to prune, you just have to make sure that the wallet is loaded before syncing Bitcoin Core so it won't have to use rescan.
In your case, you wont have to resync again after it's done since you've now loaded the wallet (see if it's selectable from the "Wallet:" drop-down menu at the right).

You can use pywallet that's suggested by NotATether.

Or natively, use dumpwallet command to export all of the keys plus their respective addresses but you have to start Bitcoin Core first with "legacy" as the default address type because the dumpwallet file's addresses will be based from it; because you've mentioned that the wallet is from 2011~2013.

If you want to do it:

• Open Bitcoin Core's settings: "Settings->Options...->"; Click "Open configuration file"
• Type in the text editor that will open: addresstype=legacy and save it, then restart Bitcoin Core.
• Open Bitcoin Core, go to Console: "Window->Console", select the correct wallet from the drop-down menu of the console.
• Type the command: walletpassphrase "your_password" 120 to unlock the wallet (do not if it's not encrypted | "120" is to unlock it for 2minutes)
• Within the specified time, type dumpwallet "walletdump.txt" to create a dump file, you can change the name of the file if you want
  or specify the absolute path if you want to save it to another directory. e.g.: dumpwallet "E:\folder\walletdump.txt" (useful if Bitcoin Core doesn't have write permission in the install directory).
• Find the file in Bitcoin Core's installation directory where Bitcoin-qt is located or the specified absolute path and open it with a text editor.

The addresses (and their private keys) should be listed there.
Be careful with the file's contents since it contains the private keys which can be used to spend your wallet's funds.

You can also rename a copy of the wallet.dat file then paste it in that folder,
And in Bitcoin Core, use the menu: "File->Open wallet", select that wallet from the list and it will be loaded and will rescan (that could take a while to complete).

But no one mentioned but it's important that "prune" setting must be disabled when you started the initial blockchain download or else, you'll have to resync Core after loading the wallet file.
The setting is in: "Settings->Options..->Prune block storage to", it will also resync to disable that setting.