I too am seeing this problem with 6.1.28 on Windows - re-installing 6.1.26 solves the problem.
Having re-installed, I noticed last night it was automatically upgraded to 6.1.28 last night - causing the same issue.
I have the update check turned off, but how do I stop automatic updates?
jerry
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
I don't think there is a built-in automatic Virtualbox update. It will check for updates available and report this availability, but Virtualbox does not automatically update itself.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Correct. The last time someone insisted this had happened, we pretty much pinned it down to a local IT update policy, not a VirtualBox feature.scottgus1 wrote:I don't think there is a built-in automatic Virtualbox update.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Ok, then I need to understand how to disable this.mpack wrote:Correct. The last time someone insisted this had happened, we pretty much pinned it down to a local IT update policy, not a VirtualBox feature.scottgus1 wrote:I don't think there is a built-in automatic Virtualbox update.
3rd night in a row my Windows 10 system "automatically upgraded to 6.1.26 -> 6.1.28" and rebooted my system. Now my VMs no longer function.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Since Virtualbox doesn't have this function, you'll need to check your PC's or workplace's policies, or web-search how to disable it.
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
Well... today after upgrading to 6.1.28 I've found that the new version will break coexistence of VirtualBox and HyperV.heymanj wrote:I too am seeing this problem with 6.1.28 on Windows - re-installing 6.1.26 solves the problem.
Having re-installed, I noticed last night it was automatically upgraded to 6.1.28 last night - causing the same issue.
I have the update check turned off, but how do I stop automatic updates?
jerry
I hoped the new version will have and improvement in this coexistence not break it, so... for the moment the only option is go back to 6.1.26... and waiting for the 6.1.30 version...
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED
I will lock this one so we don't have to maintain more me-too's.
All would-be posters here:
In attempting to prepare for Windows 11 Hyper-v/Virtualbox coexistence, 6.1.28 introdiced a bug that broke Windows 10 Hyper-v/Virtualbox coexistence.
Revert to your previous version if you must have Hyper-V enabled, or disable Hyper-V: VERR_NEM_VM_CREATE_FAILED: What do I do?
All would-be posters here:
In attempting to prepare for Windows 11 Hyper-v/Virtualbox coexistence, 6.1.28 introdiced a bug that broke Windows 10 Hyper-v/Virtualbox coexistence.
Revert to your previous version if you must have Hyper-V enabled, or disable Hyper-V: VERR_NEM_VM_CREATE_FAILED: What do I do?