VM does not resume from saved state

[BeOne]

Hi!

I've installed VB on a new iMac and installed Windows 7 as guest OS. After the Setup has been completed, I closed the VM-Window and selected "Save virtual mashine state" instead of "Power Off" or "Trigger Shutdown AHCI Event". As a result, the VM-State seems to be saved by Virtual Box.

My problem: When I start the VM, the BIOS Status Screen Shows up and Windows boots from scratch, telling me it has not been shut down properly. VB does not load the saved state of the VM.

On my Windows 7 host everything works fine. What did I do wrong?

BeOne

[BeOne]

I now can provide some more Information:

After I closed the Windows with "save the machine state", the VirtualBox Manager Shows "saving" as machine state, which changes to "saved" and then to "aborted". What does that mean?

[mpack]

Perhaps it means that a log file would be useful.

[BeOne]

It seams to be a bug, the 4.1.18 version works perfectly!

[BeOne]

The Downgrade only worked for a couple of hours.

It really seam to be an older bug. I found a ticket, but can't find it again for link creation.

[mike_hore]

Hi there,
I had exactly this problem 6 months ago, so I'll tell you what happened, but it mightn't help much. In Windows 7 I installed Visual Studio 2008. No problem. Then the next time when Windows wanted to do an update, the updates included some for Office 2007. Now I DON'T have any version of Office installed, since I don't need it in the Windows VM. But I went ahead and allowed the update, then AFTER THAT the problem came up, every time. Whenever I tried to save the VM state, I got the status of the VM showing as "aborted".
I got out of the problem by restoring a backup VM, and after that always deselected the Office update files when Windows wanted to do an update. I can only assume that Microsoft never envisaged that somebody with Visual Studio wouldn't also have Office installed, and that the attempt to update a nonexistent Office installation corrupted the Registry somehow.

Cheers, Mike.