How to Fix SCCM Client WMI issues like Access Denied

WMI is a must for SCCM client-server connection and for remote Windows PC management. SCCM uses the Win32_Service class for monitoring services. WMIC is a command line application that helps you manipulate your Windows system effectively. Now let's address every single one of the SCCM Client WMI issues faced by users in this article.

SCCM Client WMI issues

The problems that one faces related to the SCCM client WMI that this guide covers, are as follows.

WMI Class Not Valid

Problem with WMI Connection

Cannot Access

Let us dive into their details.

1] WMI Class Not Valid

The following error notice is experienced by many customers when using SSCM Client or any other application like Battle.Net, when checking through winmgmt.msc.

All required WMI classes could not be registered.

Class not registered in the WMI of Win32_Processor

WMI: Class not registered: Invalid class: Win32_WMISetting

Information about security- done

Class not present in Win32_OperatingSystem: WMI.

We'll create a script to restart all the involved services, because it is just a bug.

Just run Notepad and from there copy and paste the following lines of code and save the file with any name but give it an .cmd extension. As simple as that to achieve this.

stop "Background Intelligent Transfer Service" stop "COM+ Event System" stop "Microsoft Software Shadow Copy Provider" stop "Volume Shadow Copy" stop Managing the net stop To look for the specific files, go to the following directories: *.dll, dlllist.txt, *.mof, moflist.txt, *.mfl, and mfllist.txt. Then, for every file in dlllist.txt, do regsvr32 /s. For every file in moflist.txt, do mofcomp %s. Lastly, for each file in the mfllist.txt file run mofcomp %s. net start "Background Intelligent Transfer Service" (BITS) "COM+ Event System" (Events) "Microsoft Software Shadow Copy Provider" (SCP) "Volume Shadow Copy" (DCP) Windows Management Framework (WMF) boot I am looking for files dlllist.txt, moflist.txt, mfllist.txt, wmiprvse and regserver.

Find where the script has been saved; we placed it on the desktop so that later it would be easy to find; you can do the same. Right-click the script file and from the context menu select "Open as administrator." When UAC prompts you, click Yes.

Every time it asks you, press 'Y' until the Command Prompt screen shows up. Hopefully this should resolve the issue.

2. WMI Connection Problem

Configuring WMI or by using SCCM, you may have some WMI Connectivity issues. Some of the following errors listed below, but the solutions provided here would still apply if you have any other issues not listed.

Disconnected from

WMI could not be found

Disconnected from

"Win32: The system cannot find the path specified."

comes to mind.

Disconnected from

due to "WMI: Generic failure."

These are in fact bugs. A live or active WMI repository we need to make sure that it is consistent.

Just run this command and have this done.

running winmgmt /verifyrepository

Using the path option to the command/verifyrepository, you can verify any archived copy of the repository. In this case, the path argument should include the whole path of the copy saved to the repository. Note that the folder of the repository should be copied to the saved repository.

This can be resolved by restarting the WMI Service. To do this, follow these steps in elevated mode of the Command Prompt.

"sc config winmgmt start= disablednet stop" The following command can be run from within the following directory: %windir%system32wbemfor /f %s in do moflist.txt & for /f %s in moflist.txt do mofcomp %s

Hopefully, one of the above fixes your problem.

Related: How to Install SCCM Console on Windows 11

3.] Access Denied

But, on the other hand, the same error message, Access is denied, states that the user account does not have appropriate permissions.

To avoid this problem when trying to access a Namespace, ensure that the user's account has been added to the administrators group or to another Active Directory account that has the privileges to access. Having the wrong credentials also causes the same problem, so check that the correct one is in use.

In case WMI Control Properties are giving you the "Access is denied" problem, then you should check and configure access manually in WMImgmt. Here are steps that you will have to follow to do that.

First of all, press Win + R. Then type "WMImgmt.msc" and click the Ok button.

When WMImgmt has been opened, it will show the Console Root expanded. Here you need to locate the WMI Control (Local), right-click on it, and select Properties.

Under the Security tab, select Everyone to give root and CCM access to all by checking all the boxes under Allow.

Open Run again, and copy "dcomcnfg," then click on the Ok button.

Click on Computers > Component Services > My Computer.

Right-click on My Computer and select Properties.

To enable the distributed component functionality on this machine, open the Properties window and click the Default Properties tab. In here, the Default Authentication Level is to be set to Connect and the Default Impersonation Level is to be set to Identify.

Under COM Security tab, click Edit limits. If you haven't granted everyone with enough permissions, grant them all full permission.

You can restart the WMI Services by following the process outlined in the previous section above to bring your newest changes into effect.

We hope that this has helped in trying to resolve the issue at hand. Until the next time, good luck.