Windows 10: Windows 10 and DISM help required please

Sorry, your right. /LimitAccess only applies when using /RestoreHealth.

 

Ran the following overnight:

dism /online /cleanup-image /restorehealth /limitaccess

This failed as before. See partial log file for this session.





I have run sfc /scannow twice this morning having shutdown and rebooted before each run. Currently running it for the third time. So far sfc has come bakc with any error. see below.

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>

So, sfc finds nothing and I cannot run DISM to completion.

Later .....

sfc /scannow completed the third run without reporting any problems.

The following DISM command ran succesffully*Smile See below.

C:\windows\system32>dism /online /cleanup-image /RestoreHealth /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\windows\system32>

Even later .....

Ran the DISM command again but this time without the /limitaccess. See results below.

C:\windows\system32>dism /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\windows\system32>

**** Something I having reported so far is that i did run chkdsk /f C: before the last two runs of DISM ****
No errors were reported.

Can I now conclude that I have a Healthy Windows 10 system?
Any idea what fixed the DISM issues?

 

Finally! *Smile - yes, it would appear so...

At a guess, you have nibbled away at the problem bit by bit until it was fixed. Apparently DISM could have corrected some errors along the way, even if it reported a failure at the end...

Creators update component store shows corruption but unable to repair - Post #93

A forensic examination of the CBS.log may show if/when/what was repaired, but as DISM now reports 100% success that would only be an exercise to satisfy curiosity.

 

OK and many thanks. If I find the CBS.log (did try) I might take a look to see if there is anything obvious.

I guess this post can be Mark(ed) as Solved. Should I do that?

Cheers,
Nolly

 

Yes, I would as DISM now works without error.

Should other problems appear later on down the line you can always start a new thread. I'm subscribed to this thread, so if you post a link here I'll be alerted.