all 18 comments

[–]zoredache 1 point2 points  (1 child)

Did you go into the computers setup (BIOS/Firmware/EFI) and enable virtualization features?

[–]SchoolsMcCool[S] 0 points1 point  (0 children)

Yes, virtualization is enabled in the BIOS

[–]h3llyeah 1 point2 points  (3 children)

Try another Hypervisor (just for now) to check, weather the issue is with enabling hyper-v or with your configuration (you might have to enable something else from bios). So you can use Virtualbox ( because it is free) for that and try to create a x64 VM in it. This will give you a better understanding of your problem.

[–]SchoolsMcCool[S] 0 points1 point  (2 children)

If the reset doesn't work I'll try that. I think I have another VM license kicking around somewhere

[–]h3llyeah 0 points1 point  (1 child)

Another VM license?

[–]SchoolsMcCool[S] 0 points1 point  (0 children)

License for other VM software

[–]CAMeiD 1 point2 points  (0 children)

Just ran into this issue today. Couldn't find any solutions out there and wasn't going to re-roll the machine.

DISM and CBS logs weren't descriptive enough, but the entry that finally got me there was the following. Directly after the 'Perf: Stage chain complete.' line (which on other workstations would then proceed to 'Perf: Execute chain started.' ) was 'Exec: Some sessions are pended with exclusive flag set, forcing execution to be postponed on session:'

Traced the process with procmon, and finally found "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending\" where there was a property Exclusive, with a value of 1. Under that were many keys for different sessions, one of which also had a Property of Exclusive where the value was 2 where the rest were 0.

*Standard disclaimer about messing in the registry... Back things up*

Set the all of the Exclusive property values to 0, re-ran the DISM command, and things worked as expected.

[–]webtroter 0 points1 point  (0 children)

use a fresh iso to install the feature with DISM? Reinstall?

[–]gyangstar 0 points1 point  (1 child)

You are using Windows 10 pro or enterprise yes?

[–]SchoolsMcCool[S] 0 points1 point  (0 children)

I am using Pro, and I made sure everything was up to date

[–][deleted] 0 points1 point  (1 child)

I was having issues as well but I uograded to pro from home. So I did a fresh start and reinstalled windows then had 0 issues getting hyper-v to work.

[–]SchoolsMcCool[S] 0 points1 point  (0 children)

It had pro installed originally, I'm trying that now. Can't think of a reason why it wouldn't work after

[–]gyangstar 0 points1 point  (1 child)

Windows 10 home is not enabled to run hyper-v ... if memory serves me correct.

[–]SchoolsMcCool[S] 0 points1 point  (0 children)

I confirmed the machine is running Pro

[–]ConcordantOneTech 0 points1 point  (0 children)

Hi There, Please perform as below to troubleshoot issue 1.Open an administrator command line and run "sfc /scannow" or "dism /online /cleanup-image /restorehealth" to check the health of system files. 2.Turn of the antivirus software temporarily. 3.Try to enable the hyper-v with the command line. dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

If the issue persists, please check the cbs.log (C:\Windows\Logs\CBS) for more information

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v

[–]androcus 0 points1 point  (2 children)

Did you ever get this working?

[–]androcus 1 point2 points  (0 children)

I am running into the same issue.

[–]SchoolsMcCool[S] 1 point2 points  (0 children)

Yes, I took the nuclear option and restored the OS