Re: I Can't run any Windows-like VMs anymore on W10 20H2
Posted: 15. Dec 2020, 02:24
In the meanwhile, I managed to start Normally Windows 98 SE changing unusually the Graphic options to VboxVGA to VMSVGA; and, above all, in a quite casual way, I found what caused the worst problms on Windows XP.
On the VM i had installed Avast Free Antivirus, since the begin. For some reason, after the Windows 10 Update, VirtualBox is unable to load the Avast drivers and goes to BSoD. Now in Safe mode i Uninstalled it and the problem disappeared; but still I don't get what caused this casual "change of mind" about the AV in the VM.
I found out this trying to make a new installation of Windows XP on a new VHD; when i Installed the AV the VM blocked and showed a red and black glitch con the top of the screen. When I rebooted the VM, it showed the BSoD like the other VM...
The thing could be connected actually to the last update of the Host OS, with which Windows 10 managed to block some internal file into the VDI file of the VM linked to the internal Antivirus. As I've already told, exactly in the moment in which Windows XP ends the Avast Antivirus installation on Windows XP, it starts to glitch and block itself and goes to critical shutdown; so this could be in some way connected to the sensibility that VirtualBox or the Host OS now have about Antivirus files in the VM. Sure is not a Host Antivirus problem, because also without it the VM wasn't still able to start...
Anyway, thanks a lot for the help, I hope that if it's a bug of VirtualBox or of Windows that it will be resolved soon, because it's kinda tricky to find and resolve because it pratically blocks suddenly the VM without a reason
On the VM i had installed Avast Free Antivirus, since the begin. For some reason, after the Windows 10 Update, VirtualBox is unable to load the Avast drivers and goes to BSoD. Now in Safe mode i Uninstalled it and the problem disappeared; but still I don't get what caused this casual "change of mind" about the AV in the VM.
I found out this trying to make a new installation of Windows XP on a new VHD; when i Installed the AV the VM blocked and showed a red and black glitch con the top of the screen. When I rebooted the VM, it showed the BSoD like the other VM...
The thing could be connected actually to the last update of the Host OS, with which Windows 10 managed to block some internal file into the VDI file of the VM linked to the internal Antivirus. As I've already told, exactly in the moment in which Windows XP ends the Avast Antivirus installation on Windows XP, it starts to glitch and block itself and goes to critical shutdown; so this could be in some way connected to the sensibility that VirtualBox or the Host OS now have about Antivirus files in the VM. Sure is not a Host Antivirus problem, because also without it the VM wasn't still able to start...
Anyway, thanks a lot for the help, I hope that if it's a bug of VirtualBox or of Windows that it will be resolved soon, because it's kinda tricky to find and resolve because it pratically blocks suddenly the VM without a reason