Error Code 0x80041010: How to Quickly Fix It

SCCM may fail at deployment due to network security settings

Windows 11 » Repair

4 min. read

Updated on October 4, 2023

by Claire Moraa

updated on October 4, 2023

Readers help support Windows Report. We may get a commission if you buy through our links.

Key notes

SCCM manages devices using a database of information and allows an organization to deploy software, policies, and configurations across users and devices.
To do this, it needs to communicate with WMI, which is responsible for backups and restorations. If it fails or gets corrupted somehow, SCCM may fail at deployment.
A quick fix is to repair the WMI before proceeding with SCCM deployments.

0x80041010 is the error code that the SCCM client may return when it fails to connect to the management point. The most common reason for this error is that the client could not obtain a site code from Active Directory.

In order to resolve this issue, you can try restarting the SCCM client service and/or rebooting the server. While this error doesn’t occur on most PCs, we were able to gather information on how to assist users who face the same issue.

What is WMI error code 80041010?

The error code 80041010 is an internal error that indicates that the Windows Management Instrumentation (WMI) subsystem is not working properly.

SCCM is Microsoft’s tool for managing Windows computers, it uses WMI as one of its mechanisms for management. SCCM primarily uses WMI to install applications on target computers but also uses other methods, such as Group Policy Objects (GPOs).

The main goal of SCCM is to be able to manage clients remotely across a network. It allows administrators to remotely install applications and updates on client machines without having physical access to those computers.

When you spot the error 0x80041010, it indicates that the Configuration Manager failed to install. It could be because the OS is not supported and, therefore, incompatible with the client machine.

What causes this problem?

This error can occur due to many different reasons, but generally, it’s caused by one of two things:

Damaged WMI database – If the WMI database becomes corrupt or damaged, then the SCCM agent will fail to install it on a computer. This is often caused by third-party applications that have modified the WMI database directly rather than using the SCCM client installer setup.
Corrupted registry settings – Editing the Registry is catastrophic, especially if you don’t know what you are doing. If you have third-party applications that have modified your registry settings incorrectly, they may have caused this problem.

When WMI is not working, SCCM cannot communicate with the client. This will result in a number of issues, including:

Inventory not being collected from clients
The client not being able to communicate with the server
Software not being deployed correctly

Other reasons include network security policies blocking the installation of a client agent. To get your SCCM back up and running, you will need to resolve these issues.

How do I fix error 0x80041010?

1. Repair WMI

Hit the Windows key, type cmd in the search bar, and click Run as administrator.
Type the following command to switch folders where the WMI repository is located: c:\windows\system32\wbem
Next, type and Enter the following command: dir /b *.mof *.mfl | findstr /v /i uninstall > moflist.txt & for /F %s in (moflist.txt) do mofcomp %s
If you’re still experiencing the error, proceed to run the following commands: Net Stop winmgmt C: CD %SystemRoot%\System32\wbem RD /S /Q repository regsvr32 /s %SystemRoot%\system32\scecli.dll regsvr32 /s %SystemRoot%\system32\userenv.dll for /f %%s in (‘dir /b /s *.dll’) do regsvr32 /s %%s scrcons.exe /regserver unsecapp.exe /regserver winmgmt.exe /regserver wmiadap.exe /regserver wmiapsrv.exe /regserver wmiprvse.exe /regserver mofcomp cimwin32.mof mofcomp cimwin32.mfl mofcomp rsop.mof mofcomp rsop.mfl for /f %%s in (‘dir /b *.mof’) do mofcomp %%s for /f %%s in (‘dir /b *.mfl’) do mofcomp %%s

2. Reset WMI

Hit the Windows key, type cmd in the search bar, and click Run as administrator.
Type in the following commands and press Enter after each one: winmgmt /salvagerepository winmgmt /verifyrepository winmgmt /resetrepository

These commands will check for any inconsistencies and rebuild if necessary.

Elsewhere, you may also come across the SCCM task sequence error, so check out our recommended fixes for the same. The SCNotification may also fail at times, but we have answers on how to get it back up.

That’s it from us, but share any additional thoughts in the comment section below.