Opened 11 years ago
Closed 11 years ago
#11336 closed defect (worksforme)
Unable to restore saved Vista 32-bit session after upgrading to 4.2.6 r82870
| Reported by: | Pepijn Schmitz | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.6 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
After VirtualBox prompted me to upgrade to version 4.2.6 and I did so I can no longer restore a saved Windows Vista 32-bit session. When I try, I get the following error message:
Failed to open a session for the virtual machine Vista.
Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
I will attach the VBox.log file. I know I can probably fix the problem by throwing away the saved state, but I don't want to do what, as it could potentially damage the image, and I don't know exactly what unsaved changes or other important information I will be throwing away.
I have another saved session (a Windows XP one) which does restore without problems.
Attachments (1)
Change History (4)
by , 11 years ago
comment:2 by , 11 years ago
Aha. After rebooting the computer (which I had not done since upgrading VirtualBox) it started working again. So it appears there is an easy workaround for this bug.
It's still a bug of course; at the very least, if a reboot is necessary after upgrading VirtualBox, it should tell you that at the time of installation of the update. Ideally a reboot should not be necessary at all.
comment:3 by , 11 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
To me this looks like VirtualBox found some error when testing for the integrity of the saved state. This could be the result of a disk read error or a hardware bug or similar. My initial suspicion was that the saved state was not correctly saved the last time but then you said that rebooting your host makes the problem go away which is mysterious. I will close this bug except you can reproduce it. In that case you might want to add a comment to ticket #8970.
Log file