was your wallet.dat passcode protected before you ran the new wallet? if you have an old wallet.dat backup and you create passcode on this new wallet you get a new addresspool for change addresses. if this wallet gets corrupted and you bring in the old one you have lost the keys... if you sent out a transaction after encrypting your wallet last night the rest may be in a change address. you need that corrupt file to try and repair.
*edit this may not be plausable in your case if you did not send any transactions from this new coin -qt
*edit this may not be plausable in your case if you did not send any transactions from this new coin -qt
He staked, means the hacker could see the pass because computer was already compromised.
We need to push people that devs start to use a secondary pass for staking which is logic and more secure.
fair enough, this is just the first time im hearing of an event like this here.
*Edit: sorry UnHappyDay it surely sucks terribly.

Thanks for the feedback Stealth and Jase. It is strange that something would happen shortly after I install the new wallet and I have never had problems on that system before this.
Yeah it does suck, had put a bit too much investment into the coin too early. Expensive Lesson Learnt!!