🇬🇧 | 🇩🇪 | 🇫🇷 | 🇪🇸 | 🇨🇳 | 🇸🇦
We don't have DLL but we have:
Windows File Analyzer & Online Fast Antivirus

A minimalist interface featuring quick search, convenient uploading, and a clean section structure.

🛡️🔍 Fast verify your file, just drop on this page.
Virus check, hashes, sign verify, architecture, AI info.

How to fix "The WS-Management service cannot process the request. The WMI provider returned an 'access denied' error."

Error Description

This error occurs when the Windows Remote Management (WinRM) / WS-Management service attempts to interact with the Windows Management Instrumentation (WMI) repository but lacks the necessary administrative permissions to access the requested namespace. This typically happens because the user account executing the command—or the WinRM service account itself—has not been granted explicit remote or local launch/activation permissions within the WMI security settings, or because the User Account Control (UAC) filtering is blocking the administrative token over a remote connection.

Step-by-Step Fixes

Method 1: Grant WMI Namespace Security Permissions

  1. Press the Windows Key + R on your keyboard to open the Run dialog box.
  2. Type wmimgmt.msc and press Enter to open the WMI Control console.
  3. In the left pane, right-click on WMI Control (Local) and select Properties.
  4. Navigate to the Security tab in the properties window.
  5. Expand the root folder tree, locate the specific namespace causing the issue (usually Root\CIMV2), select it, and click the Security button at the bottom right.
  6. Look for your user account or group (e.g., Administrators or Remote Management Users). If it is not listed, click Add, type the object name, and click OK.
  7. Select the user or group, and in the "Permissions" section below, check the Allow boxes for:
    • Execute Methods
    • Enable Account
    • Remote Enable
  8. Click the Advanced button to open Advanced Security Settings.
  9. Select the user account you just modified and click Edit.
  10. Ensure the Applies to dropdown menu is set to This namespace and subnamespaces.
  11. Click OK, then click Apply, and close all WMI properties windows.

Method 2: Configure DCOM Launch and Activation Permissions

  1. Press the Windows Key + R to open the Run dialog box.
  2. Type dcomcnfg and press Enter to open Component Services.
  3. In the left console tree, expand Component Services, expand Computers, and right-click on My Computer, then select Properties.
  4. Navigate to the COM Security tab.
  5. Under the Launch and Activation Permissions section, click the Edit Limits... button.
  6. In the security settings window, select Administrators or the specific user group you are using.
  7. Ensure that the Allow checkbox is selected for the following permissions:
    • Local Launch
    • Remote Launch
    • Local Activation
    • Remote Activation
  8. Click OK to save the changes.
  9. Under the Access Permissions section on the same tab, click Edit Limits....
  10. Ensure that Local Access and Remote Access are allowed for your administrative user or group.
  11. Click OK, then click Apply, and close the Component Services utility.

Method 3: Disable Remote UAC Restrictions (LocalAccountTokenFilterPolicy)

If you are connecting remotely using a local administrator account instead of a domain administrator account, Windows UAC strips administrative privileges by default. You can disable this restriction via the registry.

  1. Press the Windows Key + R, type regedit, and press Enter to open the Registry Editor.
  2. Navigate to the following registry path using the left pane hierarchy: HKEY LOCAL MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. Right-click on an empty space in the right pane, hover over New, and select DWORD (32-bit) Value.
  4. Name the new value exactly as: LocalAccountTokenFilterPolicy
  5. Double-click the newly created LocalAccountTokenFilterPolicy entry to modify it.
  6. Change the value data from 0 to 1 and make sure the Base is set to Hexadecimal.
  7. Click OK to save and apply the registry configuration changes.
  8. Close the Registry Editor.

Method 4: Restart WinRM and WMI Services

After applying the configuration changes, you must restart the relevant system services for the permissions to take full effect.

  1. Press the Windows Key + R, type services.msc, and press Enter to open the Services management console.
  2. Scroll down the list to find the Windows Remote Management (WS-Management) service.
  3. Right-click on it and select Restart.
  4. Next, scroll to find the Windows Management Instrumentation service.
  5. Right-click on it and select Restart. Note that restarting this service may prompt you to restart other dependent services; click Yes to proceed.
  6. Close the Services window and restart your machine if necessary.
ERROR_WSMAN_WMI_INVALID_VALUE | ERROR_WSMAN_WMI_SVC_ACCESS_DENIED | ERROR_WSMAN_WMI_CANNOT_CONNECT_ACCESS_DENIED | ERROR_WSMAN_INVALID_FILTER_XML | ERROR_WSMAN_ENUMERATE_WMI_INVALID_KEY

There may be some errors. Learn Microsoft