DISM - Fixing Component Store Corruption in Windows 8

How to Use DISM to Fix Component Store Corruption in Windows 8 and Windows Server 2012

One of the most used tools when fixing corruption for Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2 was the System Update and Readiness Tool (KB947821), commonly called CheckSUR. The CheckSUR tool was an excellent way for most people to see what corruption had happened on their store, and potentially fix that corruption if the tool contained the payload to do so.

In Windows 8/8.1 and Windows Server 2012, this has changed. It’s called Inbox Corruption Repair and it brings the functionality of CheckSUR into Windows rather than requiring a separate download to get the utility like you do now. This is exposed in two ways, the first is really unseen by the end user and happens when Windows detects a corrupted state when attempting to install fixes via Windows Update. When this happens, Windows fix the corruption silently and then re-install the prior packages. The manual way to use this tool is via DISM (Deployment Imaging and Servicing Management). The way this is exposed is via the DISM /Cleanup-Image functionality.

If a Windows image (Windows component store) becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.

For example:

  • To use to fix Windows component store corruption when a SFC /SCANNOW command is unable to repair corrupted system files because the store (source) is corrupted, then run the SFC command again.
  • To use to fix Windows component store corruption when the same Windows Updates continue to appear to be available to install even though they already show successfully installed in update history.

For more information, see:



This tutorial will show you how to do an Inbox Corruption Repair with the DISM /Cleanup-Image tool to fix component store corruption in Windows 8 and Windows Server 2012.

You must be signed in as an administrator to be able to do an Inbox Corruption Repair with the Deployment Imaging and Servicing Management (DISM) tool.

Note   Note
The DISM /Cleanup-Image tool saves it's log files in the file locations below. To be able to view these logs, you would need to copy them from the locations below to your desktop, then open them from your desktop.

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\DISM\dism.log


CBS.log.jpg

DISM.log.jpg

Tip   Tip
If you get an error like below when running a DISM command in an option below, then run the command below and try again afterwards.

Dism.exe /online /Cleanup-Image /StartComponentCleanup


Note   Note
Error: 0x80240021

Failure DISM. No operation was performed.



CONTENTS:

  • Option One: To Run "DISM /Cleanup-Image" tool in an Elevated Command Prompt
  • Option Two: To Run "DISM /Cleanup-Image" tool in an Elevated PowerShell






OPTION ONE

To Run "DISM /Cleanup-Image" tool in an Elevated Command Prompt



1. Open an elevated command prompt.

2. Do step3, step 4, step 5, or step 6 below for what DISM command you would like to use.


3. To Use DISM /CheckHealth Command
Note   Note
You would use /CheckHealth to only check whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired. This is just a quick way to see if corruption currently exists, and to inform you if there is corruption. This does not fix anything or create a log. This will finish running almost instantly.




A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:ar: Dism /Online /Cleanup-Image /CheckHealth

CMD_CheckHealth.jpg



4. To Use DISM /ScanHealth Command
Note   Note
You would use /ScanHealth to scan the image for component store corruption. This option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This can take around 5-10 minutes to finish. It will stay at 20% for a while before continuing.





A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:ar: Dism /Online /Cleanup-Image /ScanHealth

CMD_ScanHealth.jpg



5. To Use DISM /RestoreHealth Command
Note   Note
(recommended) You would use /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.





A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:ar: Dism /Online /Cleanup-Image /RestoreHealth

CMD_RestoreHealth.jpg



6. To Use DISM /RestoreHealth /Source:wim Command
Note   Note
You would use /Source with /RestoreHealth to specify the location of an install.wim file as the source of known good versions of files that can be used for the repair. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.

This can be useful if step 5 above was not able to repair the Windows image (component store).


The install.wim file will be in the Sources folder of a mounted Windows 8.1 ISO file.





A) In the elevated command prompt, type the command below you want to use, press Enter, and go to step 7 below. (see screenshot below)

:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1

OR

(To prevent DISM from using Windows Update for online images)
:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

For example:

:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

DISM_RestoreHealth_wim_sources.png



7. If you did step 5 or step 6 above, it is recommended to restart the computer to fully apply.






OPTION TWO

To Run "DISM /Cleanup-Image" tool in an Elevated PowerShell



1. Open an elevated PowerShell.

2. Do step3, step 4, step 5, or step 6 below for what DISM command you would like to use.


3. To Use DISM /CheckHealth Command
Note   Note
You would use /CheckHealth to only check whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired. This is just a quick way to see if corruption currently exists, and to inform you if there is corruption. This does not fix anything or create a log. This will finish running almost instantly.




A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:arrow: Repair-WindowsImage /Cleanup-Image /CheckHealth

PowerShell_CheckHealth.jpg



4. To Use DISM /ScanHealth Command
Note   Note
You would use /ScanHealth to scan the image for component store corruption. This option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This can take around 5-10 minutes to finish. It will stay at 20% for a while before continuing.




A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:arrow: Repair-WindowsImage /Cleanup-Image /ScanHealth

PowerShell_ScanHealth.jpg



5. To Use DISM /RestoreHealth Command
Note   Note
(recommended) You would use /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.





A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

:arrow: Repair-WindowsImage /Cleanup-Image /RestoreHealth

PowerShell_RestoreHealth.jpg



6. To Use DISM /RestoreHealth /Source:wim Command
Note   Note
You would use /Source with /RestoreHealth to specify the location of an install.wim file as the source of known good versions of files that can be used for the repair. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.

This can be useful if step 5 above was not able to repair the Windows image (component store).


The install.wim file will be in the Sources folder of a mounted Windows 8.1 ISO file.





A) In the elevated command prompt, type the command below you want to use, press Enter, and go to step 7 below. (see screenshot below)

:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1

OR

(To prevent DISM from using Windows Update for online images)
:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

For example:

:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

PowerShell_DISM_RestoreHealth_wim_sources.png



7. If you did step 5, step 6, or step 7 above, it is recommended to restart the computer to fully apply.





That's it,
Shawn


 

Attachments

  • Command_Prompt.png
    Command_Prompt.png
    3.4 KB · Views: 579
Last edited by a moderator:
Well, Dell at the link below only has Windows 7 drivers available for the Inspiron N5010. None of them are for a LSI controller.
Were you having any issues for why you ran a DISM command? If not, then I wouldn't worry about this. If so, then I would recommend to refresh Windows 8 instead to preserve most of your drivers to not have to worry about them.
 
Last edited:

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
whils running dism in power shell i m getting this:

PS C:\WINDOWS\system32> Repair-WindowsImage -Online -ScanHealth
Repair-WindowsImage : The name of an attribute in an identity is not within the legal range.
At line:1 char:1
+ Repair-WindowsImage -Online -ScanHealth
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: :)) [Repair-WindowsImage], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand

PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> Repair-WindowsImage -Online -RestoreHealth
Repair-WindowsImage : The name of an attribute in an identity is not within the legal range.
At line:1 char:1
+ Repair-WindowsImage -Online -RestoreHealth
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: :)) [Repair-WindowsImage], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand



the thing wich is worrying me is to loose my old programs and data

what do you suggest for avoiding reinstall and loose old programs for wich i don t have any backup?

thanks
 

My Computer

System One

  • OS
    WIN8
    Computer type
    Laptop
Were you having any issues other than dism not running though?
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Were you having any issues other than dism not running though?

i ve tried to repair win after having ram and hard disk issues.

got the hard disk regenerated but now i can t access to the network settings (see attached pic) so then i ve tried to repair win

and gone thru different process as dism and sfc scan and until now nothing is working

let me know if you have better idea
acces denied.jpg

thanks
 

My Computer

System One

  • OS
    WIN8
    Computer type
    Laptop
Yeah, I'd say it's time to refresh Windows 8 to see if that helps first. :(
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Normally, that would be fine. Since we do not know what's causing these issues, there's a chance that the cause may be transferred over as well to only have the same issue again when you restore it to the new installation.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Normally, that would be fine. Since we do not know what's causing these issues, there's a chance that the cause may be transferred over as well to only have the same issue again when you restore it to the new installation.

i ve got another ideas it s to make an easy transfer from another similar pc wich is healthy at this time or may be do the both

one easy transfer from the same pc s data and if things doesnt work well then easy transfer from the second one

maybe there is more chance with this?
 

My Computer

System One

  • OS
    WIN8
    Computer type
    Laptop
If you don't mind having that PC's settings, then it would be fine. I think you would be better off in the long run starting with a fresh start though.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Brink, I just want to thank you for posting this info - it worked great for me. SFC /scannow found corrupted files and after three runs, they were still there. But, then using DISM command, corrupted files disappeared. You do great work in here - I hope members appreciate it as much as I. Thanks again!
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    HP Pavillion p6230f
    CPU
    HP AMD Phenom II X4 810
    Motherboard
    FOXCONN ALOE
    Memory
    8 GBytes
    Graphics Card(s)
    ATI/AMD Radeon HD 42
    Sound Card
    ATI/AMD SB600 - High
    Monitor(s) Displays
    Dell SE198WFP
    Screen Resolution
    1440 x 900
    Hard Drives
    Seagate ST3750528AS
    Browser
    IE 11
    Antivirus
    Windows Defender
You're welcome John. I'm glad it was able to help. :)
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
DISM and SFC have become schizoid

I've been accustomed to regularly running both sfc and DISM on Win8, regardless of whether sfc finds corruption or not, the same as I did with Vista and Win7, but then with sfc and KB947821. The nice difference about Win8 is that even if sfc could not fix some of the corrupt files, DISM would always fix them, so that a successive sfc run would then find no corrupt files.
Although sfc usually tells me--"Windows Resource Protection did not find any integrity violations"--running DISM.exe immediately thereafter has started giving me this, using the Restorehealth switch:
"[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.
Error: 0x800f081f
DISM failed. No operation was performed.
For more information, review the log file.":cry:

That made me wonder, so I ran DISM.exe with the ScanHealth switch and got the message,
"[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully."

Before, with no corrupted files, it would at least give me the message that it had repaired the non-existent corrupt files, which I always found humorous: "The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully." :)

Since the version of DISM.exe is still the same--6.2.9200.16384--it doesn't seem reasonable that Microsoft might have merely updated the tool so that it won't run if sfc or its own Scanhealth have not found corruption, although that possibility did occur to me.

So the question is, what is going on? The component store can be repaired, so, according to DISM, the only explanation is that the repair source cannot be found. On the other hand, it's giving me conflicting information as to whether anything is really corrupt. Yes, it's the metadata, or, no it isn't.

I've found that particular error discussed in a number of forums, with no workable fix; usually, though, it's in relation to updates failing to install. In this case, updates install just fine. This is a new installation of an oem Windows, and I did have to install some updates manually in getting Windows current, which hasn't happened before with Win8. Checking out
dism.exe /online /cleanup-image /restore health failed - Microsoft Community, for instance, gives a couple of suggestions, one being to run the Windows troubleshooter on Windows Update, which does give a clue:

"The troubleshooter made some changes to your system. Try attempting the task you were trying to do before.
Problems found
Windows Update components must be repaired Fixed"
However, it does find issues "not present" as "Default Windows Update data locations have changed" and "Potential windows Update Database error detected None."
Unfortunately, whatever the troubleshooter thinks it "fixed" does not fix the problem.

Another suggestion in that particular Microsoft Answer, to create and run a particular batch file, does not solve the problem of the DISM error either.

The log gives this for sfc: "Error DISM DISM Package Manager: PID=8764 TID=5864 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)".
Also, no corruption, but metadata corruption (?!):
"2013-10-01 08:18:05, Info CSI 00000009 CSI Store 724735956064 (0x000000a8bda11460) initialized
2013-10-01 08:18:05, Info CSI 0000000a StoreCorruptionRepair transaction begun. WcpVersion: [l:74{37}]"6.2.9200.16683 (win8_gdr.130806-1503)".
2013-10-01 08:18:05, Info CSI 0000000b@2013/10/1:13:18:05.170 Starting corruption detection (InnerFlags=5)
2013-10-01 08:21:07, Info CSI 0000000c@2013/10/1:13:21:07.942 Corruption detection complete. numCorruptions = 0, Disp = 1.
2013-10-01 08:21:07, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2013-10-01 08:21:07, Info CBS Repr: CSI Store check completes
2013-10-01 08:21:07, Info CBS Exec:Only CSI metadata corruption found, Process CSI repair.
2013-10-01 08:21:07, Info CSI 0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
2013-10-01 08:21:07, Info CSI 0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x5f4
2013-10-01 08:21:07, Info CSI 0000000f@2013/10/1:13:21:07.943 Beginning NT transaction commit...
2013-10-01 08:21:07, Info CSI 00000010@2013/10/1:13:21:07.954 CSI perf trace:
CSIPERF:TXCOMMIT;13135
2013-10-01 08:21:07, Info CSI 00000011 StoreCorruptionRepair transaction completed.
2013-10-01 08:21:07, Info CBS Repr: Finished repairing CSI store."
Additionally, "Checking System Update Readiness.
Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 0
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True"

Running the restorehealth from powershell gives a modified version of the error:
PS C:\Windows\system32>
PS C:\Windows\system32> Repair-WindowsImage -Online -RestoreHealth
Repair-WindowsImage : The restore operation failed. Either the repair source was not found or the component store
cannot be repaired.
At line:1 char:1
+ Repair-WindowsImage -Online -RestoreHealth
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: ([Repair-WindowsImage], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand
 
Last edited:

My Computer

System One

  • OS
    Win8.1 Pro 64bit
    Computer type
    Laptop
    System Manufacturer/Model
    Asus G75V
    CPU
    i7 3630QM 2.4GHz
    Memory
    16GB
    Graphics Card(s)
    NVidia 670M
    Antivirus
    NIS/Malwarebytes/SuperAntiSpyware/Zemana Anti-Logger
Hello ParrotSlave, and welcome to Eight Forums.

Just to help clarify: SFC repairs system files by replacing any corrupted ones found with copies from the component store. DISM only repairs the component store, and not system files. This way if SFC cannot repair files due to a corrupted component store, DISM will hopefully fix the component store to then allow SFC to be able to repair the system files.

I'm afraid that I'm not familiar with that error either. Usually when DISM fails to repair the component store, it's time to reinstall Windows. :(
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
This is a fresh install

The problem is that this is a fresh reinstall. I just got the laptop back from Asus Wednesday, and have been reinstalling a myriad of programs, carefully, and making a ludicrous number of system images during the process. I have two omg images, and five Windows Image Backups at the moment, although Windows does not "see" all of its backups. (It used to only see the one in the folder named "WindowsImageBackup", so you could keep it from deleting old images merely by renaming the folders, but now it is seeing its images even if they have been renamed, or, at least, most of them.) I could save the current image one way or another and then restore the older images to see when the problem began. The hassle is, depending on how far back I have to go, in activating all the third-party programs, which I just got through doing. The software companies think that we're giving away their software on street corners when they get multiple re-activation requests, apparently.
I did copy the oem's install.wim file from the recovery partition (by using DiskImage to copy the partition, then mounting it and copying the file), which is different from the one that came with the laptop in November, and I also made my own install.wim on Saturday, and put it in a custom-refresh folder in the hope of being able to do a "refresh" to that image, but refresh does not work on this laptop via any method, the oem F9 or the advanced startup options or via any alternate boot mechanism. (Curiously, it will not boot from any Windows repair disks via WindowsImageBackup either.) It will "reset," though, since I tried that out just to see.
I'm sorely tempted to install Windows 7 and wait a year or so for Win8 to become more stable. It is fast, but it's worse than Vista (or WinMe) when it comes to causing all-nighters.

Is there a way to use DISM to find out if the component store in a mounted image is corrupt? What would the syntax be if, say, I had an image mounted as L:?
 

My Computer

System One

  • OS
    Win8.1 Pro 64bit
    Computer type
    Laptop
    System Manufacturer/Model
    Asus G75V
    CPU
    i7 3630QM 2.4GHz
    Memory
    16GB
    Graphics Card(s)
    NVidia 670M
    Antivirus
    NIS/Malwarebytes/SuperAntiSpyware/Zemana Anti-Logger
Not sure it's possible to check for a mounted image unless it was running in a virtual machine.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
I had the crazy idea that I should compare the WinSxS folders between this installation and one from about three weeks ago, when DISM was working perfectly, but before Asus restored the OS (with a different base image, though.) I was thinking that, maybe, there would just be a few differences, and I could take ownership of the folder and replace any files that were different with the ones from three weeks ago. So, for the heck of it, I mounted the three-week old image and copied the WinSxS folder out of it, and used FolderMatch to compare it with the OS's WinSxS folder. WinSxS comparison.PNG The file differences are astounding, and, unfortunately, it's not just one or two that are different. FolderMatch says that there are 12,684 identical folders, 2760 different folders, and 1010 orphan folders.

However, I can get a good component store from the install.wim file, which will open with 7-Zip, so I could copy the WinSxS folder from the install.wim of the oem image and see what differences there are, since that image is only two weeks old. The problem is that Windows Update would have changed some of the files, but I'd feel safe in replacing all those with the same dates. I'm tempted to replace the entire folder except keep the orphan files in the new folder. I've replaced a few individual files in the past, when SFC reported that it couldn't fix a particular component because of a problem with a store component. In this case, SFC doesn't "know" since the files it's looking at are, so far, not corrupt. It won't know until it has to replace a corrupt file and then discovers that the store's file is also corrupt.
 

My Computer

System One

  • OS
    Win8.1 Pro 64bit
    Computer type
    Laptop
    System Manufacturer/Model
    Asus G75V
    CPU
    i7 3630QM 2.4GHz
    Memory
    16GB
    Graphics Card(s)
    NVidia 670M
    Antivirus
    NIS/Malwarebytes/SuperAntiSpyware/Zemana Anti-Logger
Hi All,

I have typed in the /Scanhealth command and it has been running for a lot longer than the suggested 5 - 10 minutes.. been almost 30 min and its still going.

Is this [or any relation to] the Windows Module Installer Worker ???
 

My Computer

System One

  • OS
    Windows 8
    Computer type
    Laptop
    System Manufacturer/Model
    DELL Inspiron 17R - SE
    CPU
    i7-3630QM
    Motherboard
    DELL ?
    Memory
    8GB
    Graphics Card(s)
    nVidia GT650M
    Sound Card
    On-Board
    Screen Resolution
    1920 x 1080
    Hard Drives
    Samsung SSD 840
    Samsung 1TB 5400 RPM
    Keyboard
    DELL Backlit
    Internet Speed
    ADSL 2+ - 10MB
    Browser
    Firefox
    Antivirus
    WIndows Defender
Hello SoiCBoy,

If you still have hard drive activity from DISM working, then it would be best to wait a bit longer to see if it may finish.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Hey Brink

I waited for over 30min and off memory I think there was HDD activity.

As per my other post, does it have any relation to "Windows Module Installer Worker" as I noticed both were using about 17% of CPU.

Anyway, I figure it was either looping or stuck and just closed the command prompt and proceed to shutdown. Then a strange thing happened, I got the message "Preparing to configure windows, do not turn off your computer". This took about 40 min and it finally shutdown, but I now wonder why the hell it took so long to configure and what was it configuring. I know it was not any window updates as I have it set to let me choose when to DL and install them. I also checked when the last updates where installed and they were dated yesterday, so it's got me stumped as to what it was that took so long??

Any ideas as I have never experienced this on Windows 7 and to be honest, I kind of like Windows 8
 

My Computer

System One

  • OS
    Windows 8
    Computer type
    Laptop
    System Manufacturer/Model
    DELL Inspiron 17R - SE
    CPU
    i7-3630QM
    Motherboard
    DELL ?
    Memory
    8GB
    Graphics Card(s)
    nVidia GT650M
    Sound Card
    On-Board
    Screen Resolution
    1920 x 1080
    Hard Drives
    Samsung SSD 840
    Samsung 1TB 5400 RPM
    Keyboard
    DELL Backlit
    Internet Speed
    ADSL 2+ - 10MB
    Browser
    Firefox
    Antivirus
    WIndows Defender
It sounds like something may have interfered with DISM.

Yes, "Windows Module Installer Worker" is part of what DISM and Windows Update uses. The configuring you had seen may have been for DISM repairing the component store.

Is everything working properly now though?
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Back
Top