Running Windows 10 Pro, v1803 OS 17134.648, 64-bit.

I am having a problem with machines that I've previously installed into Hyper-V. I have successfully uninstalled Hyper-V, and have manually removed all vEthernet related NICs. From previous experience of going through this process, if I reinstall Hyper-V, it will remember a number of settings from the previous install, including but not limited to the VMs I had installed (which I have exported to a different location.)

What I want to do now that Hyper-V is uninstalled is to do a clean sweep of all settings. Find registry keys and delete them or reset them to the values they were at when I first enabled the Hyper-V feature. Same with any .vhd*, .avhd*, .xml, etc. files.

I need to get Hyper-V to a state where a new Quick Create VM from a clean (not imported) source runs clean (no boot issues), then I can look to import my exported VMs.

These are the (unsuccessful) steps I have taken so far in an attempt to reset everything back to "factory":

  • Uninstall Hyper-V using Windows Features
  • [Reboot]
  • Rename C:\ProgramData\Microsoft\Windows\Hyper-V folder
  • Rename C:\Users\Public\Documents\Hyper-V folder, if it exists
  • Rename C:\ProgramData\Microsoft\Event Viewer\Applications and Services Logs\Microsoft\Windows\Hyper-V-Hypervisor, if it exists
  • Rename C:\ProgramData\Microsoft\Event Viewer\Applications and Services Logs\Microsoft\Windows\Hyper-V-Worker, if it exists
  • Rename C:\Users[logged_in_user]\AppData\Roaming\Microsoft\Windows\Hyper-V
  • In Control Panel\All Control Panel Items\Network Connections
    • (Right-click Start icon, select Network Connections. Select Ethernet in the left navigation bar, then Change Adapter Options)
    • right-click on "vEtnernet (Default Switch)", Properties, Configure..., Driver, Uninstall Device
  • RegEdit (as Admin)
    • Change owner of HKLM\SOFTWARE\Classes\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6} from TrustedInstaller to Administrators
    • Confirm that HKLM\SOFTWARE\Classes\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}\TypeLib Default value is {565783C6-CB41-11D1-8B02-00600806D9B6} - Change HKLM\SOFTWARE\Classes\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}\InProcServer32\ThreadingModel from Apartment to Both
    • Add HKLM\SOFTWARE\Classes\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}\AppID = {76A64158-CB41-11D1-8B02-00600806D9B6}
    • Add HKLM\SOFTWARE\Classes\AppID\{76A64158-CB41-11D1-8B02-00600806D9B6} Subkey
    • Add empty string value HKLM\SOFTWARE\Classes\AppID\{76A64158-CB41-11D1-8B02-00600806D9B6}\DllSurrogate
  • After doing all of this, found https://wiki.abiquo.com/display/ABI26/Hyper-V+Cloud+Node+Configuration, where they automate all of the above in a Powershell Script and Registry Import file
    • Download and run the script to ensure I didn't mess anything up.
    • (Other options don't apply to Windows 10 Pro, or running Hyper-V locally, or when Hyper-V hasn't been installed yet.)
  • [Reboot]
  • Reinstall Hyper-V using Windows Features
  • [Reboot]
  • I found blogs.technet.microsoft.com/canitpro/2012/09/11/…, and I have renamed the existing Hyper-V folders. I am going to reinstall and see if anything is remembered. However, if there are still remembered settings, I'll be back here looking for more direction. Mar 26, 2019 at 16:38
  • 1
    Perhaps you should be asking about the actual problem instead.
    – Daniel B
    Mar 28, 2019 at 21:28
  • 1
    I asked about the actual problem in this SO posting, which also has a bounty, so this one is specifically reserved to only resetting Hyper-V, which others have also asked for in the past (but got answers regarding their specific issue, which didn't help me at all). Mar 28, 2019 at 22:03
  • 1
    @pimp-juice-it, I have previously run these steps, but for the sake of completeness (and because of, well, you know, Microsoft), I'll try the steps again, and maybe this time they will produce the results I'm looking for. I'll report back with the results. Apr 1, 2019 at 18:35
  • 1
    @pimp-juice-it, as suspected, while this allows me to uninstall Hyper-V (which I could not do about 3 weeks ago because of problems with a corrupted DISM), these steps do not actually reset the Hyper-V settings. The virtual machines that were in place still exist in the associated Hyper-V folders, and the setting which is causing my real problem (“failed to power on: system cannot find the path specified”) still persists. Thanks for the try, though. Apr 1, 2019 at 20:44

2 Answers 2


I'm pretty sure you just delete the configs and the dir content.

You can force it with dism

dism /online /Disable-Feature /FeatureName:Microsoft-Hyper-V

then just

dism /online /Enable-Feature /FeatureName:Microsoft-Hyper-V

  • 1
    Thanks, but no, this isn't the answer. I have tried all 3 routes to installing/uninstalling Hyper-V (using Windows Features, using Powershell, and using dism), deleting all pertinent files/folders after each uninstall, and while Hyper-V installs/uninstalls "fine", there are still settings somewhere that aren't getting reset. Apr 10, 2019 at 16:36
  • 1
    Thanks this not only worked for me but for some reason cut down Hyper-V's memory utilization down to half. I went from 11GB memory usage on a cold system startup down to only 4GB. Feb 21, 2020 at 10:40

Thanks to all who tried to help, but I have since abandoned this entirely. I have purchased a new machine, which I will be installing a new Windows 10 environment onto, and will start Hyper-V completely from scratch on that box, then after confirming that Hyper-V functions correctly, I will import my VMs to there.

  • 1
    While I entirely agree that this answer is a horrible answer, and Microsoft really does need to fix this (because "you're screwed, dude, buy a new machine" is never an answer) realize that I started searching on March 16th, and gave up on April 10th. That was almost a month of hand-wringing and searching with no solution in sight, and this was only last year... :-( Aug 10, 2020 at 23:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.