The component store has been corrupted, 0x80073712

When trying to install a role or feature (like Windows Security Updates or Server Backup feature) to the Windows Server, the feature installation fails and some users get to see a message saying The component store has been corrupted, error 0x80073712. Instead of the Add Roles and Features Wizard completing successfully, this message pops up! We will talk about solutions that may help you resolve this isue. The entire error message for this Windows Server wizard looks like this-

The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. The component store has been corrupted. Error: 0x80073712

The component store has been corrupted, 0x80073712

To fix The component store has been corrupted, error 0x80073712 on Windows Server, you can use the following solutions:

1. Run the DISM tool
2. Use the System File Checker tool
3. Add WinSxS folder to exclusion to Windows Security.

Let’s check these options.

1] Run the DISM tool

As the error itself indicates, there is a possibility that the Windows Component Store that stores the files for adding features or roles using Windows Server and other data is corrupted. Maybe that’s why you are getting this component store corrupted error 0x80073712. So, in such a case, you should run the DISM tool (Deployment Image Servicing and Management command-line tool) that can help you check as well as repair Windows Component Store.

For doing so, first, run Command Prompt as an administrator. After this, execute the command to check if Windows Component Store is corrupted. The command is:

Dism /Online /Cleanup-Image /CheckHealth

If it is not corrupted, it should show the message No component store corruption detected.

But, if Windows Component Store is corrupted, then run the following command to repair it:

Dism /Online /Cleanup-Image /RestoreHealth

It may take longer than expected time to complete the command and repair process. So, you should wait. Once the process is completed, install the role or service, or feature on Windows Server and see if this works.

The repair process should work and complete as expected, but it might also end up with Error 14098, Error 0x800f0906, or something else.

In that case, you need to run the DISM tool with a locally mounted Windows ISO image file to perform the repair process. For that, execute the command that includes the path of the ISO file and the install.wim file that is present in the Sources folder of the ISO file. The command would be:

DISM /Online /Cleanup-Image /RestoreHealth /Source:F:\Sources\install.wim:1

Replace F with the drive location where you have mounted the ISO. This should work and solve your issue.

You can also execute the above command with limited use (to skip checking Windows Server Update Services or Windows Update). Your command would be:

DISM /Online /Cleanup-Image /RestoreHealth /Source:F:\Sources\Install.wim:1 /LimitAccess

Related: Fix DISM Errors 87, 112, 50, 11, 1726, 3, 87, 1392, 1393, 1910, etc.

2] Use the System File Checker tool

You can also run the System File Checker tool and see if that works. It scans for protected system files and repairs or replaces the corrupt or damaged data with a cached copy. To run the System File Checker tool, first, open the elevated Command Prompt window and then execute the following command:

Sfc /scannow

Let the command complete and it should be able to repair all the corrupt files (if any). After this, you can try to perform the task you were doing on your Windows Server and it should be complete without interruption.

This post will help you if you see Windows Resource Protection could not perform the requested operation message.

3] Add WinSxS folder to exclusion to Windows Security

This option seems to work for one of the users having the same problem. It was the antivirus conflict with the WinSxS folder because of which this component store has been corrupted error 0x80073712 appears on Windows Server. So, you need to add an exclusion to Windows Security for the WinSxS folder and this may get rid of this problem.

In Windows Security, access the Exclusions section and click on the Add or remove exclusions option. After that, you can use the Add an exclusion button and then add the WinSxS folder (C:\Windows\WinSxS) to the exclusion list.

If you use some other security tool, then look for exclusions or whitelist or something similar option in your antivirus security settings and add the WinSxS folder there.

You may also need to put Dism.exe on the Exclusion list.

I hope this will help.

Also read: How to remove Roles and Features in Windows Server

How do I fix error code 0x80073712?

If you get error code 0x80073712 for Windows Update on your Windows 11/10 computer, then you can fix Windows Update error 0x80073712 using the DISM tool, Windows Update Troubleshooter, repairing hard drive errors, etc. On the other hand, if you get a 0x80073712 error for Windows Server, then the solutions covered in this post might be useful. Check them out.

How do I repair Windows components?

If you see Windows Update components must be repaired error while troubleshooting Windows Update, then you can use the following solutions to fix this issue:

1. Reset the Windows Update component to default
2. Repair corrupt Windows Update files
3. Use Windows Update Troubleshooter.

Read next: How to use Windows Server Migration Tool.