“CcmSetup failed with error code 0x80041010” in SCCM

The System Center Configuration Manager (SCCM), now known as Microsoft Endpoint Configuration Manager (MECM), is super important for keeping an eye on various devices in a workplace. But, like anything techy, it sometimes hits a bump, especially when trying to add its agent to some computers. A common hiccup you might run into is the “CcmSetup failed with error code 0x80041010.” This error can be a bit of a pain when setting up the ConfigMgr client on some PCs. We’re going to break down what this error means, why it happens, and how you can fix it.

Also see: Uninstall SCCM Client Manually in Windows 10/11 via CMD

Knowing the 0x80041010 error in SCCM

When SCCM throws the error code 0x80041010, it’s basically saying, “I don’t know what went wrong.” To get to the bottom of this mystery, IT folks usually check out the ccmsetup.log file on the affected computer. This log keeps track of what happened during the setup of the client agent.

Sometimes, the error comes with hints that it might be about Windows version issues, like saying “OS is not Win10RS3+” even on newer versions of Windows. There could also be mentions of problems connecting to a Fallback Status Point or policy namespaces.

The log can show other errors too, suggesting issues with Management Points (MPs) or client-side problems. But, not all computers will see this error, hinting it’s something specific to certain setups or configurations.

Tip: Running into errors with SCCM? Try using ConfigMgr’s error lookup tools to figure out what those codes mean.

How to fix the CcmSetup failed with error code 0x80041010 issue

1. WMI repairs

Windows Management Instrumentation, or WMI, is a key part of Windows that helps manage things in a network. If WMI has problems, it can mess up installing the Configuration Manager client agent.

Why WMI matters in SCCM

In SCCM, WMI is essential for a lot of tasks, like gathering system info or setting up client preferences. So, if WMI isn’t working right, you might run into the “CcmSetup failed with error code 0x80041010” error.

Steps to repair WMI

If WMI is the culprit, here’s how to fix it:

1. First, stop the WMI Service with Net Stop winmgmt.
2. Then, fix the WMI repository by deleting it with RD /S /Q repository in the wbem directory.
3. Next, make sure DLLs for WMI are okay by re-registering them. You’ll use commands like regsvr32 /s %SystemRoot%\system32\scecli.dll.
4. Also, fix MOF Files with the mofcomp command to make sure they’re right.
5. Don’t forget to start the WMI Service again with Net Start winmgmt.
6. Last, try installing the SCCM client again to see if the error goes away.

You can also use this script below. Just copy it into a text file, save it as a .bat file, and run it as admin.

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

After you run the script, reboot the computer before trying the SCCM client setup again.

Things to keep in mind

These steps usually fix WMI problems, but remember every computer is a bit different. Make sure you back up important stuff before messing with system parts, and maybe try these fixes on a few machines before rolling them out everywhere.

2. Addressing DNS Issues

DNS (Domain Name System) problems can also lead to the 0x80041010 error. If a computer can’t find the SCCM server because of DNS issues, the setup won’t work.

The importance of DNS in SCCM

SCCM needs DNS to talk to clients, distribution points, and other parts of the network. If DNS can’t match the SCCM server’s name with its IP address, things won’t run smoothly.

Common DNS symptoms in SCCM

You might notice DNS issues in SCCM if:

• The computer can’t find the SCCM server’s name.
• The ccmsetup.log shows problems finding the Management Point or source location.
• There are delays or failures in getting policies or deploying apps because DNS can’t find what it needs.

Steps to troubleshoot

1. Check if the computer can find the SCCM server’s name with nslookup.
2. Make sure the SCCM DNS records are correct and up to date.
3. Look over the network setup to make sure everything’s configured right.
4. Clear out any old or wrong DNS info with ipconfig /flushdns.
5. Update group policies with gpupdate /force to make sure the computer’s using the latest settings.

Related resource: DNS Servers to Unblock Websites and Possibly Everything

Things to consider

If you’re still stuck with DNS issues after trying these steps, you might need to dig deeper or get help from your network team. A smooth-running SCCM setup needs both the app and the network foundation to work right.

Quick recap

SCCM or MECM is a powerful tool, but sometimes it runs into problems. The error 0x80041010 might look scary, but with some step-by-step troubleshooting, you can usually get to the bottom of it. Each error is a chance to learn more about how the system works, so treat these moments as opportunities to grow your skills.