An error occurred while attempting to connect to a Hyper-V server

Jul 4, 2017

While setting up a new Hyper-V failover cluster I got an error when trying to connect using the Hyper-V manager console:

An error occurred while attempting to connect to server “[computername]”. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.
Hyper-V encountered an error trying to access an object on Computer ‘[computername]’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.

There is nothing in the logs and everything I tried didn’t work. In the end uninstalling the Hyper-V role and reinstalling it did fix the issue. However, sometimes simply reinstalling roles is not possible. When I experienced the same error again on another machine I investigated a bit more and finally ended up in restoring the Hyper-V WMI registration which fixed the issue without reinstalling the role.

You can do so by running the following command in an elevated command prompt locally on the server where hyper-v is installed:

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



Did that help?

Buy me a coffeeBuy me a coffee

45 Comments

  1. Jesper on 04.10.2017 at 16:23

    Thanks, it worked perfectly! Thumbs up. :-)

  2. Dave84620 on 15.11.2017 at 15:23

    Thank you, that saved me a lot of time. I was about to re-install the whole machine to be sure that everything works fine. I assume that the error occured because I installed HPE Management Software which depends on WMI right after I installed the Hyper-V role. I wasn’t aware that this destroys the whole system ;o)

    Best regards
    Dave :o)

  3. Simon D on 23.12.2017 at 15:14

    Thankyou, you saved me a world of pain !

  4. Jeremy on 20.04.2018 at 02:15

    Thanks that worked perfectly.

  5. sandeep on 22.04.2018 at 18:03

    Thanks a lot. It worked for me too.

  6. GV on 02.05.2018 at 12:50

    Thanks!!

  7. Rune on 15.05.2018 at 16:15

    Thanks a lot.
    Worked like a charm.

  8. saraga on 28.05.2018 at 03:32

    Thanks a lot.

  9. Greg on 29.06.2018 at 16:59

    Just had the issue today. Did a google search and your article came up on top. Lucky me. This fixed it. Thank you.

  10. Martijn Daas on 16.07.2018 at 21:58

    Thank you!
    As somebody mentioned here also, it has something to do with installing HPE System Management Homepage after installing Hyper-V.
    Nice find, thumbs up.

  11. Ceraz24 on 21.07.2018 at 16:11

    I can confirm this fixed it for me as well. I had the Homepage already installed but only when I installed the WBEM Provider Packager – cp031735 the error occured (for me at least)

    Cheers

  12. ernesto on 24.07.2018 at 19:19

    before doing this, use your domain administrator credentials if you have one if not use this command.

  13. Yevgeny on 30.07.2018 at 20:12

    I got messege: file not found.

  14. Guruprasad on 31.07.2018 at 16:21

    File ‘C:\WINDOWS\System32\WindowsVirtualization.V2.mof’ not found!

  15. Bruno Moura on 11.09.2018 at 00:53

    UAU!! Thanks!!

  16. Dan Regalia on 18.09.2018 at 07:52

    Got this as a reply: Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof
    Microsoft (R) MOF Compiler Version 10.0.17134.1
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: C:\WINDOWS\System32\WindowsVirtualization.V2.mof
    MOF file has been successfully parsed
    Storing data in the repository…
    An error occurred while opening the namespace for object 1:
    0X80041002 Class, instance, or property ” was not found.
    Compiler returned error 0x80041002
    PS C:\WINDOWS\system32>

  17. Eddie on 21.09.2018 at 12:25

    Thanks for this article, it fixed the issues I was having with HyperV manager and HyperV 2016 core server.

  18. Jeff on 10.10.2018 at 20:39

    Worked perfectly! Thanks for posting!

  19. JonR on 27.10.2018 at 17:57

    Wow. Thank you for this simple and effective article. Also happened after HPE software install.

  20. Jason H on 14.11.2018 at 01:28

    This fixed it! Thanks! Issue occurred on 11/13/2018 spontaneously on a computer I use Hyper-V on extensively. I literally had several VMs already open, left for a meeting, and came back to this error. Rebooting did not solve it. This did.

  21. a.t on 06.03.2019 at 15:26

    thanks a lot, worked like a charm. i appreciate you saving the hair on my head.

  22. Kevin A on 28.03.2019 at 21:36

    The suggested command did not work for me. For those who fall into this category, I resolved by opening Powershell on the host and typing > enable-psremoting -force. This will make the appropriate exceptions in your client firewall.

  23. Stephen on 28.05.2019 at 16:40

    Great Solution! Many Thanks. I had the issue when the drive hosting my VM’s failed. I replaced the drive, but couldn’t subsequently connect to the Hypervisor.

  24. bo on 04.07.2019 at 09:22

    File ‘C:\Windows\System32\WindowsVirtualization.V2.mof’ not found!

    How to Solve the Problem？

  25. jacob on 19.08.2019 at 19:18

    also, i found that i had set a static entry in a hosts file but the hv-server was setup on dhcp; so assigning it the correct static ip address worked as I was trying to connect to the wrong system

  26. Nithin on 03.09.2019 at 22:04

    This fixed my issue too. Thanks!

  27. Emil on 18.09.2019 at 13:38

    Worked for me perfectly. God bless save me sleepless nights. Thanks you !

  28. Rod on 15.10.2019 at 17:48

    You save my time thank you

  29. miro on 26.10.2019 at 03:01

    OMG, why does Microsoft not do something and write up a knowledge based article that links to this website since so many people, including me, have experienced this ongoing issue. Server is 2019 and the issue is still present 2 years running!

  30. Anonymous on 17.12.2019 at 21:47

    thanks was looking for this for past 8 hours.

  31. Speedy on 27.03.2020 at 08:31

    Thanks!

  32. Mike D on 15.04.2020 at 23:36

    Worked perfectly. Good find and thanks for posting it.

  33. Patrick K. on 22.04.2020 at 07:40

    Searched for hours for a solution. Your command line did the job in seconds. Thanks a lot.

  34. Jamie on 14.05.2020 at 16:57

    Thanks, This seemed to happen once I installed the HPE Proliant Support Pack….

  35. Gary R on 16.07.2020 at 12:51

    Absolute star!
    I can confirm this fixed it for me as well. I had the Homepage already installed but seemed to break HV when I installed the WBEM Provider Package – cp037689 on Server 2019

  36. Antec on 17.11.2020 at 19:06

    Thank you! worked perfect! Server 2016

  37. Nathan Ashe on 17.11.2020 at 23:25

    I’ve found this solution many times, however non of them state if you run that command on the Server your trying to connect FROM or the server your trying to connect TO.

    I have just done it on both, without any luck.

  38. Anthony Feghaly on 26.11.2020 at 22:31

    It worked for me perfectly, Thank you

  39. Simon on 14.03.2021 at 23:23

    Thanks was driving me crazy this nailed you are a top banana!!!

  40. Anonymous on 05.05.2021 at 03:22

    Thank you, it worked!

  41. Elias on 28.07.2021 at 10:02

    Great. It worked. Thanks

  42. Monica on 12.10.2021 at 20:54

    This worked for me! Thank you!

  43. Raj on 28.12.2021 at 16:26

    wow! this MOF thingy worked perfectly and immediately fixed the issue. Been searching for hours. Thanks a lot

  44. Anonymous on 23.05.2023 at 10:34

    I love you!
    1 billion thanks

  45. Anonymus on 09.11.2023 at 10:37

    I love you man saved me!

Trackbacks/Pingbacks

  1. Correcting Hyper-V Management Errors (Server 2016) | PoeticsOnline.Net - […] the management console to start without error. Thus, I could continue my work. A big thank you to Norman…

Submit a Comment

Your email address will not be published. Required fields are marked *