Method 3: Installing the VirtualBox kernel driver If you’re still seeing the error despite disabling your 3rd party security suite, move down to the next method below. If the AV was interfering with VirtualBox, you’ll no longer get the “Virtual machine has terminated unexpectedly during startup with exit code 1 (0x1)” error. Once the antivirus has been taken care of, open VirtualBox and launch the virtual machine again. You can do this by following this guide ( here). Disabling the real-time protection on Avast AntivirusĪn alternative would be to uninstall the security suite completely by removing the 3rd party security suite from your system. The steps of disabling the real-time protection are specific to each 3rd party antivirus, but you can typically disable it by right-clicking the taskbar icon and using the context menu. Several users that were using a 3rd party security suite have reported that the error doesn’t occur if the real-time protection of the AV is disabled. Method 2: Disable the antivirus while running the virtual machineĪnother frequent culprit that will trigger the “Virtual machine has terminated unexpectedly during startup with exit code 1 (0x1)” error is an external antivirus suite ( a security option different than Windows Defender). If a restart is not effective or you’re looking for a more permanent fix, move down to the next method below. Several users have reported that after they rebooted their computer, VirtualBox was able to open virtual machines without being interrupted by the “Virtual machine has terminated unexpectedly during startup with exit code 1 (0x1)” error. If you haven’t already done this, start simply by rebooting your machine. Since the methods below are ordered by efficiency and severity, follow them in the order that they are presented until you find a fix that successfully resolves the issue in your particular scenario. Below you have several fixes that other users in a similar situation have used to get the issue resolved. If you’re currently struggling to resolve this particular issue, one of the methods below will enable you to resolve the issue. So far, this issue is only confirmed to occur on Windows 7. A bad Windows Update is causing the error – There’s one particular update that is confirmed to be causing this particular error.3rd-party antivirus is interfering with VirtualBox – In a couple of reports, affected users were able to get the issue resolved by temporarily disabling the real-time protection of their 3rd party AV.The VirtualBox kernel driver is not installed (or is corrupted) – A couple of users have managed to get the issue resolved by reinstalling VirtualBox along with the VirtualBox kernel driver.
0 kommentar(er)
