Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x80070032 - The process cannot access the file because it is being used by another process. | ConfigMgr client log (CMTrace.log) | -> Indicates a file access conflict. |
| Affected OS build | Windows 11 23H2 | System Information tool or $OSBuild variable | -> Confirmed via System Info. |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WMI | Registry Editor (Regedit.exe) | -> Contains WMI configuration settings. |
| Relevant service/endpoint URL | DCOM (Dynamic Configuration Management) | Microsoft Learn documentation on DCOM | -> Required for WMI communication. |
| Log line signature | [ConfigMgr Client] Error: Failed to access WMI namespace due to access denied. | CMTrace.log | -> Indicates WMI access issues. |
Log Files to Check
C:\Windows\CCM\Logs\CMTrace.logC:\Windows\System32\Wbem\Logs\WmiApRpl.log
What This Error Actually Means
The error code
0x80070032 translates to the Windows system error message "The process cannot access the file because it is being used by another process." This error is raised by the Windows Management Instrumentation (WMI) subsystem or the Distributed Component Object Model (DCOM) during a Configuration Manager client push installation attempt. Specifically, it indicates that the ConfigMgr client installer cannot access a required WMI namespace or DCOM endpoint due to a file lock, access denial, or network policy conflict. The error is often misattributed to file locks, but in the context of ConfigMgr client push, it is typically caused by Windows Firewall blocking DCOM traffic or a corrupted WMI repository. The error is logged in
C:\Windows\CCM\Logs\CMTrace.log with the signature
[ConfigMgr Client] Error: Failed to access WMI namespace due to access denied, confirming the root component as WMI/DCOM.
Affected Versions and Scope
This error is most commonly observed on **Windows 11 23H2** (OS build 22621.x or newer), particularly in environments where Windows Firewall is configured with strict outbound rules or where WMI repository corruption has occurred. The issue is not exclusive to 23H2 but is amplified by changes in how Windows 11 handles DCOM and WMI security contexts compared to earlier OS versions like Windows 10 21H2. Environments using **Microsoft Endpoint Manager (MEM) with Intune co-management** or standalone ConfigMgr deployments are both susceptible. The error does not occur in unmanaged Windows 11 devices or in scenarios where client push is replaced by user-driven installation (e.g., via SCCM client UI). It is also less common in Azure AD-joined devices unless hybrid Azure AD join is enforced with on-premises group policy conflicts.
Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are located in
C:\Windows\CCM\Logs\CMTrace.log and
C:\Windows\System32\Wbem\Logs\WmiApRpl.log. In
CMTrace.log, search for the exact line:
[ConfigMgr Client] Error: Failed to access WMI namespace due to access denied. In
WmiApRpl.log, look for entries with
ERROR severity and keywords like
WBEM_E_ACCESS_DENIED or
WBEM_E_FAILED.
Event Viewer provides additional context:
- **Event ID 10** in the **System** log under
Microsoft-Windows-WMI-Activity/Operational with source
WMI and description "WMI operation failed with error code 0x80070032".
- **Event ID 10016** in the **Application** log under
Microsoft-Windows-DCOM/Operational with source
DCOM and details about failed DCOM activation attempts.
Root Causes
1. Windows Firewall Blocking DCOM Traffic
This is the most common cause. The ConfigMgr client push relies on DCOM over RPC, which requires specific Windows Firewall rules (e.g.,
DCOM-In and
WMI-RPC-In). If these rules are disabled or overridden by custom policies, the installer cannot establish a connection. To differentiate, check the firewall status using
Get-NetFirewallRule -Name "WMI-RPC-In" and verify if the rule is enabled.
2. WMI Repository Corruption
A corrupted WMI repository prevents the installer from querying or modifying WMI namespaces. This can be diagnosed by running
Get-WmiObject -Namespace root\ccm -Class SMS_Client, which will fail with error
0x80070032. Use
winmgmt /verifyrepository to confirm corruption.
3. WMI Namespace Permissions
Incorrect permissions on the
root\ccm namespace can trigger this error. Check permissions via
WBEMTest by connecting to the namespace and selecting **Security**. Ensure the SYSTEM account has full control.
Fix Procedure
- Enable Required Firewall Rules:
Set-NetFirewallRule -Name "WMI-RPC-In" -Enabled True
Set-NetFirewallRule -Name "DCOM-In" -Enabled True
Warning: Disabling firewall rules globally can expose devices to network-based attacks. Apply changes via Group Policy or Intune to target only affected devices.
- Rebuild WMI Repository:
- Stop the WMI service:
Stop-Service -Name winmgmt
- Delete the repository:
Remove-Item -Path "C:\Windows\System32\wbem\Repository" -Recurse -Force
- Restart the WMI service:
Start-Service -Name winmgmt
- Repair WMI Namespace Permissions:
Get-WmiObject -Namespace root\ccm -Class SMS_Client | Set-WmiInstance -Arguments @{__PERMISSIONS__ = "A:OICI;$(SYSTEM):(ID)F;;;SY"} -EnableAllPrivileges
- Intune Policy Fix:
Navigate to **Intune admin center > Devices > Windows > Windows device features > Device restrictions**, and create a policy with OMA-URI
./Device/Vendor/MSFT/Policy/Config/WindowsFirewall/DomainProfile/AllowInboundRules set to True.
Error Code Variants
| Error Code | Description | Differentiator |
0x80070032 | File access denied due to lock or policy | Occurs during WMI/DCOM access; linked to firewall or repository issues |
0x80070005 | Access denied (permissions) | Logged when WMI namespace permissions are explicitly denied to SYSTEM |
0x8004100E | WMI namespace not found | Indicates missing root\ccm namespace, not a file lock |
Verification
After applying fixes, verify success by:
- Checking
CMTrace.log for the line
[ConfigMgr Client] Successfully installed client.
- Running
Get-WmiObject -Namespace root\ccm -Class SMS_Client without errors.
- Confirming in the ConfigMgr console under **Monitoring > Client Status** that the device shows "Client is working properly".
Prevention
To prevent recurrence:
- Deploy a Group Policy Object (GPO) or Intune policy to enforce
WMI-RPC-In and
DCOM-In firewall rules.
- Schedule a monthly task to validate WMI health using
winmgmt /verifyrepository and rebuild if necessary.
- Use
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to proactively monitor for WMI/DCOM errors in managed devices.
Tip: Use logman start CCMTrace -p Microsoft-Windows-ConfigMgrClient -ets to capture real-time traces during client push attempts, bypassing the need to manually parse large log files.