Opened 6 years ago
Last modified 6 years ago
#17935 new defect
VBox crash restarting after Windows guest put into fullscreen mode, and VM unusable after that
| Reported by: | SDD | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.18 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Mac OS X |
Description
I'm using Virtualbox 5.2.18 to run a new Windows 10 VM on Mac OS 10.13.6 on a 12" MacBook. If I take the Windows 10 guest full screen, then save the machine state, I am unable to restart it. I get:
Failed to open a session for the virtual machine Win10. The VM session was aborted. Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
After that, Virtualbox itself crashes, and the machine has a status of Aborted. I've not found a way to get the machine started after that, short of restoring from a Time Machine backup. Even if I delve into the vbox file and change fullscreen to false, I get the same crash trying to restart the machine. I've attached a zip archive of the Mac OS crash log, and the Virtualbox log. This is entirely repeatable, and I get the same error on an old Windows 7 VM.
Attachments (1)
Change History (2)
by , 6 years ago
| Attachment: | Archive.zip added |
|---|
comment:1 by , 6 years ago
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=8&t=89008
So far, the issue hasn't been reproduced on 10.11.6 or 10.13.6. I asked the OP for more details in the forums. Will update the ticket if/when newer information is (hopefully) available.
Log and crash log