Back to Windows Vista and Server editions, a potential fix for repairing the corruption on a system that we casually use is the CheckSUR. CheckSUR is commonly defined under System Update and Readiness Tool (KB947821). In Windows 8 and Windows Server 2012, the tool is renamed to Inbox Corruption Repair still the functionality remains same.
If you’re are not getting what I’m talking of, let me demonstrate you. Suppose, a package on your system becomes corrupted. In general cases, Windows Updates provides the patches to repair the package. All this is done silently and the end user didn’t even notice it. However, if we want to fix the corrupted package on the basis of our own knowledge, then we need to use the Deployment Imaging and Servicing Management (DISM) tool instead via Windows Powershell or Command Prompt.
Using DISM, you can easily recover an unserviceable Windows Image. Add to these, DISM is powerful way to meet out the issues not solved by System File Checker (commonly used as SFC /SCANNOW command). In this article, I’ll show you how to do Inbox Corruption Repair using DISM, so without wasting anymore time, lets go…
FIX : Repair Your Windows 8 Using DISM Commands
1. Press + Q, type powershell, from results pick Windows PowerShell and right click over this result entry and select Run as administrator. In other words, you have to run Windows PowerShell as administrator, not as a user.
2. You can use following switches depending upon the requirements:
Command 1 :
Repair-WindowsImage -Online -CheckHealth : This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.
Running Dism /Online /Cleanup-Image /CheckHealth in Command Prompt will also do the same job.
Command 2 :
Repair-WindowsImage -Online -ScanHealth : This checks to see if a component corruption marker is already present in the registry. This is merely a way to see if corruption currently exists. This is could take almost 5 minutes to finish.
This operation can be executed using Dism /Online /Cleanup-Image /ScanHealth command in Command Prompt.
Command 3 :
Repair-WindowsImage -Online -RestoreHealth : This switch option checks for component store corruption, records the corruption to E:\WindowsLogs\CBS\CBS.log, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes or more to finish depending on the level of corruption.
Executing command Dism /Online /Cleanup-Image /RestoreHealth will do the same job as above.
To repair an online image using some of your own sources instead of Windows Update, type:
Dism /Online /Cleanup-Image /RestoreHealth /Source:c:testmountwindows /LimitAccess
If you do not specify a /Source for the repair files, the default location for Features on Demand is used. If you specify more than one /Source, the files are copied from the first location where they are found and the rest of the locations are ignored. You can use /LimitAccess to prevent the DISM tool from using Windows Update as a repair source or as a backup repair source for online images.