Thanks for the response. I did try to rescan. It rescanned very fast, and still no balance. When I try to add the backup wallet file that I had made earlier, it always makes a new wallet file, as if there is no file there. – Chad Michael Libby – 2018-01-12T01:26:52.773

When you use a backup, you must name it wallet.dat otherwise Bitcoin Core won't know it is there. Rescanning should take a very long time unless you are not fully synced. – Andrew Chow – 2018-01-12T01:30:34.683

Yes, I did name it wallet.dat , it says that it is fully synced. Still no balance. When I used salvagwallet, it also made a wallet bak file. When I try to run with that file, even when renamed, it just makes a new wallet, again. – Chad Michael Libby – 2018-01-12T01:33:43.247

Is the backup from before or after you used salvagewallet? What makes you think that it makes a new wallet file? – Andrew Chow – 2018-01-12T01:37:33.630

Yes, I have tried the backup that I made before I used salvagewallet. I can see in the bitcoin folder that it is making a new wallet each time. It also has a new receiving address. – Chad Michael Libby – 2018-01-12T01:39:16.353

If it is making a new wallet every time and you can see that file, then you are not naming your wallet file correctly. The underlying file system does not allow for two files to share the same name (which includes the extension). – Andrew Chow – 2018-01-12T01:43:37.130

it seems to be naming the new wallet "wallet" without the .dat, – Chad Michael Libby – 2018-01-12T01:45:32.920

This is in the debug file:

Renamed wallet.dat to wallet.dat.1515627016.bak 2018-01-10 23:30:16 Salvage(aggressive) found 5256 records – Chad Michael Libby – 2018-01-12T01:51:12.127

No, it's just that your file explorer is not showing the extension, which is default behavior on windows. In Windows, click "View" and then click "File name extensions" to see the full file names. What you should then see is the new wallet is wallet.dat and your backup is wallet.dat.dat. – Andrew Chow – 2018-01-12T01:53:08.693

Thank you very much. That did it. This is an old wallet file, from one of the first versions of bitcoin core. I don`t remember having any coins on it back then, but wanted to make sure that there were no private keys that were not showing up on the new program, which is why I ran salvage, I probably should have moved my known coins first. Anyway, how do I check for old private keys? – Chad Michael Libby – 2018-01-12T02:05:12.203

Is it normal for salvage to have found 5256 records? – Chad Michael Libby – 2018-01-12T02:10:07.813

You don't/can't. All private keys (old and new, whatever the distinction for that is) are loaded regardless and don't just "hide somewhere". salvagewallet will make things worse and make it more likely that private keys don't appear as it is known to corrupt uncorrupted wallets. – Andrew Chow – 2018-01-12T02:10:53.927

So when I ran salvagewallet, it made a backup (bak) file and it also made a new wallet file. What is the new wallet file for? Is it just an empty new wallet, or did it try to import keys to the new wallet? – Chad Michael Libby – 2018-01-12T02:18:36.507

It is a new wallet file with only the private keys it was able to extract imported into that wallet. Note that those private keys are not necessarily actually your private keys (they could just be garbage data that looks like a private key) and that it may not actually find all of your private keys. – Andrew Chow – 2018-01-12T02:21:23.577

So, when I use the new wallet that was created, it shows zero balance. It this right? – Chad Michael Libby – 2018-01-12T02:26:46.300

Without a rescan, it will show zero balance as there is no transaction information known to the wallet. – Andrew Chow – 2018-01-12T02:38:16.077

Well, it`s odd. Even with a rescan and the sync up to date, it shows zero balance. – Chad Michael Libby – 2018-01-12T02:55:02.213