Hi folks
Upgrading a Machine that didn't have VMWare installed on it -- HYPER-V installed OK (all components) and worked. So not sure what the problem is --seems some issues with VMWare 15.5 and HYPER-V even if not actually running any VMWare VM's.
Strange thing is that AFTER the upgrade you can install VMWare without any issue on the HYPER-V services -- you can't of course run concurrently VMWare VM's and HYPER-V ones though.
Cheers
jimbo
I appreciate everyone's contributions to this thread (even if I don't follow your advice.)
The Hyper-V services appear to install successfully, but then get rolled back during the required re-start. Same thing happens when I install the Hyper-V services in Safe Mode. Running with no third-party antivirus doesn't help.
I'm thinking that some Talisker might improve my chances. Certainly couldn't hurt.
Okay, so here's what happened.
I decided to do a clean install. Not because of my Hyper-V issue. Because it was time. My last clean install was back when I installed Windows 10 in the first place, and there have been 8 or 9 feature updates since then. So it was time.
The whole thing took almost 10 hours, which is as I suspected. And I will spend more time over the next few days getting everything to work the way I like and solving problems.
But at least I've got Hyper-V. Only now I'll never find out why it wouldn't install.
I actually kept the CBS log - don't know why I didn't think of that earlier - and started to work my way through it. If I can find out what happened I'll report back here.
Believe it or not, I actually read through the CBS log generated from my failed install of Hyper-V (from the bottom up, which is the correct way) and I think I can draw some conclusions.
Near the bottom of the log I found this error:HRESULT = 0x800f0826
I read that this error is typically caused by missing drivers. I might have brought this on myself by performing unwarranted 'maintenance' on my computer. Another lesson learned the hard way.
If this is, in fact, the reason Hyper-V failed to install, I also read that when this error occurs, the computer usually downloads and installs the software in question but then reverts back to the previous version of the Windows, which is what happened in my case.
However, there was also this error: HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED
I read that this error means that a request for the installation of the .Net Framework failed, was denied or did not complete. If installation of Hyper-V needed updates to my copy of the .Net Framework, that could account for the failure to install Hyper-V.
This error code, however, is not specific to .NET Framework only. And I don't know why .Net could not be updated, but I have read on other occasions that updating an existing install of .Net is an uncertain procedure. I remember having a heck of a time updating .Net 3.5 in Windows 8.1. For that reason, when I did my initial clean install of Windows 10, I made sure to install .Net 3.5 before installing any application software.
Thanks for the update, and thank you for spending more than a week reading through the CBS log - that's above and beyond the call of duty
Quote