Can't connect to Hyper-V Manager after inplace upgrade

[AJWhite1970]

Firstly, yeah I know inplace OS upgrades are bad, TBH I'd forgotten I'd had Hyper-V on this box until after the upgrade

 

So, inplace upgraded Server 2012R2 to Server 2016 and everything went fine. Hyper-V was loaded but no guest hosts were powered on at the time, this is just a little used server. Post upgrade I installed KB4019472 to bring it up to date (May 2017 roll-up) and then loaded Hyper-V Manager to connect to local server I get the error message

 

 

I've checked the Hyper-V role is installed which it is and the Hyper-V Virtual Machine Management service is running. Also checked Authorization Manager to make sure the domain administrator account was in Role Assignment Administrator which it is.

 

So I'm stuck. Any magic way to get this up and running again?

 

And yes, I know OS inplace upgrades are bad....

Cheers

Andrew

[TwistedHelixis]

I assume you checked the vm settings as adapter issues etc will cause a vm to fail

 

Do you have another server you can put hyper-v on? if so, you could try and move the vhd disks to the new server and install a new vm using the old disks. Once that is up and running you can play with the faulty hyper-v

[FN-GM]

Did you team any NICS? If so in place upgrades are not support on Team Nics. If you did have them teamed, you will need to recreate the team, no major issue.

[AJWhite1970]

Hi. Nope, just a single NIC, nothing fancy on this box like teaming etc.

[AJWhite1970]

OK, fixed it after a lot of google dead-ends I found an old doc where someone suggested this command line which got the manager back-up and running

 

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

 

Thanks for taking the time to post

Andrew

 

 

 

 

[andydis]

export the vm's and reinstall Hyper-v role?