I had a situation where a VM in Hyper-V on Win 10 Pro (build 19043.1415) wouldn´t stop and the first thing I did was stopping various services related to Hyper-V. After that I rebooted the host, and suddenly all my VM`s were no longer listed in Hyper-V. I thought this was weird, cause usually you´d expect these services to come back after a reboot. Anyway, I tried restarting services related to Hyper-V, but they all seemed to have a dependency, unnamed, prevending them from running. After a bit of trying to resolve it, I decided to simply uncheck Hyper-V as installed, reboot and then check it as installed + reboot again. Now I could see my machines again, but ran into a new problem: The virtual internal switch that I use for connecting through my VPN was gone. So I tried creating it, both with Hyper-V and from PowerShell, but with the same result:
New-VMSwitch -Name Intern -SwitchType Internal New-VMSwitch : Virtuelle Ethernet-switchforbindelser kunne ikke tilføjes. Intern miniport kunne ikke oprettes. Navn = '1F870B16-E6E9-4D9E-83EC-7A114ACB9A49', brugervenligt navn = '', MAC = 'DYN AMIC': Not found (0x80041002). At line:1 char:1 + New-VMSwitch -Name Intern -SwitchType Internal + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-VMSwitch], VirtualizationException + FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.NewVMSwitch
Please bear with the message being in Danish, but it´s basically telling that Virtual internet switch connections could not be added and the internal miniport could not be created. The same thing happened when trying to add an external switch. It takes up to 10 mins before I get the message btw. I found others with what seemed to be a similar problem, but here the solution was to remove Hyper-V (in already mentioned way) and do a netcfg -d, reboot, reinstall hyper-v and reboot, but this did not make any difference for me. I also found a quick fix from MS, that also did not improve my situation.
Some good ideas apart from reinstalling Windows?
Edit: Added list showing states of all hyper-v related services in my system.
Edit: Did a repair install of Win 10, but this did not solve the problem.
Edit: Did a sfc /scannow - same result.
Edit: Current output for relevant info from CoreInfo64:
HYPERVISOR * Hypervisor is present VMX - Supports Intel hardware-assisted virtualization SVM - Supports AMD hardware-assisted virtualization