There are a lot of WMI errors out there. Way too many, right?

Quick fix

The WMI error 5858 is a common issue occurring while using the Windows server with applications that use IWbemServices:ExecQuery. The error message pops up in the Event Viewer and shows the Event ID 5858 resulting in different ResultCodes, for example “Result Code = 0x80041032 (WBEM_E_CALL_CANCELLED)”.

To solve the problem, you need to modify the WMI client application to issue calls to IEnumWbemClassObject::Next to retrieve full result sets prior to the release of the IWbemContext object. Also ensure that the timeout value is set to greater than 0 (ITimeout).

Best solution:

• https://support.microsoft.com/de-de/help/3124914/wmi-activity-event-5858-logged-frequently-with-resultcode-0x80041032

Quick fix

Are you facing error code 0x80041002 (WBEM_E_NOT_FOUND) when you try to open a WMI namespace on a Windows computer? Then you are dealing with a corrupted WMI repository. If the WMI repository is corrupted, it fails to handle an item deletion operation correctly, resulting in the described error message when you try to open a namespace.

Error 0x80041002 can be eliminated with the following troubleshoot solutions:

1. Apply the supported hotfix provided by Microsoft. After applying the hotfix, restart the computer. The problem should now be solved.
2. Another option is a workaround solution. Disable the Resultant Set of Policy (RSoP) logging policy. This should easily help you get rid of the WMI error message

Best solution:

• https://support.microsoft.com/en-us/help/2465990/0x80041002-wbem-e-not-found-error-occurs-when-you-try-to-open-a-wmi-na

Quick fix

The WMI error codes 0x80041003 and 0x80070005 with the description “Access denied” indicate a permission problem.

If you come across the 80041003 error, it is most definitely because you do not have the necessary permissions to perform the operation you are trying to perform in WMI. To solve the issue, first check if you have the necessary permissions. If you do, you can solve the problem by changing the WMI.bat file to rebuild the WMI values. Copy the following code and save it as WMI.bat, then run as administrator to update the settings.

@echo on

cd /d c:\temp 
if not exist %windir%\system32\wbem goto TryInstall 
cd /d %windir%\system32\wbem 
net stop winmgmt 
winmgmt /kill 
if exist Rep_bak rd Rep_bak /s /q 
rename Repository Rep_bak 
for %%i in (*.dll) do RegSvr32 -s %%i 
for %%i in (*.exe) do call :FixSrv %%i 
for %%i in (*.mof,*.mfl) do Mofcomp %%i 
net start winmgmt 
goto End 
  
:FixSrv 
if /I (%1) == (wbemcntl.exe) goto SkipSrv 
if /I (%1) == (wbemtest.exe) goto SkipSrv 
if /I (%1) == (mofcomp.exe) goto SkipSrv 
%1 /Regserver 
:SkipSrv 
goto End 
:TryInstall 
if not exist wmicore.exe goto End 
wmicore /s 
net start winmgmt 
:End

The error 80070005 means than the local Windows system is not able to verify the credentials of the target computer. To get rid of the error, check the access rights and make sure that the user account is part of the administrator group.

Best solution: 

• https://windowsforum.com/threads/bsod-microsoft-windows-wmi-0x80041003.46244/

Quick fix

Does your WMI connection time out while running the Windows Management Instrumentation? A timeout error is a common problem faced by WMI users and admins. The timeout is caused by network lag issues, resulting in the computer being unable to respond in time.

To get rid of the timeout error, try the following steps: When connecting to WMI, set the wbemConnectFlagUseMaxWait flag (scripting) or the WBEM_FLAG_CONNECT_USE_MAX_WAIT in C++ value to 128 (0x80) to change the timeout on the call to two minutes. The new settings can help you solve the issue. You should also check your network to find the cause of the lag issues.

However, there are other possible causes for a timeout error that may require further troubleshooting.

Best solution:

• https://docs.microsoft.com/en-us/windows/win32/wmisdk/troubleshooting-a-remote-wmi-connection#wmi-connection-timed-out