Hyper-V virtualization - Setup and Use in Windows 10  

I think I'll try researching here too(at least learn a bit): Hyper-V (Updated: October 16, 2015)

I checked my ISO's properties(the troubleshooting goes on) some were re-blocked for some reason, so I unblocked them all and tried to recreate the machine from scratch, but... still that darn error

I will not give up until it either works, or I know why it won't! I would rather use Hyper-V than a 3rd party tool...

I'm running Tweaking(dot)com's Windows Repair to see if it is a permission, COM or network problem(and some other repairs just to be sure). After running it twice in safe mode, I'll try to create a VM again. I was thinking maybe, something(s) after upgrading to Pro might not of been set correctly or something.

Cliff S said:

I'm running Tweaking(dot)com's Windows Repair to see if it is a permission, COM or network problem(and some other repairs just to be sure). After running it twice in safe mode, I'll try to create a VM again. I was thinking maybe, something(s) after upgrading to Pro might not of been set correctly or something.

The above didn't work. In fact, it made it worse, so anybody reading this- DON'T DO IT!!! You'll break it even more.
Now I'm attempting a repair install, if that doesn't work, I guess a fresh install(which I wanted to avoid until Red Stone came out) is the last resort.

Repair install fixed Hyper -V, but I still can't create a machine
I'm beginning to think my CPU is good enough to activate Hyper -V but not use it

I don't believe it's because of your processor. The more I think of it the more permissions issue it looks. Are you able to create and run Windows virtual machines?

Kari said:

I don't believe it's because of your processor. The more I think of it the more permissions issue it looks. Are you able to create and run Windows virtual machines?

With Hyper -V nothing. I had no problems with VMPlayer though. I have reset all permissions(with Tweaking(dot)com's Repair tool, but that totally broke Hyper -V, hence the repair install(which fixed it). I have also tried turning it off in Programs & features and back on, still no joy. Could it be settings in Local Security Policy(I've never used it before, so bear with me please)?

Let's check this permissions issue. Launch the vm once again, let the error message stay open on your display and open the admin command prompt.

Type this command, press Enter, come back to tell what message the command gave (success / error):

Code:

icacls "VHD-PATH\VM_NAME.vhdx" /grant "NT VIRTUAL MACHINE\VM_SID_FROM_ERROR_MESSAGE":(F)

It should grant the current admin user full rights to that vm.

Kari said:

Let's check this permissions issue. Launch the vm once again, let the error message stay open on your display and open the admin command prompt.

Type this command, press Enter, come back to tell what message the command gave (success / error):

Code:

icacls "VHD-PATH\VM_NAME.vhdx" /grant "NT VIRTUAL MACHINE\VM_SID_FROM_ERROR_MESSAGE":(F)

It should grant the current admin user full rights to that vm.

I got this

OK, no mapping done, permissions should be OK.

Next, please post ALL event IDs for Hyper-V created when you last run the vm. It's easiest done in Event Viewer by creating a custom view, selecting Event level as Error, selecting By log, then expanding Applications and Services logs > Microsoft > Windows and selecting all Hyper-V list items:

In this example case the blue highlight shows the errors of the last run, timestamp revealing that the red highlighted error is from an earlier run. In this case you would post the four event IDs highlighted in blue: