Harry Putnam
2014-09-13 15:08:13 UTC
[NOTE: This was also posted on the online Vbox forum under the Windows
Hosts section]
Setup: HOST: Win 7 64bit
Virtualbox 4.3.14
GUEST: Linux: debian (jessie)
I've had this vm running for a few months now. I think this problem may
have been brought on by something like a hard reboot.
At any rate on bootup today I see the vm is reported as `aborted' in the
gui vbox tool. Attempting to boot brings this error:
VirtualBox - Error In supR3HardenedWinReSpawn
===========================================
Error Relaunching VirtualBox VM process 5
Command Line: `81954AFS-4D2F-31EB-A142-B7AF187A1C41-suplib-2ndchild
--comment dv --startvm 4e50922d-ac89-4353-b003-aa3c5b5fe103 --no-
startvm-errormsgbox`(rc=-104)
(Boy, that last bit's a mouthful)
I realize things have moved on to a new version but I was afraid to do
much of anything without getting some advice. I would really like to
salvage this vm as a lot of time was spent setting up the debian system
to do specific things.
Can anyone tell me if this kind of error is just hopeless or are there
some known rescue attempts I can make?
------- ------- ---=--- ------- -------
ps - since writing this I've been reading more of the online vbox
forums where this trouble has cropped up but mostly inregard to 4.3.16
In that discussion, someone mentioned that 4.3.12 does not have the
problem .. I downgraded to 4.3.12 and now have my vm running again.
That is not a wonderful solution but for the moment at least I can
backup a working system.
Hosts section]
Setup: HOST: Win 7 64bit
Virtualbox 4.3.14
GUEST: Linux: debian (jessie)
I've had this vm running for a few months now. I think this problem may
have been brought on by something like a hard reboot.
At any rate on bootup today I see the vm is reported as `aborted' in the
gui vbox tool. Attempting to boot brings this error:
VirtualBox - Error In supR3HardenedWinReSpawn
===========================================
Error Relaunching VirtualBox VM process 5
Command Line: `81954AFS-4D2F-31EB-A142-B7AF187A1C41-suplib-2ndchild
--comment dv --startvm 4e50922d-ac89-4353-b003-aa3c5b5fe103 --no-
startvm-errormsgbox`(rc=-104)
(Boy, that last bit's a mouthful)
I realize things have moved on to a new version but I was afraid to do
much of anything without getting some advice. I would really like to
salvage this vm as a lot of time was spent setting up the debian system
to do specific things.
Can anyone tell me if this kind of error is just hopeless or are there
some known rescue attempts I can make?
------- ------- ---=--- ------- -------
ps - since writing this I've been reading more of the online vbox
forums where this trouble has cropped up but mostly inregard to 4.3.16
In that discussion, someone mentioned that 4.3.12 does not have the
problem .. I downgraded to 4.3.12 and now have my vm running again.
That is not a wonderful solution but for the moment at least I can
backup a working system.