So you send your coins to a wallet with no backup or exported keys - very bad idea - please ALL never do this. Many things can and will go wrong, esp with Windows, maybe the exe was still holding onto the file, maybe it was corrupted, etc. Are you sure you didn't run the old version after you ran the new version (that can screw up the wallet too). The hard drive can fail, disk can become corupted etc etc. Not scolding you of course just please always have backups.
Whats the address you sent the coins to? Let me lookup the transaction
Look to see if there is another copy of wallet.dat
Another thing you can see is run: dumpprivkey [address you sent to] on the machine/wallet you sent to - if it spits out the private key, then try re-downloading the blockchain or adding rescan=1 to your conf
So I have run the dumpprivkey through all of the wallets that I could find on my computer, and all of them returned the error code -5, or no key found. Which sucks.
As you asked this is the address I sent my coins to : FUqKqd66Eovmq34nomhshxk4TfzpwFZzYC
The thing is I've been religiously backing up my wallet every time I receive coins (this was on the old qt on my other computer) so I have backups of my old wallet no problems. Its just when I sent the coins to the new wallet (FUqKqd66Eovmq34nomhshxk4TfzpwFZzYC) and I encrypted it (which makes other backups obsolete) that it did the shitty thing. There was no wallet file in the directory which was encrypted, just a brand new wallet.dat that didn't match the address I sent it to.
The running of an old wallet version instead of a new one is not possible. Well not if the computer went and found the old exe somewhere in the seas of deletion! I had my original wallet on this computer (lets name it C1) and then sent it all to a new wallet (only 100 coins
) on another computer (C2). Then for reasons unknown I decided that I wanted my FLT wallet back on C1 (after I had gotten rid of the wallet qt etc from C1, I did not touch the roaming folder) which meant I had my original wallet address still chillin' so I sent it to that. I saw the transaction come in, and thats the reason I encrypted it because I had coins in it
Running Recuva on my external drive where the wallet backups are kept maybe I'll have an old C1 wallet backup somewhere
Ps how do you export private keys?
Let me get this correct? You sent coins from C1 to C2. And you messed up C2 and you can't get to your coins?
If this is the case, on C2, the first thing you did was backup the wallet with your addresses, or encrypted it and then backed it up. Basically, do you have a copy of this wallet.dat before you sent the coins to it?
If so, in %appdata%/fluttercoin, backup the existing wallet.dat just in case...then delete everything, and load the backup you took of C2's wallet before you sent the coins. Load fluttercoin up, let it sync, bingo coins are back.
deleting exe's, encrypting the wallet, nothing matters if you have the original wallet.dat you backed up, you can create everything from that.
NOTE: First step of any wallet management is to encrypt it with a key you WONT forget, and then to back this up somewhere.
there's other things you might be able to do, PM me and we can work on it off thread. I've done recoveries from MEOW forked chain issues, and a really messed up PoS Graincoin wallet.
if recuva can get your C2 wallet.dat it would help
To dump your priv keys from the wallet, in console "dumpprivkey address" if I remember, wallet needs to be unlocked, and not just for minting, walletpassphrase passphrase 9999 false (true is mint only)
