Hyper-V virtualization - Setup and Use in Windows 10  

Page 42 of 43 FirstFirst ... 3240414243 LastLast

  1. Posts : 19
    Windows 10 Pro, 1709
       #410

    Hyper-V virtualization process reverses back at the end of rebooting


    Hi,

    I have Windows 10 Pro 1709 with virtualization activated in BIOS.

    The virtualization process runs fine until restarting after "completing the requested changes" under the Windows Features. During the restart it finalizes 95% of the changes but then it says it "can't complete the changes" or something alike, and says it's reversing the changes back. After that it reboots again 2-3 times to complete the reversing.

    So I approached again the Windows Features and re-enabled the Hyper-V. But now I noticed that the Hyper-V doesn't get fully enabled as it's shown in the tutorial. It gets only partially enabled (I don't know how it was at my first trial which failed as mentioned above). Please see the attached photo below. I don't know why it gets just partially enabled and not fully. Any ideas ?? Perhaps that's why it didn't complete the changes.

    Name:  Hyper-V Windows Feature box.jpg
Views: 81
Size:  67.8 KB
      My ComputerSystem Spec

  2. johngalt's Avatar
    Posts : 1,711
    WinX Pro x64 IP current
       #411

    newu873 said: View Post
    Hi,

    I have Windows 10 Pro 1709 with virtualization activated in BIOS.

    The virtualization process runs fine until restarting after "completing the requested changes" under the Windows Features. During the restart it finalizes 95% of the changes but then it says it "can't complete the changes" or something alike, and says it's reversing the changes back. After that it reboots again 2-3 times to complete the reversing.

    So I approached again the Windows Features and re-enabled the Hyper-V. But now I noticed that the Hyper-V doesn't get fully enabled as it's shown in the tutorial. It gets only partially enabled (I don't know how it was at my first trial which failed as mentioned above). Please see the attached photo below. I don't know why it gets just partially enabled and not fully. Any ideas ?? Perhaps that's why it didn't complete the changes.

    Name:  Hyper-V Windows Feature box.jpg
Views: 81
Size:  67.8 KB

    Hi there,

    As a quick first check to verify that your BIOS is, in fact, working correctly and enabling Virtualization in the BIOS actually enabled it, can you get the Securable utility from GRC and run it as admin and verify that it shows the architecture and then Yes twice? Use the link below.

    GRC

    The reason I ask is that certain boards / chipsets combinations led to a bug that was never really quite fixed (mostly much older boards) so that enabling VTx was actually disabling it. This will help eliminate a mis-reporting BIOS from the troubleshooting steps.
      My ComputersSystem Spec


  3. Posts : 19
    Windows 10 Pro, 1709
       #412

    johngalt said: View Post
    Hi there,

    As a quick first check to verify that your BIOS is, in fact, working correctly and enabling Virtualization in the BIOS actually enabled it, can you get the Securable utility from GRC and run it as admin and verify that it shows the architecture and then Yes twice? Use the link below.

    GRC

    The reason I ask is that certain boards / chipsets combinations led to a bug that was never really quite fixed (mostly much older boards) so that enabling VTx was actually disabling it. This will help eliminate a mis-reporting BIOS from the troubleshooting steps.
    Hi,

    Thanks for replying. I will do your advise. But meanwhile just 1 comment and 2 questions:

    Comment: My desktop is fresh new from Dell. So I guess its motherboard is not old.

    Questions:
    1. Is there a log file which got created during my virtualization which failed ??
    2. After I run the GRC, do you need a screenshot or log, etc., to see ??
      My ComputerSystem Spec

  4. johngalt's Avatar
    Posts : 1,711
    WinX Pro x64 IP current
       #413

    Re: Log file: Not sure about that, will have to research. I'm sure that people who make use of Hyper-V on WinX will have more of an idea (I used to use it but my ancient system is simply too overtaxed to continue to make use of it, so since my last clean install I have not enabled it).

    Re: Securable - no, unless you really want to include the screenshot, just a verification that you have 64 / Yes / Yes showing will be fine.

    As for your system being new - Since my own system is, as I referred to above, ancient, I know all about its idiosyncrasies, but I have very little clue about newer systems, as I don't have direct physical access to them to play around with :)

    That being said, I cannot confirm nor deny that such a bug as exists in my system also exists in yours.

    Finally, it might also be a good idea to edit your system specs under your profile - go to the top of the page, hit the Settings link / button (depending upon which board skin you're using), and then select the Edit System Spec from the navigation menu on the left to edit your specs. That will probably go a long way to help troubleshooting as well. It includes not only information about the system itself, including peripherals, but also OS (and please be specific where you can - e.g. for OS, Windows 10 (Home / Pro) and build version, instead of just saying Windows 10).

    Here is a tutorial to help you with that task: System Specs - Fill in at Ten Forums | Tutorials
      My ComputersSystem Spec


  5. Posts : 19
    Windows 10 Pro, 1709
       #414

    johngalt said: View Post
    Re: Log file: Not sure about that, will have to research. I'm sure that people who make use of Hyper-V on WinX will have more of an idea (I used to use it but my ancient system is simply too overtaxed to continue to make use of it, so since my last clean install I have not enabled it).

    Re: Securable - no, unless you really want to include the screenshot, just a verification that you have 64 / Yes / Yes showing will be fine.

    As for your system being new - Since my own system is, as I referred to above, ancient, I know all about its idiosyncrasies, but I have very little clue about newer systems, as I don't have direct physical access to them to play around with :)

    That being said, I cannot confirm nor deny that such a bug as exists in my system also exists in yours.

    Finally, it might also be a good idea to edit your system specs under your profile - go to the top of the page, hit the Settings link / button (depending upon which board skin you're using), and then select the Edit System Spec from the navigation menu on the left to edit your specs. That will probably go a long way to help troubleshooting as well. It includes not only information about the system itself, including peripherals, but also OS (and please be specific where you can - e.g. for OS, Windows 10 (Home / Pro) and build version, instead of just saying Windows 10).

    Here is a tutorial to help you with that task: System Specs - Fill in at Ten Forums | Tutorials
    I ran the Securable from GRC and it gave positives to all, BUT with comments regarding the virtualization.

    Parts of the comment rise doubts for me. I give full quote of the comments:

    "This processor does offer advanced hardware support for virtualization. However, while running under a 64-bit version of Windows this program cannot execute its 32-bit kernel code to determine whether Intel's VMX virtual machine extensions are being locked on, locked off, or neither. Since there's a chance that your system's BIOS may be deliberately disabling support for hardware virtualization (some do) you should re-run this program, if possible, with administrative privileges under a 32-bit version of NT, XP, or Vista. That will allow SecurAble to run a bit of kernel-mode code in order to determine exactly what's going on. (Note that you can also poke around in your system's BIOS to see whether you're able to find any references to "hardware virtualization" or "VMX", etc."
      My ComputerSystem Spec

  6. johngalt's Avatar
    Posts : 1,711
    WinX Pro x64 IP current
       #415

    I get the same when I click on the second Yes (Hardware Virtualization).

    Interestingly enough, though, you listed Windows 10 Pro version 1709 - which, at this point in time, is actually over a year old.

    What model Dell is this?
      My ComputersSystem Spec


  7. Posts : 19
    Windows 10 Pro, 1709
       #416

    johngalt said: View Post
    I get the same when I click on the second Yes (Hardware Virtualization).

    Interestingly enough, though, you listed Windows 10 Pro version 1709 - which, at this point in time, is actually over a year old.

    What model Dell is this?
    Dell Vostro 3668

    I have reversed 1 step back with the Windows 10 version. Originally I had 1803.
    Meanwhile just now I found on other forum some suggestion. I shall try it. It's on:
    Virtual machine could not started because the hypervisor is not running

    There's a suggestion to run the command:
    BCDEDIT /Set {current} hypervisorlaunchtype auto
    By David Johnson, CD, MVP
      My ComputerSystem Spec

  8. johngalt's Avatar
    Posts : 1,711
    WinX Pro x64 IP current
       #417

    First just run BCEDIT from an *Elevated* CMD / PowerShell prompt (Fastest way to get to that is to *right* click the start button, and select CMD (Admin) / Windows PowerShell (Admin), whichever shows in that popup. Alternatively, you could click hte start button, start typing CMD (or PowerShell), then when it shows as a program entry, right click and select run as administrator.

    If BCDEDIT shows
    Code:
    hypervisorlaunchtype    Auto
    near the bottom then it is already enabled.

    However, I suspect this may not lead anywhere, as the user in question had it working fine, as his last post shows - he was trying to connect to a non-existent hypervisor, which assumes that his installation (as seen in the screenshots) was already working.

    That post, however, does give a good idea - to look at the Event Log and see what happened when you were trying to enable it.

    I'm actually beginning to suspect it might have to do with the Dell installation of Windows 10 itself (more specifically, with some sort of Group Policy that might be enabled on their OEM build). I'll research your particular machine and see if it leads me anywhere.

    Also, could you more fully explain how you downgraded from 1803 to 1709?
      My ComputersSystem Spec

  9. johngalt's Avatar
    Posts : 1,711
    WinX Pro x64 IP current
       #418

    In looking up your system, yes, it is pretty new (the owners' manual is dated Dec 2016), so we need to make sure that the BIOS settings are, in fact, correct. Did you alter anything in the BIOS when you were in there at all, or just verify that the *2* settings related to VTx were both enabled?

    Here is the Owner's manual for your machine: https://topics-cdn.dell.com/pdf/vost...nual_en-us.pdf

    According to this, by default both of those settings should be enabled (See page 53)
      My ComputersSystem Spec


  10. Posts : 19
    Windows 10 Pro, 1709
       #419

    johngalt said: View Post
    In looking up your system, yes, it is pretty new (the owners' manual is dated Dec 2016), so we need to make sure that the BIOS settings are, in fact, correct. Did you alter anything in the BIOS when you were in there at all, or just verify that the *2* settings related to VTx were both enabled?

    Here is the Owner's manual for your machine: https://topics-cdn.dell.com/pdf/vost...nual_en-us.pdf

    According to this, by default both of those settings should be enabled (See page 53)
    Thanks for tips & care. Before I proceed with them, few answers:

    Yes, I found that my system was OFF for the <hypervisorlaunchtype>. So I shall give it a try for the command although I too saw it didn't help that person. It's interesting he has HP (mine Dell). So it means perhaps the problem is not a Vendor-specific.

    I downgraded my PC through Windows 10 settings -- just chose there the "reverse version" or something alike and then Windows did all the work.

    At the last time I haven't done anything to BIOS. I just checked the Virtualization is enabled. But at first weeks I tried there various things, mostly tried the various boot options -- safe boot, Legacy boot, etc. Once I restored there the default settings. Later I have upgraded the BIOS as Dell have recommended on their site for my desktop model. I also upgraded the Chipset driver as they recommended with that. I don't remember seeing any VTx in BIOS. I need to read the manual.

    Right now I have to delay all the tests and checking. I shall go through all of them later today.
      My ComputerSystem Spec


 
Page 42 of 43 FirstFirst ... 3240414243 LastLast

Tutorial Categories

Hyper-V virtualization - Setup and Use in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


Related Threads
I've been using Windows 7 Home Edition 64bit since it's release &, by in large, I'm pretty pleased with it. During a motherboard change & RAM upgrade to 32G, I upgraded to Windows 7 Pro (to enable all RAM to be used) which I choose in preference to...
Used this tool, Download Microsoft® Hardware-Assisted Virtualization Detection Tool from Official Microsoft Download Center No go VMware said the same thing boo-hoo anyone have instruction to enable in bios ? Spec's are added, Cheers.
Hi I'm getting there, I've downloaded the .ISO file, I've made 2 images of my C:\ drive (using 2 different backup programs) and I've created a 100 GB partition on my second hard drive labeled Windows 10. Now I'm going to create the install...
Solved Windows 10 and Hyper-V in Installation and Upgrade
I tried to install the preview as a virtual machine and everything went fine until after a reboot following the download and installation of the updates. Both 8.1 & 10 locked up with a strange crackling noise through the speakers every few seconds....

Tags for this Thread

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:24.
Find Us