locked
Can't enable Hyper V on Windows 10? RRS feed

  • Question

  • Hi All,

    I've just upgraded from Windows 8.1 Pro to Windows 10, and I'm having trouble enabling Hyper V from the 'Turn Windows Features on or off' section.   

    On reboot, after selecting the 'Enable' checkbox, it claims that the features couldn't be enabled and that it is reverting the changes. Another forum suggested disabling network adapters, which I did, but didn't seem to make any difference.

    Does anyone have any ideas or suggestions?

    Cheers,Brendan

    Sunday, August 23, 2015 9:53 AM

Answers

  • Your hardware must support virtualization, SLAT/EPT, and Data Execute Prevention.

    These need to be enabled in the BIOS and then cold boot.

    Do not select the checkbox to allow the role addition to create the first virtual switch.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Kevin Remde Monday, August 24, 2015 5:58 PM
    • Marked as answer by Zen the Ocelot Tuesday, September 1, 2015 5:34 AM
    Monday, August 24, 2015 5:51 PM

All replies

  • Hi All,

    I've just upgraded from Windows 8.1 Pro to Windows 10, and I'm having trouble enabling Hyper V from the 'Turn Windows Features on or off' section.   

    On reboot, after selecting the 'Enable' checkbox, it claims that the features couldn't be enabled and that it is reverting the changes. Another forum suggested disabling network adapters, which I did, but didn't seem to make any difference.

    Does anyone have any ideas or suggestions?

    Cheers,Brendan

    Saturday, August 22, 2015 7:40 AM
  • On Sat, 22 Aug 2015 07:40:38 +0000, Brendan Goden wrote:

    I've just upgraded from Windows 8.1 Pro to Windows 10, and I'm having trouble enabling Hyper V from the 'Turn Windows Features on or off' section.   

    On reboot, after selecting the 'Enable' checkbox, it claims that the features couldn't be enabled and that it is reverting the changes. Another forum suggested disabling network adapters, which I did, but didn't seem to make any difference.

    Does anyone have any ideas or suggestions?

    Please repost your question to the Windows 10 Virtualization forum:

    https://social.technet.microsoft.com/Forums/en-US/home?forum=win10itprovirt


    Paul Adare - FIM CM MVP

    Saturday, August 22, 2015 8:15 AM
  • Kindly go through the following article:

    How to setup a virtual machine using Hyper-V


    S.Sengupta, Windows Experience MVP

    Sunday, August 23, 2015 1:14 PM
  • Hi Brendan Goden,

    Have you got any error code or error messages? Did the hyper-v feature work well before on Windows 8.1 machine?
    Please try to update the BIOS and chipset drivers from the device manufacturer website and ensure the machine has been updated.
    We could run "dism/online/cleanup-image/restorehealth" to check the health of system files.
    To enable the hyper-v feature, we could try the following command line.
    dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, August 24, 2015 9:09 AM
  • Your hardware must support virtualization, SLAT/EPT, and Data Execute Prevention.

    These need to be enabled in the BIOS and then cold boot.

    Do not select the checkbox to allow the role addition to create the first virtual switch.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Kevin Remde Monday, August 24, 2015 5:58 PM
    • Marked as answer by Zen the Ocelot Tuesday, September 1, 2015 5:34 AM
    Monday, August 24, 2015 5:51 PM
  • Hi Brendan, did you get anywhere with this?

    I've got the same problem. However I upgraded from 7 home to 10 home and then to 10 pro.

    From "Turn Windows Features on and off" section I can install all the Hyper-V apps but not the Hyper-V services. When I try to install it does the reverting changes thing!

    I'm really annoyed because I upgraded from home to pro specifically for this feature. I've enabled it in the BIOS too.

    Saturday, August 29, 2015 8:49 PM
  •   There have always been problems with Hyper-V and upgrades. I remember upgrading Win 8.1 Home to Pro and not being able to enable Hyper-V on it.

      I would try a rebuild of the OS using the Windows 10 installation media from within the current OS. This gives you the option to retain current settings and programs. It fixed a few problems for me on an upgraded Windows 10 system.


    Bill

    Sunday, August 30, 2015 10:01 AM
  • Hi, you should investigate C:\windows\logs\cbs\CBS.log to find what exactly is failing.
    Sunday, August 30, 2015 5:11 PM
  • 2015-09-03 16:48:20, Info                  CSI    000000aa Performing 1 operations as follows:
      (0)  LockComponentPath: flags: 0 comp: {l:16 b:dfbfadcf46e6d001400000000c073007} pathid: {l:16 b:dfbfadcf46e6d001410000000c073007} path: [l:238{119}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.10240.16384_none_e4739596a56e9b02" pid: 70c starttime: 130857580990343532 (0x01d0e646cf18a96c)
    2015-09-03 16:48:20, Error      [0x01805b] CSI    000000ab (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_MOD_NOT_FOUND).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2015-09-03 16:48:20, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
    2015-09-03 16:48:20, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20150903112333.log to WER report.
    2015-09-03 16:48:20, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20150829040655.log to WER report.
    2015-09-03 16:48:20, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20150819042638.cab to WER report.
    2015-09-03 16:48:20, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20150813051712.cab to WER report.
    2015-09-03 16:48:20, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2015-09-03 16:48:20, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2015-09-03 16:48:20, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2015-09-03 16:48:20, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
    2015-09-03 16:48:20, Info                  CBS    Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 74.
    2015-09-03 16:48:20, Info                  CSI    000000ac Creating NT transaction (seq 2), objectname [6]"(null)"
    2015-09-03 16:48:20, Info                  CSI    000000ad Created NT transaction (seq 2) result 0x00000000, handle @0x2bc
    2015-09-03 16:48:20, Info                  CSI    000000ae@2015/9/3:12:48:20.652 Beginning NT transaction commit...
    2015-09-03 16:48:20, Info                  CSI    000000af@2015/9/3:12:48:20.683 CSI perf trace:
    CSIPERF:TXCOMMIT;31866

    Then further down:

    2015-09-03 16:48:24, Error                 CSI    00000107@2015/9/3:12:48:24.808 (F) Winsock Transports AI: status = ERROR_FILE_NOT_FOUND; message = [19]"Failed to get value"

    I do wonder if it's similar to the VMware issue where it can not create virtual network devices.

    • Edited by Zenettii Thursday, September 3, 2015 1:09 PM
    Thursday, September 3, 2015 1:08 PM
  • Zenettii, aren't you on build 10532 as mentioned in the other thread? This thread is about the RTM build.
    Thursday, September 3, 2015 1:13 PM
  • The paste above is from RTM. It's my primary machine that I've just upgraded from Windows home to Windows Pro today.
     I got a few machines.
    • Edited by Zenettii Thursday, September 3, 2015 1:50 PM
    Thursday, September 3, 2015 1:48 PM
  • Hi Brendan,

    Do you have specifics on your chipset? I am running an X58 chipset (an EVGA motherboard) and I wasn't able to do the upgrade from Windows 8.1 (where hyper-v worked fine) to 10 RTM without uninstalling hyper-v. Now that I am on 10, I cannot enable hyper-v without it rebooting a few times, eventually failing and having to boot into safe mode to shut it back off.

    In my case, Microsoft is aware of it and has taken some log files. My issue does sound a little different, though.

    As always, make sure your BIOS is at the latest version.

    Wednesday, September 9, 2015 2:48 AM
  • Hi Brendan,

    Do you have specifics on your chipset? I am running an X58 chipset (an EVGA motherboard) and I wasn't able to do the upgrade from Windows 8.1 (where hyper-v worked fine) to 10 RTM without uninstalling hyper-v. Now that I am on 10, I cannot enable hyper-v without it rebooting a few times, eventually failing and having to boot into safe mode to shut it back off.

    In my case, Microsoft is aware of it and has taken some log files. My issue does sound a little different, though.

    As always, make sure your BIOS is at the latest version.

    I've got the same motherboard and same problem.

    Thursday, October 8, 2015 11:49 AM
  • I ended up doing a clean install of Windows 10 pro in order to get Hyper-V to work.

    I was originally on 8.1 home, upgraded free to win 10 home, and then upgraded that via the windows store, to win 10 pro. It always failed to install the windows-service for hyper-v, but all other ticked boxes for hyper-v (in the turn windows features on/off) installed fine.

    Now a clean install directly to win10 pro, and it worked first time. Initially during the install, none of my license keys would work (win 8.1home, win 10 home, or win10 pro) but you can skip the key part and when windows logs in, it'll activate itself if you have a key on your windows login and the machine is recognised.

    • Proposed as answer by Zenettii Thursday, October 8, 2015 11:54 AM
    Thursday, October 8, 2015 11:53 AM
  • I ended up doing a clean install of Windows 10 pro in order to get Hyper-V to work.

    I was originally on 8.1 home, upgraded free to win 10 home, and then upgraded that via the windows store, to win 10 pro. It always failed to install the windows-service for hyper-v, but all other ticked boxes for hyper-v (in the turn windows features on/off) installed fine.

    Now a clean install directly to win10 pro, and it worked first time. Initially during the install, none of my license keys would work (win 8.1home, win 10 home, or win10 pro) but you can skip the key part and when windows logs in, it'll activate itself if you have a key on your windows login and the machine is recognised.

    I attempted to upgrade from 8.1 to 10 multiple times.  Every attempt ending up with the installer reverting back to 8.1.     I finally gave up on upgrades and did a clean install.    The clean install worked but I can't active Hyper-V without the boot loop.
    Friday, October 9, 2015 1:25 AM
  • how do i see if my pc supports data execute prevention 


    Monday, March 26, 2018 4:51 PM
  • run msinfo32

    The last four entries should all be Yes

    

    Monday, March 26, 2018 5:56 PM