text: Scenario
  The common urge by many is to simply take a hammer to WMI and either rebuild the repository or recompile all of the .mof files in the C:WindowsSystem32Wbemfolder. While the hammer may seem a good approach to solve your problem in some cases or what seems like a quick fix, it can actually cause more problems and issues that are not immediately visible or felt. These newly created problems as a result of the hammer approach are not always immediately obvious and tend to surface later, and usually when the last thing you need is another problem to have to deal with on your plate, especially if it created a critical business situation.
  Rebuilding the repository or recompiling all of the .mof files as a first action when other steps should be taken first can cause damage to the system and/or to installed applications.
  First we want to just check right up front if our repository is corrupted or not to save time, then continue from there with appropriate actions.
  Check the Windows Application log, look for events in the past week where Source = Microsoft-Windows-WMI, check if any of the following WMI event IDs exist: 28, 65, 5600, 5601, 5614. Any of these could indicate a WMI repository or core infrastructure problem.
  Check if the repository is corrupted or not by running following command from command prompt with admin rights: winmgmt /verifyrepository. If it is corrupted the returned result will be “Repository is inconsistent.” If it comes back as consistent, then repository is not corrupted so do not rebuild repository at this point.
  Note: if results came back as “inconsistent”, then skip to bottom of the page and reference the section titled “Wmi Repository Corrupted”, otherwise continue with the methods below.
  If issue is with a 3rd party provider or namespace, the vendor should be engaged as they are responsible for their own namespaces and providers..
  When a quota issue is hit in wmiprvse, new memory allocations fail and based on where the failure happen client gets different errors “invalid query”/Invalid class/Provider load failure/quota check”
  When a quota issue is hit when a new operation is for a provider which is not loaded already in wmiprvse and thus requiring it to be loaded in a new instance of wmiprvse, then the provider loading would fail with “provider load failure”. namespace.
  - Click on the Security tab and expand Root folder. This is where you will see all of the namespace listed for WMI
  - Find the namespace referenced in the error message you are getting
  - If you find the namespace is missing, do the following, otherwise skip to step 6 if the namespace is listed
  a.hangs.
  Join the conversationAdd Comment
  That would do it, but if it comes back refer to my blog for troubleshooting.
  Jeff Worline MSFT
  @eazlan: Try stopping/disabling the WMI service first.
  I got a "WMI Error: 0x8004106C Description: Quota violation, while running WMI queries"
  I did not want to get the administrator mad at me and restart the server, so I just restarted the "Windows Management Instrumentation" service.
  Hi, after run winmgmt /verifyrepository command, i get this error
  WMI repository verification failed
  Error code: 0x80041003
  Facility: WMI
  Description: Access denied
  So I'm unsure how to move forward since I did get an error on the last step of scenario #2. In my case, any of the MSFT_NetLbfoTeam_Provider classes give me an error when I click on "Instances" The error is "Number: 0x8004100c Facility: WMI Description:
  Not supported. The issue is that I'm unabled to manage Windows NIC Teaming. How do I troubleshoot this? Thanks!
  On Win 2008 standard I am getting: Volume Query Failed. WMI Query failed. Provider Failure – When opening Share and Storage management. Yet running through what you list here I ran WMIMGMT.msc and shows no error so nothing to look for under securty>root.
  winmgmt /verifyrepository shows consistent
  In eventviewer I see:
  Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: HandleCount Value: 4457 Maximum value: 4096 WMIPRVSE PID: 7884
  And I am getting a string of these in the log of wmidiag they are repeated a dozen times
  ERROR(S)!
  (0) ** – Root/CIMV2, Win32_PerfFormattedData_ESENT_Database, 0x80041002 – (WBEM_E_NOT_FOUND) Object cannot be found.
  (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  Root/CIMV2, Win32_PerfRawData_ESENT_Database, 0x80041002 – (WBEM_E_NOT_FOUND) Object cannot be found.
  (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  If you failed installing sccm client with message
  “File C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603Action: ErrorMessages: ”
  and error number in MicrosoftPolicyPlatformSetup.msi.log
  “0x80041013”
  try removing application “Google Desktop” or “Windows Eyes”
  I ran into invalid namespace error for “root\virtualization” namespace on win2k12 machine.
  I tried finding the corresponding *.mof file for virtualization namespace on msdn.com, but couldnt find anything. Any help is greatly appreciated!