Page 1 of 1
VM session was aborted on W10 host, WXP VM
Posted: 11. Feb 2019, 16:24
by oferlaor
Since upgrading to VBox 6.0 (tried 6.04 same issue), when I load an XP VM on my Windows 10 host I am getting E_FAIL (0x80004005) errors. The errors only occur if I use the temporary saved machine state. If I load the whole VM from a powered down state, it works fine.
The same thing happens on another W7 VM...
Both are giving me the same hardening error: it looks like the error is coming from "C:\WINDOWS\system32\wintab32.dll"
Everything worked perfectly normal on VBOX 5.X
Re: VM session was aborted on W10 host, WXP VM
Posted: 11. Feb 2019, 16:57
by andyp73
VBoxHardening.log wrote:44a0.4d28: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 73681 ms, the end);
259c.1324: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 74187 ms, the end);
This says that the hardening checks are all passing correctly. There is a known issue with restoring saved states under certain circumstances under VirtualBox 6.0.x. See the discussion
Version 6.0.0 Final Snapshot Bug and ticket
#18265 Win7 in VB 6.0.0 fails on resume on 97% for more details and some workarounds you can try.
-Andy.
Re: VM session was aborted on W10 host, WXP VM
Posted: 11. Feb 2019, 19:47
by oferlaor
Tried the fixes proposed in the posts: changing the graphics controller and IO APIC and mouse controller.
No change. I still can't save current state and go back to it. When I load it I get 97% and then E_FAIL.