Solved VirtualBox error

[proudtobegreek]

Hi there everyone,all of a sudden three fully working virtual machines,stopped functioning,deleted all of them,created new vhd's,using disk2vhd,the error persists.Completelly uninstalled VBox,installed 4.3.26 98988 and its extension,no go!

Any help out there?

 

[DaddyG]

Hi there

These errors you're experiencing are no doubt caused by the security 'hardening' introduced to VirtualBox.
This is causing a lot of concern to users of the software whose VM's are now 'broken'.
You can follow the progress towards a solution at the VirtualBox forums, specifically this one ..
https://forums.virtualbox.org/viewtopic.php?f=6&t=66639

In the meantime to get your VM's working again, you will probably need to revert back to version 4.3.12 (which was the last one before 'hardening' was introduced).

This has been an ongoing problem for a long time and I personally can't wait any longer for VirtualBox to be fixed. I intend to switch to VMWare in a few days.

 

[Kari]

Hi there everyone,all of a sudden three fully working virtual machines,stopped functioning,deleted all of them,created new vhd's,using disk2vhd,the error persists.Completelly uninstalled VBox,installed 4.3.26 98988 and its extension,no go!

Any help out there?

Did you try creating new virtual machines in Hyper-V? Your specs say you have Windows 8 Pro which means you have Hyper-V. In your case I would try it at least.

 

[proudtobegreek]

Did you try creating new virtual machines in Hyper-V? Your specs say you have Windows 8 Pro which means you have Hyper-V. In your case I would try it at least.[/QUOTE]

Tried once,cant remember exactly,but had some crashing issues,stuck to VBox,am running 10 in VMWare though.Is there a guide,how to run actual OS in VMWare?

 

[proudtobegreek]

Hi there

These errors you're experiencing are no doubt caused by the security 'hardening' introduced to VirtualBox.
This is causing a lot of concern to users of the software whose VM's are now 'broken'.
You can follow the progress towards a solution at the VirtualBox forums, specifically this one ..
https://forums.virtualbox.org/viewtopic.php?f=6&t=66639

In the meantime to get your VM's working again, you will probably need to revert back to version 4.3.12 (which was the last one before 'hardening' was introduced).

This has been an ongoing problem for a long time and I personally can't wait any longer for VirtualBox to be fixed. I intend to switch to VMWare in a few days.

did some reading,those "renaming" solutions did not apply,will give it a second chance or revert to the older working 4.12 version,as stated...

 

[proudtobegreek]

Confirming,that version 4.3.12 is fully functional,actual installation as vhd,created with disk2vhd,in fullscreen and seemless mode.
My interest is in virtualizing my actual OS's,installing any application to them or "tweaking" the system,before i proceed to do so in my "real" ones,precaution wise,has kept me off troubles for a long time.