Share via

DISM reports "corruption was repaired", but corruption/repairs not listed in DISM.log file.

Anonymous
2022-03-23T13:10:56+00:00

I have Windows 8.1 x64.

Microsoft Windows [Version 6.3.9600]

From an elevated command prompt I ran

sfc /scannow

which found no problems.

"Windows Resource Protection did not find any integrity violations."

I then ran

Dism /Online /Cleanup-image /RestoreHealth

This seemed to find problems: 

Deployment Image Servicing and Management tool 

Version: 6.3.9600.19408 

Image Version: 6.3.9600.19397 

[==========================100.0%==========================] 

The restore operation completed successfully. The component store corruption was repaired. 

The operation completed successfully.

I then ran it again

Dism /Online /Cleanup-image /RestoreHealth

And to my surprise it seemed to report finding problems again:

Deployment Image Servicing and Management tool 

Version: 6.3.9600.19408 

Image Version: 6.3.9600.19397 

[==========================100.0%==========================] 

The restore operation completed successfully. The component store corruption was repaired. 

The operation completed successfully.

At this point I checked the log file at "C:\Windows\Logs\DISM\dism.log", but there's nothing obvious there indicating a problem that was identified or repaired. 

2022-03-23 21:24:40, Info                  DISM   DISM Package Manager: PID=8424 TID=12344 

=================================

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

Total Operation Time: 2054 seconds.

 - CDISMPackageManager::Internal_Finalize

So did the commandline output not really mean that errors were found/repaired? Or are the errors recorded somewhere else in the DISM.log file (or another file)?? Or are some errors found/repaired by DISM simply not logged???

There seems to be a dearth of information online about interpreting/analysing the DISM.log file.

—DIV

P.S. Subsequently I saw some advice to re-run sfc /scannow if DISM finds & repairs any problems:

"After the component store has been repaired, you can run the system file checker tool (sfc /scannow). It is likely that it will be able to restore the damaged or missing system files (Windows Resource Protection found corrupt files and successfully repaired them)."

So I ran sfc /scannow again, but it still reported

"Windows Resource Protection did not find any integrity violations."

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-03-24T03:22:53+00:00

    Note   Note If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

    If not, then run the Dism /Online /Cleanup-Image /RestoreHealthcommand to repair any component store corruption, restart the PC afterwards, and try the sfc /scannow command again.

    https://www.eightforums.com/threads/sfc-scannow-command-run-in-windows-8.3047/

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-04-16T13:56:16+00:00

    Thanks, Bill.

    In the meanwhile I was in communication with a member of Microsoft's Premier Support team about a different matter, but I took the opportunity to briefly ask about the point you raised. (No offence, but it's always interesting to hear advice direct from MS.)

    She advised that she thought it was 'probably' correct that there's no benefit in running DISM unless SFC reports problems, but that to confirm it a series of tests would be needed.... On the other hand, she advised that there's no harm running DISM anyway. (Aside from the fact that it takes some time to run.)

    —DIV

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-03-24T00:22:55+00:00

    Hello, Bill.

    Yours is the first suggestion I've seen to only run DISM if SFC identifies a problem. I thought they checked different aspects of Windows, and likewise targeted their repairs differently.

    Are you able to please provide any reputable documentation which supports the basic idea that the user should only run DISM if SFC identifies a problem (i.e. don't run DISM unless SFC identifies a problem)?

    —DIV

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-03-23T13:53:53+00:00

    I don't even know why you ran DISM, as SFC told you everything was fine.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-03-23T13:36:17+00:00

    OK, I have to admit that I thought the statement about the DISM log location:

    "You can find the DISM log of scanning and repair of the system files here: C:\Windows\Logs\CBS.log."

    was a misprint. But I guess it wasn't!

    Having a look at that file, I find the following. I'm not totally sure where the relevant section starts or ends. I have marked lines that seem important in bold and/or colour.

    2022-03-23 19:26:49, Info                  CBS    TI: --- Initializing Trusted Installer ---

    2022-03-23 19:26:49, Info                  CBS    TI: Last boot time: 2022-03-21 23:32:07.512

    2022-03-23 19:26:49, Info                  CBS    Starting TrustedInstaller initialization.

    2022-03-23 19:26:49, Info                  CBS    Ending TrustedInstaller initialization.

    2022-03-23 19:26:49, Info                  CBS    Starting the TrustedInstaller main loop.

    2022-03-23 19:26:49, Info                  CBS    TrustedInstaller service starts successfully.

    2022-03-23 19:26:49, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart

    2022-03-23 19:26:49, Info                  CBS    Startup processing thread terminated normally

    2022-03-23 19:26:53, Info                  CBS    Starting TiWorker initialization.

    2022-03-23 19:26:53, Info                  CBS    Ending TiWorker initialization.

    2022-03-23 19:26:53, Info                  CBS    Starting the TiWorker main loop.

    2022-03-23 19:26:53, Info                  CBS    TiWorker starts successfully.

    2022-03-23 19:26:53, Info                  CBS    Universal Time is: 2022-03-23 08:26:53.415

    2022-03-23 19:26:53, Info                  CBS    Loaded Servicing Stack v6.3.9600.19991 with Core: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.19991_none_fa0fb7959b4c8c91\cbscore.dll

    2022-03-23 19:26:53, Info                  CSI    00000001@2022/3/23:08:26:53.426 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff95d407f69 @0x7ff961533fe4 @0x7ff9615335eb @0x7ff7bd4dd69a @0x7ff7bd4ddf4f @0x7ff9829f2613)

    2022-03-23 19:26:53, Info                  CBS    SQM: Initializing online with Windows opt-in: False

    2022-03-23 19:26:53, Info                  CBS    SQM: Cleaning up report files older than 10 days.

    2022-03-23 19:26:53, Info                  CBS    SQM: Requesting upload of all unsent reports.

    2022-03-23 19:26:53, Info                  CBS    SQM: Failed to start upload with file pattern: C:\windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]

    2022-03-23 19:26:53, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]

    2022-03-23 19:26:53, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\windows\servicing\sqm\*_all.sqm, flags: 0x6

    2022-03-23 19:26:53, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

    2022-03-23 19:26:53, Info                  CBS    NonStart: Set pending store consistency check.

    2022-03-23 19:26:53, Info                  CBS    Session: 30949007_3225858855 initialized by client DISM Package Manager Provider.

    2022-03-23 19:26:53, Info                  CBS    Client specifies store corruption detect and repair.

    2022-03-23 19:26:53, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30949007_3225858855

    2022-03-23 19:26:53, Info                  CBS    Reboot mark set

    2022-03-23 19:26:53, Info                  CBS    Winlogon: Registering for CreateSession notifications

    2022-03-23 19:35:00, Info                  CBS    Repr: CBS Store check completes

    2022-03-23 19:35:03, Info                  CSI    00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xf370d6fbf0

    2022-03-23 19:35:03, Info                  CSI    00000003 Creating NT transaction (seq 1), objectname [6]"(null)"

    2022-03-23 19:35:03, Info                  CSI    00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x3ac

    2022-03-23 19:35:03, Info                  CSI    00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"

    2022-03-23 19:35:03, Info                  CSI    00000006@2022/3/23:08:35:03.388 Beginning NT transaction commit...

    2022-03-23 19:35:03, Info                  CSI    00000007@2022/3/23:08:35:03.390 CSI perf trace:

    CSIPERF:TXCOMMIT;1943

    2022-03-23 19:35:03, Info                  CSI    00000008 CSI Store 1045554415520 (0x000000f36fe647a0) initialized

    2022-03-23 19:35:03, Info                  CSI    00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:96{48}]"6.3.9600.19991 (winblue_ltsb_escrow.210322-1741)".

    2022-03-23 19:35:03, Info                  CSI    0000000a@2022/3/23:08:35:03.490 Starting corruption detection (InnerFlags=5)

    2022-03-23 20:22:04, Info                  CSI    0000000b@2022/3/23:09:22:04.365 Corruption detection complete. numCorruptions = 0, Disp = 1.

    2022-03-23 20:22:04, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.

    2022-03-23 20:22:04, Info                  CBS    Repr: CSI Store check completes

    2022-03-23 20:22:04, Info                  CBS    Exec:Only CSI metadata corruption found, Process CSI repair.

    2022-03-23 20:22:04, Info                  CSI    0000000c Creating NT transaction (seq 2), objectname [6]"(null)"

    2022-03-23 20:22:04, Info                  CSI    0000000d Created NT transaction (seq 2) result 0x00000000, handle @0x268

    2022-03-23 20:22:04, Info                  CSI    0000000e@2022/3/23:09:22:04.630 Beginning NT transaction commit...

    2022-03-23 20:22:04, Info                  CSI    0000000f@2022/3/23:09:22:04.862 CSI perf trace:

    CSIPERF:TXCOMMIT;271105

    2022-03-23 20:22:04, Info                  CSI    00000010 StoreCorruptionRepair transaction completed.

    2022-03-23 20:22:04, Info                  CBS    Repr: Finished repairing CSI store.

    2022-03-23 20:22:04, Info                  CBS    Ensure CBS corruption flag is clear

    2022-03-23 20:22:04, Info                  CBS    Ensure WCP corruption flag is clear

    2022-03-23 20:22:04, Info                  CBS    

    =================================

    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

    Total Operation Time: 3311 seconds.

    2022-03-23 20:22:04, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]

    2022-03-23 20:22:04, Info                  CBS    Count of times corruption detected: 1

    2022-03-23 20:22:04, Info                  CBS    Seconds between initial corruption detections: -1

    2022-03-23 20:22:04, Info                  CBS    Seconds between corruption and repair: -1

    2022-03-23 20:22:07, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard

    2022-03-23 20:22:07, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard

    2022-03-23 20:22:08, Info                  CBS    Reboot mark cleared

    2022-03-23 20:22:08, Info                  CBS    Winlogon: Deregistering for CreateSession notifications

    2022-03-23 20:22:08, Info                  CBS    Winlogon: Stopping notify server

    2022-03-23 20:22:08, Info                  CBS    Winlogon: Unloading SysNotify DLL

    2022-03-23 20:22:08, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30949007_3225858855 [HRESULT = 0x00000000 - S_OK]

    2022-03-23 20:22:08, Info                  CBS    Session: 30949007_3225858855 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]

    2022-03-23 20:22:09, Info                  CBS    Session: 30949015_2022155777 initialized by client DISM Package Manager Provider.

    2022-03-23 20:24:09, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

    2022-03-23 20:24:09, Info                  CBS    TiWorker signaled for shutdown, going to exit.

    2022-03-23 20:24:09, Info                  CBS    Ending the TiWorker main loop.

    2022-03-23 20:24:09, Info                  CBS    Starting TiWorker finalization.

    2022-03-23 20:24:09, Info                  CBS    Ending the TrustedInstaller main loop.

    2022-03-23 20:24:09, Info                  CBS    Starting TrustedInstaller finalization.

    2022-03-23 20:24:09, Info                  CBS    Ending TrustedInstaller finalization.

    2022-03-23 20:24:09, Info                  CBS    Ending TiWorker finalization.

    So is this saying that some metadata corruption was the only problem detected?

    (If so, why isn't it shown in this log's "Summary" section either?)

    And was it reported as successfully fixed in this log? I see an 'OK' result, but cannot tell whether it's a general result of running DISM, or specific to repairing the metadata.

    —DIV

    Was this answer helpful?

    0 comments