Opened 8 years ago
Closed 8 years ago
#15985 closed defect (fixed)
windows 10 version 1607 VirtualBox 5.1.6-110634 failed to start
Reported by: | DsiGS | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.6 |
Keywords: | failed to start | Cc: | |
Guest type: | all | Host type: | Windows |
Description
OS :windows 10 version 1607 VirtualBox : 5.1.6-110634 failed to start
Windows Log :
Nom de l’application défaillante VirtualBox.exe, version : 5.0.16.5871, horodatage : 0x56d9b7eb Nom du module défaillant : VirtualBox.exe, version : 5.0.16.5871, horodatage : 0x56d9b7eb Code d’exception : 0xc0000005 Décalage d’erreur : 0x000000000001a432 ID du processus défaillant : 0x1750 Heure de début de l’application défaillante : 0x01d216effb22bd38 Chemin d’accès de l’application défaillante : C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Chemin d’accès du module défaillant: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe ID de rapport : 60a717d2-0940-4be1-a090-5a8ed1311052 Nom complet du package défaillant : ID de l’application relative au package défaillant :
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-09-25T05:45:12.331101800Z" /> <EventRecordID>663</EventRecordID> <Channel>Application</Channel> <Computer>PCHomeB</Computer> <Security /> </System>
- <EventData> <Data>VirtualBox.exe</Data> <Data>5.0.16.5871</Data> <Data>56d9b7eb</Data> <Data>VirtualBox.exe</Data> <Data>5.0.16.5871</Data> <Data>56d9b7eb</Data> <Data>c0000005</Data> <Data>000000000001a432</Data> <Data>1750</Data> <Data>01d216effb22bd38</Data> <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data> <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data> <Data>60a717d2-0940-4be1-a090-5a8ed1311052</Data> <Data /> <Data /> </EventData> </Event>
Change History (2)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Should be fixed with VBox 5.1.8.
Workaround for now (works for me) - is just to rollback Windows update. See how: http://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/