How To the Fix Error 14098: The Component Store Has Been Corrupted?

The component store has been corrupted error is also known as DISM error 14098. DISM allows users to update and alter different features and drivers of Windows and it can occur while servicing Windows’ images due to which the image can become corrupted. Several features of Windows can stop working due to this error. The occurrence of this error displays the following message:
Error: 14098, The component store has been corrupted

What Causes “Component Store Has Been Corrupted” Error?

The main reasons for the component store has been corrupted error can be one of the following listed below.

1.  Corruption of Windows Update Components.
2. Presence of confliction between files.

Pre Tips:

If you are a victim of this error before doing anything else. Follow the steps mentioned below.

1. Go to the taskbar and in search bar type command prompt.
2. Right-click on command prompt and select run as administrator.

   

3. Type the following command in cmd and press enter

Dism.exe /online /Cleanup-Image /StartComponentCleanup

What to do if you get the Component Store Has Been Corrupted Error on Windows?

Solution 1: Reboot Your Windows Update Components.

Resetting your windows update components can be beneficial in eliminating the error. Follow the given steps to do that.

1. Go to the taskbar and in search bar type command prompt.
2. Right-click on command prompt and select run as administrator.

   

3. Type the following commands in cmd one by one and press enter after every command.

   net stop bits
   net stop wuauserv
   net stop appidsvc
   net stop cryptsvc

   

4. Now delete the qmgr*.dat files .Type the following command to do so

   Del “%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat”

5. After the above steps type the following command

   cd /d %windir%\system32

   

6. In order to reregister the BITS files and the Windows Update files you need to type following commands and press enter after each command

   regsvr32.exe atl.dll
   regsvr32.exe urlmon.dll
   regsvr32.exe mshtml.dll
   regsvr32.exe shdocvw.dll
   regsvr32.exe browseui.dll
   regsvr32.exe jscript.dll
   regsvr32.exe vbscript.dll
   regsvr32.exe scrrun.dll
   regsvr32.exe msxml.dll
   regsvr32.exe msxml3.dll
   regsvr32.exe msxml6.dll
   regsvr32.exe actxprxy.dll
   regsvr32.exe softpub.dll
   regsvr32.exe wintrust.dll
   regsvr32.exe dssenh.dll
   regsvr32.exe rsaenh.dll 
   regsvr32.exe gpkcsp.dll
   regsvr32.exe sccbase.dll
   regsvr32.exe slbcsp.dll
   regsvr32.exe cryptdlg.dll
   regsvr32.exe oleaut32.dll
   regsvr32.exe ole32.dll
   regsvr32.exe shell32.dll 
   regsvr32.exe initpki.dll
   regsvr32.exe wuapi.dll
   regsvr32.exe wuaueng.dll
   regsvr32.exe wuaueng1.dll
   regsvr32.exe wucltui.dll
   regsvr32.exe wups.dll
   regsvr32.exe wups2.dll
   regsvr32.exe wuweb.dll
   regsvr32.exe qmgr.dll
   regsvr32.exe qmgrprxy.dll
   regsvr32.exe wucltux.dll
   regscr32.exe muweb.dll
   regsvr32.exe wuwebv.dll

7. To reset Winsock.Type following command

   netsh winsock reset

   

8. Now it is time to reset BITS service and the Windows Update service to the default. To do so type the following code.

   sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
   sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

9. Now type the following code to start window update service.
   

   net start bits
   net start wuauserv
   net start appidsvc
   net start cryptsvc

   

10. Restart your system.

Solution 2:Delete The Recent Updates.

Recent updates can be the reason for error 14098 on your computer. So you can eradicate the component store corruption by deleting them. This can be done by following these steps.

1. Go to the taskbar and type settings in the search bar.
2. Select updates and security.

   

3. Select windows update.
4. Select  View update history and then click on the Uninstall Updates option.

   

5. Select the recently installed updates.
6. Right-click on it and select uninstall.

   

Solution 3: Permit “dism.exe” in your system’s antivirus

Sometimes your antivirus program can cause the Error: 14098 due to the blockage of dism.exe. In order to allow dism.exe through the antivirus:

1. Go to the taskbar and type virus and threat protection in the search bar.

   

2. Select Virus and threat protection settings.

   

3. Find the Exclusions in the current window and click on the Add or remove exclusions option.

   

4. Left-click on the + button and add the desired exclusion and then select the item from the menu.

   

5. Select the WinSxS folder: C:\Windows\WinSxS by navigating the path.
6. Select yes to proceed.

Solution 4: Scan Your System by using ASR.

If you have already performed all the above solutions and the component store corruption still exists try doing a full system scan using ASR.

1. Reboot your system
2. BIOS screen will appear. Continue pressing f8 until advance options show up.
3. Select Safe Mode with Networking.

   

4. When Safe Mode with Networking is loaded. Press Windows key +R to open the Run prompt.
5. After following all the steps Windows Run Box will appear.
6. Type the URL address and click ok.
7. It will start downloading the program When it is done open launcher to install the program.
8.  Run ASR to perform a full system scan.
9. Click the Fix, Clean & Optimize Now option.

   

Solution 5: Repair using Microsoft System Readiness Tool

If you still can’t get rid of store corruption, try to use a repairing tool to resolve this issue. Follow the steps to carry his task out:

1. Download the Microsoft System Readiness Tool from your favorite browser.
2. Click the downloaded executable file and follow the onscreen instructions to install the tool on your PC.

   

3. After the installation is done, click close.
4. This tool will help you to repair the broken parts of the registry. Now reinstall the update you were trying to install previously and see if the issue is resolved.

If you need further assistance. Contact here