VERR_NEM_VM_CREATE_FAILED - need some help where to look next

[Gerry S.]

I've read through the FAQ-directed post, and I think I've covered what was in there. I'm a bit confused by some apparently conflicting bits I've read (which may be nothing more than changes in versions).

I have several existing VM's, and am trying to create a new one. Existing ones range from full Windows 10 on 64-bit, to a 32-bit Linux platform. All (existing and new) produce the dreaded error: "Call to WHvSetupPartition failed: ERROR_SUCCESS ... (VERR_NEM_VM_CREATE_FAILED)."

I've verified virtualization is on in the BIOS (no specific mention of AMD-v), and have done "bcdedit /set hypervisorlaunchtype off" then shut down, as well as verifying all the Windows components listed in the FAQ are appropriately disabled.

I'm looking for some help figuring out where to look next. Here are the details that might (or might not) be salient:

• Dell 7375 Inspiron laptop
• AMD Ryzen 5 2500U CPU, 32 GB RAM
• 64-bit Win 10 Pro fully updated
• Using the latest version of Virtualbox (just updated, was having same issue with whatever my previous version was)
• Webroot is my antivirus (also have Malwarebytes installed, but not actively monitoring - not sure if this matters)

Any ideas where I should look next?

[scottgus1]

How-tos and Tutorials > Windows Hosts:
VERR_NEM_VM_CREATE_FAILED: What do I do?

If the tutorial in this link is the FAQ you read, then you missed something. Everything we know of that causes this error is in that tutorial, there is no other available information.

[Gerry S.]

Thanks. As I said in the OP, I've been through that post and I think I've covered everything specifically listed there.

[scottgus1]

Sorry, edited too slowly, take a look above again.

[Gerry S.]

Specifically, this section (in the thread linked through the FAQ) implies there are other things to look for:

If (1) and (2) are already taken care of, then make sure that no other host apps are already using VT-x/AMD-v. The usual culprits are system level debuggers, other VM platforms, and some resident anti-virus applications. This has become a particular issue with 64bit Windows desktop and server hosts - especially Win2k12 and Win10, as these may enable Microsoft's Hyper-v VM platform by default: this grabs ownership of VT-x and won't play nice with VirtualBox. Note: see the third post below for other Win10 functions that have this effect.

I'm just not sure where to look beyond what's specifically listed in the thread. I have no other VM platforms installed, haven't added any system-level debuggers (and haven't used/activated any included in Windows, if such exist). I don't know if either Webroot or Malwarebytes would be involved, and don't know how to find out. In short, I don't know where to look for other host apps using AMD-v. That's where I was hoping for some guidance where to look next.

[scottgus1]

This is what I was thinking of:

resident anti-virus applications

These are "resident anti-virus applications":

Webroot is my antivirus (also have Malwarebytes installed, but not actively monitoring

I don't know if either Webroot or Malwarebytes would be involved, and don't know how to find out

I suspect this might do it as a quick test:

Webroot [&] Malwarebytes UNinstalled

[Gerry S.]

So, clearly a couple of cups of coffee wasn't sufficient today. Uninstalling those was a straightforward step I didn't try (though I did try disabling both). Future generations may come back and marvel at the lack of snark in your suggestion.

Anyway, the culprit was apparently Malwarebytes - I'm posting that here for future searchers. I liked having it handy as a secondary scan when I felt like it, but Webroot is probably all I really need.

In any case, thanks for the quick replies. I seem to be back up and running.

[scottgus1]

Glad you're up and running!

FWIW, Windows 10 comes with a good AV built-in, some forum gurus and myself just let Windows Defender handle it. Seems to be good so far.