Installation of virtualbox 5 breaks guest for 4

[elmos]

I had a guest machine (Ubuntu 64 bit) on virtualbox 4 on windows 7. After I had installed virtualbox 5, I cannot open it anymore. The error message says that the process read could not be done in memory... click OK to quit program. And then it says for this virtual machine no new session could be started. Is there a way to fix this?

[socratis]

First of all, you posted to the Windows guests forum. You should have posted this in the Windows hosts one. I believe that a green hat will take care of this any time now™.

Second, post the whole exact message. Post a screenshot (locally, attached in your message) if you have to.

Third, I suspect that the error message was telling you to post the VBoxHardening.log. Please zip it and post it here. Again attached to your message.

Fourth, have a look at the top of the Windows hosts forum. There is a topic called Discussion of Problems due to Hardened Security. I suspect that this might be your problem, BUT, I cannot know for sure unless you post the exact error messages and appropriate logs.

[Perryg]

Moved to Windows host.

[elmos]

Next to the symbol to start it, it says with a red sign:

abgebrochen

After trying to start it:

VirtualBox.exe - Fehler in Anwendung

Die Anweisung in 0x69d4cd83 verweist auf Speicher 0xb04a7468. Der Vorgang read konnte nicht im Speicher durchgeführt werden.

Klicken Sie auf "OK", um das Programm zu beenden.

Then:

VirtualBox- Fehler

Für die virtuelle Maschine VM1 konnte keine neue Sitzung eröffnet werden.

Details:
The VM session was aborted.


Fehlercode:
E_FAIL (0x80004005)
Komponente:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

[elmos]

VBoxHardening file

[socratis]

Fourth, have a look at the top of the Windows hosts forum. There is a topic called Discussion of Problems due to Hardened Security.

You have a lot of system DLLs that are failing the hardened security test. Take a look at the thread above and see which KB##### from Microsoft are responsible for this kind of mess...

[elmos]

Thanks for your help!

Unfortunately I can't quite figure out how to proceed.

How can I find out which of the KB#### are responsible?

I also don't know how to use the information in the thread you mentioned. There were not windows updates between the upgrade of virtualbox and now that I am aware of. And how can I find out if Avira is the problem or what to do about it if it is?

[socratis]

There were not windows updates between the upgrade of virtualbox and now that I am aware of.

But there was an upgrade of VirtualBox itself. After version 4.3.12, there were some security checks put in place to prevent DLL injections. In order to do this, VirtualBox checks for signed DLLs. Some antivirus, theme changing apps and Windows updates cause problems. If you had these Windows updates and then you upgraded VirtualBox, the security check kicked in. So, you have to search the thread that I pointed you to, to see which of the Windows updates caused problems with VB.

I don't know if Avira is also responsible for that. It could be. I don't run Windows. Again, you have to search the thread that I pointed you to. If you do not find anything similar to your case, then follow the instructions and post your information so that the developers can have a look at it and potentially fix the incompatibility in a future release.

[mpack]

KB3004394 fiasco
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html

KB3045999
http://www.infoworld.com/article/291459 ... albox.html

Note that merely uninstalling the above is not a fix. You have to repair the damage (read the articles, follow the links) or reinstall the host OS.