virtualbox.org

hi after some trouble with the uuid i decided to re install vbox , but even after re installing i cannot get anything to start, no vdi is accessible or even if i try installing a new OS it will give an error message
MY QUESTION NOW
how can you clean the host OS of the vbox software and re install, since i get still the errors i suspect the deinstall is not deleting the software properly, i deleted anything vbox in the system32 driver folder + deleted both folders in the users folder, also deleted to entrys in the registry

at first this error.

The virtual machine '98' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\jk\VirtualBox VMs\98\Logs\VBoxHardening.log'.
Fehlercode:
E_FAIL (0x80004005)
Komponente:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

THEN THIS ERROR MESSAGE.

timed out after waiting for child request
rc=258
where supr3hardntchildwaitfor what 5 unknown status 258 (0x102) (258) unkonwn status

Moved to Windows host.

You need to read or post the log that is mentioned in the warning. Re-installing VirtualBox will not fix your problem.

I think I suffer from the same issue. From time to time I use VB to do research for bugs in open source software. Few days Ago my VirtualBox-5.0.8-103449 on WIN7 Home 64Bit stopped working. Always when I try to launch a VM for a minute or so nothing happens, and then I get an error message "Timeout after 60001 ms waiting for child request #1 (Close Events) (rc=258)".
This problem started without any reason I know.
Disabling Antivirus before Launching OVB did not help

Updating to "VirtualBox graphische Benutzeroberfläche Version 5.0.10 r104061" after uninstallation of old version did not help.

Attached .zip contains screenshots and VBoxHardening.log

Hi all,

i get the same timeout error since yesterday. I guess this could be caused ba a virus protection. If I click on the okay button of the message box, the start of the VM will be terminated and the state changes to aborted. If I don't press the button, the VM starts after a couple of minutes, and I can work with them, but I must not press on the button of the twe messega boxes which apperas, if I do so, it the VM will be closed immediately.

Halis, are you using Avira AV? I and others recently ran into this after an Avira update. Uninstall and try.

Yes, it's Avira Pro 2015.

Halis wrote:Yes, it's Avira Pro 2015.

I did not see an effect simply deactivating Avira. Was it necessary to do a new installation of Virtualbox aufter uninstallation of Avira?

Rainer

So I tried the Avira Beta, recommended in the avira forums. Build 15.0.15.132 from "https://betacenter.avira.com/" should resolve the problem, but it seems it does not, I still get the timeout messages.

And the installation process of that Avira on my WIN7 64Bit was not inspiring confidence:
- A message "Installing ..." popped up, promising tipps and facts, but only showed boring advertisement and demand to recommend
AV at facebook and Twitter.
- Browser protection can not be installed, "Install error".

Rainer

Also reboot after having installed Avira Antivirus Update build 15.0.15.132 did not solve my timeout problem. May be I should uninstall AV to test whether my problems really are AV related.

You definitely have a hardening issue. Whether it is AV related is hard to tell. If you still get the same problem with all AV uninstalled then it clearly isn't AV.

What you may have instead is corruption of the security certificates database on your host. Windows Update does this occasionally, and Win7 hosts seem to be especially prone for some reason.

KB3004394
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

Caveat: I would have expected you to notice the corruption before, if these updates caused it.

RrBd wrote:So I tried the Avira Beta, recommended in the avira forums. Build 15.0.15.132 from "https://betacenter.avira.com/" should resolve the problem, but it seems it does not, I still get the timeout messages.

And the problem definitively is the Avira Antivirus Program. Different to promises in the release notes AV Build 15.0.15.132 does NOT heal the problem. https://avira.ideascale.com/a/token/CYF ... aAHDGblT-K seems to tell a good idea where to kick Avira

After I have dropped AV, now VirtualBox works without any problem.

CU

Rainer Bielefeld