Fix Software Center returned error code 0x80080005

A customer recently reported an issue where the Software Center failed to load, displaying error code 0x80080005. After thoroughly analyzing the SCCM client logs, I was able to identify the problem and resolve it. I recreated this issue in my lab, and I hope the troubleshooting process and the solution proves helpful if you encounter a similar issue.

Previously, I addressed various issues with the software center on my blog, such as error code 0x80041001, app downloads stuck at 0%, and insufficient permission for software installations. However, error 0x80080005 stands out because it completely prevents the software center from loading.

Note: The error code 0x80080005 is also encountered during Configuration Manager client installation; however, when it appears for software center loading issues, the solution is different.

Symptoms

The client computer on which the software center failed was located in a different region, so I initiated an RDP session to investigate the issue. Upon logging into the PC, I observed that the software center remained stuck on the loading screen for several minutes after being launched. The below screenshot demonstrates this issue.

After a few minutes, the software center reported a loading issue with the error code 0x80080005. The following message was displayed: “There is a problem showing the current status. Software Center cannot get the current status for some of the software. The Software Center will list any items with available status. You can press F5 to refresh the view. If the problem persists, contact your help desk.”

More information: Loading Software Center returned error code 0x80080005 (-2146959355)

Troubleshooting Error 0x80080005 with Logs

I decided to review some logs on the client computer to check the issue. Reviewing the ClientIDManagerStartup.log showed the error “[RegTask] – Server rejected registration request: 3“. It appears that client registration is failing due to the SCCM server rejecting the process. The log file indicates multiple attempts to complete the registration.

Next, I reviewed the ccmmessaging.log and noticed the error “Failed to open to WMI namespace 80041003“.

Access check failed against user 'CORPW1$'
Failed to open to WMI namespace '\\.\root\ccm' (80041003)
Status Agent hasn't been initialized yet. Attempting to create pending event.

Access check failed against user 'CORPW1$'
Failed to open to WMI namespace '\\.\root\ccm' (80041003)
Status Agent hasn't been initialized yet. Attempting to create pending event.

Lastly, I reviewed the SCClient.log on the client computer and noticed that it failed to retrieve the UI settings data from WMI. This might explain why the Software Center remained stuck on the loading screen for an extended period.

Fix Software Center returned error code 0x80080005

The Software Center displays error code 0x80080005 when the client is blocked in the SCCM console. You can resolve this issue by manually unblocking the client from the console.

When you block a client, it cannot communicate with site systems to download policy, upload inventory data, or send state or status messages. When the software center is launched in such situations, it displays a white loading screen for a few minutes. If it fails to retrieve the latest policy from the management point, it generates error 0x80080005.

To unblock the client, open the Configuration Manager and go to Assets and Compliance > Devices. Type the computer’s name in the search box to find it. Right-click the client and select Unblock.

In the confirmation box, select OK. Performing this action prompts the client to retrieve the latest policy from the management point server, ensuring the Software Center loads properly.

Note: Repairing the client agent might not fully resolve the Software Center error 0x80080005. While the repair process could work temporarily, the issue with the Software Center may reoccur.

That’s how I resolved the error code 0x80080005 for Software Center. If you encountered the same issue at your work and something else worked, do let me know in the comments section. Until then, bookmark this site for more such troubleshooting guides on SCCM.