Hyper-V Fails to Install on Windows 10 v.1909

Like the title says, Hyper-V fails to install on Windows 10 v.1909. [OS build 18363.592] It's a mystery to me, because I successfully installed and used Hyper-V on earlier versions of Windows.

Yes, I've got the necessary hardware and BIOS support (I successfully installed and used Hyper-V on earlier versions of Windows) and there are no other hypervisors currently installed. I disabled my anti-malware software (the same brand that I was using when I previously installed Hyper-V) and added the feature from an Administrators user account.

This may be a clue: Event Viewer only has one entry made at the time I tried to install Hyper-V, but it makes no sense (to me.) It's a 7043 Service Control Manager event that says the Hyper-V Virtual Machine Manager did not close following a pre-shutdown command, but I don't even have Hyper-V Virtual Machine Manager listed as a service.

If it matters (doubt it) the install failed at 98% and, of course, Windows rolled back any changes.

I'm open to any suggestions as to what I can try to get Hyper-V to install. Thanks for your help.

Bulldog said:

Like the title says, Hyper-V fails to install on Windows 10 v.1909. [OS build 18363.592] It's a mystery to me...

A mystery to me too, I've been running Hyper-V on two W10 Pro machines, both on 1909 (build 18363.592).

Event Viewer only has one entry made at the time I tried to install Hyper-V, but it makes no sense (to me.) It's a 7043 Service Control Manager event that says the Hyper-V Virtual Machine Manager did not close following a pre-shutdown command, but I don't even have Hyper-V Virtual Machine Manager listed as a service...

You should do if Hyper-V has been installed successfully. For reference, these are the services I have....




There is also the Hyper-V Manager, which is the virtmgmt.msc snap-in for the MMC management console.

Bree said:

You should [have the Hyper-V Virtual Machine Management service] if Hyper-V has been installed successfully.

I should ...if Hyper-V installed successfully. But it did not install successfully.

I'm thinking that the Event ID 7043 arose from the rollback ... Windows rolled back the unsuccessful attempt to install Hyper-V, so there was no Hyper-V Virtual Machine Management service to close.

At any rate, back to my original question: How can I persuade Hyper-V to install?

Bulldog said:

At any rate, back to my original question: How can I persuade Hyper-V to install?

I've just tested installing Hyper-V on a machine that has a clean install of 1909 (18363.628) and has never had Hyper-V installed before. It installed successfully and I created and ran a VM on it. So it's not a problem with 1909. What machine do you have? It may help diagnosis if you fill in your system specs here: https://www.tenforums.com/profile.php?do=extra


@Kari or @cereberus may have some ideas, but all I can suggest is you run SFC /SCANNOW to check the system is healthy.

Thanks very much for everyone's comments.

Most important was that you confirmed that Hyper-V can install on v.1909. This was not a surprise, since I successfully installed Hyper-V on an earlier version of Windows 10, but it was good to have that confirmation nonetheless.

I also tried to install Hyper-V after removing my anti-malware protection with the developer's own removal tool (Kaspersky Internet Security with kavremover) but that made no difference. I even temporarily disabled Windows Defender - that did not help either.

I followed your suggestions to run DISM and SFC. The result - no surprise to me - was "Windows Resource Protection did not find any integrity violations."

So I'm back to square one. I could do a clean install - I don't have confidence in repair installs - and I probably should at some point, since my last clean install was in 2016, when I clean installed Windows 10 in the first place. But a clean install is not a solution - it won't explain why I can't install Hyper-V - it's a do-over. So, for now at least, I'm going to continue looking for a solution.

If you're wondering "why doesn't he just install Virtualbox or VMWare?" the goal for me is not to run a virtual machine per se - been there, done that. It's specifically to learn about Hyper-V.

Bulldog said:

- I don't have confidence in repair installs -

An in-place repair install reinstalls Windows, resets a lot of the registry back to default and removes incorrect registry settings. I would try one, it's almost as effective a fix as a clean install but with the advantage of retaining your files and installed software.

Repair Install Windows 10 with an In-place Upgrade

I have narrowed the source of my inability to install Hyper-V.

First, to make a point: With greatest respect to all, a re-install is not in the cards. My computer is setup exactly as I like and that will take hours to re-do and check, so not going to happen.

By installing the Hyper-V components individually, I discovered that it's the Hyper-V Services that will not install:



Comparing my Hyper-V services to Bree's services (above) it's evident that I am missing two services.

Here's Bree:



and here's me:



so it's the Hyper-V Host Compute Service and/or the Hyper-V Virtual Machine Management service that will not install.

Not to be un-biblical, but in this case the truth is not setting me free. I am at a loss to understand why either or both of these services will not install, nor how to install them individually (and I don't hack my OS.) Suggestions are welcome, and in any case thanks for your patience.

Hi there
On a Physical machine I couldn't install the HYPER-V Hypervisor -- it was greyed out and I couldn't enter anything in the box -- the services etc installed. No other HYPERVISOR was running on this machine and VMWare not installed either.

It worked perfectly well on a NEW install of this build but not an upgrade. The upgrade version did originally have VMWare installed but I uninstalled that before attempting the upgrade. I'll have another go by re-installing NEW the current release of this build, and then doing an Upgrade before adding any "User" software.

I'm running W10 Pro Workstation edituion BTW.

Cheers
jimbo