34 Comments

1. Jesper on October 4, 2017 at 16:23

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

2. Dave84620 on November 15, 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 December 23, 2017 at 15:14

   Thankyou, you saved me a world of pain !

4. Jeremy on April 20, 2018 at 02:15

   Thanks that worked perfectly.

5. sandeep on April 22, 2018 at 18:03

   Thanks a lot. It worked for me too.

6. GV on May 2, 2018 at 12:50

   Thanks!!

7. Rune on May 15, 2018 at 16:15

   Thanks a lot.
   Worked like a charm.

8. saraga on May 28, 2018 at 03:32

   Thanks a lot.

9. Greg on June 29, 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 July 16, 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 July 21, 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 July 24, 2018 at 19:19

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

13. Yevgeny on July 30, 2018 at 20:12

    I got messege: file not found.

14. Guruprasad on July 31, 2018 at 16:21

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

15. Bruno Moura on September 11, 2018 at 00:53

    UAU!! Thanks!!

16. Dan Regalia on September 18, 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 September 21, 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 October 10, 2018 at 20:39

    Worked perfectly! Thanks for posting!

19. JonR on October 27, 2018 at 17:57

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

20. Jason H on November 14, 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 March 6, 2019 at 15:26

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

22. Kevin A on March 28, 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 May 28, 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 July 4, 2019 at 09:22

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

    How to Solve the Problem？

25. jacob on August 19, 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 September 3, 2019 at 22:04

    This fixed my issue too. Thanks!

27. Emil on September 18, 2019 at 13:38

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

28. Rod on October 15, 2019 at 17:48

    You save my time thank you

29. miro on October 26, 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 December 17, 2019 at 21:47

    thanks was looking for this for past 8 hours.

31. Speedy on March 27, 2020 at 08:31

    Thanks!

32. Mike D on April 15, 2020 at 23:36

    Worked perfectly. Good find and thanks for posting it.

33. Patrick K. on April 22, 2020 at 07:40

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

34. Jamie on May 14, 2020 at 16:57

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