Opened 9 years ago
Last modified 7 years ago
#14978 reopened defect
Error In supR3HardNtChildWaitFor
| Reported by: | Nils | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.12 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Hello, I get this error on startup since 5.0.8 (also on .10 and .12). Key Host Info:
- Lenovo x250 16GB RAM, 512 SSD
- Host win7 (latest patches some win10 upgrade stuff suppressed)
- guests: debian (but probably irrelevant)
- avira antivir antivirus
- comodo firewall
When I start vbox, after a while I get the following error:
VirtualBox - Error In supR3HardNtChildWaitFor Timed out after 60001 ms waiting for child request #1 (CloseEvents). (rc=258) where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)
If I do not close it and wait a while (another minute or so) I get it again, and then the guest opens just fine. See this bug description: https://forums.virtualbox.org/viewtopic.php?t=64111&f=6#p301426 (way back from Oct 2014 and 4.3.18) ...it is essentially this. If I close any of the dialogs, then the guest does not open. Attached are the logs (from 5.0.10, I can recreate with .12 if desired) and a screenshot of the errors. The logs appear normal.
Thanks Nils
Attachments (6)
Change History (10)
by , 9 years ago
| Attachment: | dweb642-2015-12-14-22-55-17.log added |
|---|
comment:1 by , 9 years ago
This is probably a duplicate of https://www.virtualbox.org/ticket/14908 and https://www.virtualbox.org/ticket/14905 It seems to be the same issue, also with Avira antivir causing it. It started around the same time my problems started (a few weeks ago)
comment:2 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
comment:3 by , 7 years ago
| Resolution: | obsolete |
|---|---|
| Status: | closed → reopened |
Would like to mention that this bug happens still in VirtualBox 5.1.x and 5.2.x series.
comment:4 by , 7 years ago
Please search the forums as well before re-opening a ticket. For the solution/workaround see this post.
And complain to Avira to not interfere on other's processes without being properly signed, or without having updated the Windows certificate database. For more information, check out the article Diagnosing VirtualBox Hardening Issues and point them to that.
vbox log