Updating to 6.1.26 broke all my VMs

Discussions related to using VirtualBox on Windows hosts.
Post Reply
JohF
Posts: 2
Joined: 31. Aug 2021, 15:20

Updating to 6.1.26 broke all my VMs

Post by JohF »

Hello,
today, back from my holidays i see that VirtualBox needs to be updated.

I was previously using the version VirtualBox-6.1.22-144080-Win.exe on a professionnal computer Windows 10 Version 20H2 (19042.1110).
I downloaded/Installed both VirtualBox-6.1.26-145957-Win.exe and Oracle_VM_VirtualBox_Extension_Pack-6.1.26 without any problems.

After a reboot i notice that none of my VMs start, all with the same error
Échec de l'ouverture de session pour la machine virtuelle xxx.

The virtual machine 'xxx' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).

Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
All my VMs are stored in a directory C:\VM, so i checked the log files in C:\VM\xxx\Logs and the most recent file (VBox.log) is dated August 6th when i stopped it the last time => I have no log of the start attempt.
I tried to uninstall the 6.1.26 version go back to the previous 6.1.22, but the VMs still can't start.

For information i can't remove/temporary stop any AV on my computer (CylancePROTECT is managed by my company, i have no rigths on it)

some of the errors i can see in windows event viewer :
Nom du journal :System
Source : VBoxNetLwf
Date : 31/08/2021 15:07:22
ID de l’événement :12
Catégorie de la tâche :Aucun
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : xxx.local
Description :
Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf.
XML de l’événement :
<Event>
<System>
<Provider Name="VBoxNetLwf" />
<EventID Qualifiers="49156">12</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-08-31T13:07:22.3804146Z" />
<EventRecordID>29271</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="536" />
<Channel>System</Channel>
<Computer>xxx.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\VBoxNetLwf</Data>
<Binary>0000140001000000000000000C0004C00800000000000000000000000000000000000000000000002816AD092E4B2A16AD092E4B28F10E1D5CA40000</Binary>
</EventData>
</Event>
Nom du journal :Application
Source : Application Error
Date : 31/08/2021 15:09:53
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur : xxx.local
Description :
Nom de l’application défaillante VirtualBoxVM.exe, version : 6.1.26.45957, horodatage : 0x61018314
Nom du module défaillant : VirtualBoxVM.exe, version : 6.1.26.45957, horodatage : 0x61018314
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000015108
ID du processus défaillant : 0x2bb0
Heure de début de l’application défaillante : 0x01d79e697cbec12c
Chemin d’accès de l’application défaillante : C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
Chemin d’accès du module défaillant: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
ID de rapport : 03428626-4842-48db-9f14-1b00b846e95c
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
XML de l’événement :
<Event>
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-08-31T13:09:53.3875534Z" />
<EventRecordID>15256</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>xxx.local</Computer>
<Security />
</System>
<EventData>
<Data>VirtualBoxVM.exe</Data>
<Data>6.1.26.45957</Data>
<Data>61018314</Data>
<Data>VirtualBoxVM.exe</Data>
<Data>6.1.26.45957</Data>
<Data>61018314</Data>
<Data>c0000005</Data>
<Data>0000000000015108</Data>
<Data>2bb0</Data>
<Data>01d79e697cbec12c</Data>
<Data>C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe</Data>
<Data>C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe</Data>
<Data>03428626-4842-48db-9f14-1b00b846e95c</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Any help would be much appreciated as i'm completly stuck.
Regards
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Updating to 6.1.26 broke all my VMs

Post by scottgus1 »

Curious you mention Cylance. A few posters in the last week report that Cylance pushed an update that broke Virtualbox, and removing Cylance cleared up the problem.

Since reverting to 6.1.22 did not work, your only chance is to get your boss to make the IT dept let you run Cylance-less for a bit while the IT dept raises a ticket with Cylance. Or they might try setting an exception to stay out of scanning every Virtualbox folder and file, including the USB and network drivers within C:\Windows with 'vbox' in the name.

FWIW, Virtualbox does not 'need' updating every time there is a new version. Updating when forced by a bug fix or new feature is OK. "If it ain't broke etc." :D
JohF
Posts: 2
Joined: 31. Aug 2021, 15:20

Re: Updating to 6.1.26 broke all my VMs

Post by JohF »

Hello,

Cylance was indeed blocking the installation of VirtualBox. After contacting my IT department an update of Cylance has been deployed and it unblocked the situation : the installation could be done and all VMs start normally.
Thanks for your help
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Updating to 6.1.26 broke all my VMs

Post by scottgus1 »

Great! Glad you're back up and running.
Post Reply