80041010: The specified class is not valid

80041010 – The specified class is not valid

This is quite an ambiguous message, as there can be different causes to it, among which are:

• If certain services (for example, Exchange) are not started when the WMI AutoDiscovery/AutoPurge (ADAP) process is started, the performance counters are not transferred to WMI because WMI uses ADAP to build its internal performance counter table. Follow the steps below to fix this. For more details, please see this article (deprecated, but still available via archive.org and the information is still valid).
  • Open a command console.
  • Execute wmiadap.exe /f
  • Start WMI.

• Performance Counters are disabled for a specific service. There is a registry entry for WMI counters for each service. To check and fix this you have to edit the Windows registry. For more details, please see this article (deprecated, but still available via archive.org and the information is still valid).
  Caution: Please back up your system before manipulating the Windows registry!
  • Key: HKLM\SYSTEM\CurrentControlSet\Services\Service-name\Performance
  • Data type: REG_DWORD
  • Range: 0|1
  • Default value: 0
  • According to Microsoft: "If the value of this entry is 1, then the Performance Library (Perflib) does not retrieve performance data about these counters from the registry. As a result, System Monitor and other tools that use the data cannot display it. Instead, the tools display a value of 0 or 100 percent, depending on the counter."
  • To activate changes, restart the Windows computer.

See also the article What are the most common errors when monitoring WMI?

Also, we would suggest following the order defined in the WMI repair list.

OK, I understand that we need to follow, can you be specify in what needs to be followed?

The list is pretty much arranged in the order that it is intended to be followed. So, proceed on all relevant entries from top to bottom.

FYI - The first microsoft link is broken. The 2nd takes you to a page to download ALL old content to 2003 KB articles.

Thank you, Peter, we have updated the article.

All the article links are now dead.

Fixed the links pointing to archive.org, working again.

I'm having this problem now too, I tried all the suggestions on this page and on this one: https://kb.paessler.com/en/topic/3713-i-have-tried-a-lot-of-things-to-fix-my-wmi-what-else-can-i-try-to-avoid-reinstalling-windows

with no luck, any other suggestions?

I was able to fix the problem on the server by following the instructions in Sabrina Shen’s post on technet here: https://social.technet.microsoft.com/Forums/Lync/en-US/3c869f91-59a5-4b03-8609-a7e3913c3b4a/failed-to-initialize-all-required-wmi-classes-on-primary-server?forum=configmgrgeneral Note the for command needs to be run in your WMI repository folder (which for me was c:\windows\system32\wbem)

Restart the WMI service

Run the command: winmgmt /salvagerepository

Next:

winmgmt /resetrepository

for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

Note, that broke ATA on the same server, I had to rebuild my repository again while the service was off:

Sc config winmgmt start= disabled
Net stop winmgmt /y
Winmgmt /resetrepository
Sc config winmgmt start= auto
Net start winmgmt