VERR_NEM_VM_CREATE_FAILED is a very long-standing error that has always been caused by Hyper-V being active on the Windows 10 host. It is natural we would consider the same cause seeing the same error as we move into Windows 10 version 2022 oops, I mean 11.srpen6 wrote:I dont appreciate (etc.)
When you've been around the forum for a hint longer, you'll appreciate that common errors have common causes.srpen6 ... posts: 1
Considering that the devs figured out only a half hour ago that maybe the Hyper-V workaround for 10 got broken trying to implement 11, vs the couple of years we've been helping folks on 10 get Virtualbox running after this error, I think a little lee-way can be given in thinking it's the same old thing.
Hope you can appreciate that.