I will wait for your updated wallet.. cause regardless of what i do here.. (and this is not a local issue).. its a wallet node issue.. I don't know how many times i have to tell you the same thing to get you to listen.. I am experienced enough to know when a wallet is not working correctly. and again to re-iterate .. it is connecting to a bad node somewhere in the time of the last 2 weeks.. and it can't figure out which is right and wont stay connected to the correct nodes.. there is no way that is my local problem.. i don't control who the wallet connects to .. get me yet? .. would sharing my wallet address help you in find out what the issue is? work with me here..
That wont help, but you do have control over what nodes you connect to, first off by deleting peers.dat, that makes you connect to the seed nodes that are all working correctly, then if your really stuck, you can make it so it only connects to the seed nodes (or any other node) by butting this in your config:
connect=ip_or_dns_here
You can have multiple connects, and this forces the wallet to ONLY connect to these ips.
I agree a few days ago there was a problem, our test wallets had the same problem, but after the checkpoint master was repaired all our test wallets started working even without a resync, we've also done full resync tests too.