Windows 10 and DISM help required please

It my help if you took a few steps back and explained what prompted you to try DISM in the first place. Were you experiencing problems with your system?

Generally, before trying DISM the first step is to check for corrupted system files. In an admin command prompt type...
SFC /SCANNOW

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 up to 3 times with Fast Startup turned off and restarting the computer after each time to completely fix everything that it's able to.

Run SFC Command in Windows 10

The error 0x80010108 seems to be associated with accessing the update servers, it has also been seen with windows update and windows upgrades. The 'Wait a few minutes and try running the command again' message is just in case the problem is at the server end.

If after running sfc /scannow you still have this error, try the /LimitAccess option to prevent DISM from contacting the update servers.

dism /online /cleanup-image /ScanHealth /LimitAccess

Recently I had a support person from where I purchsed this PC log in remotely in order to 1) Partition my hard drive, 2) Install Windows 7 in that partition. No matter what he tried, Windows 7 could not be installed. On several occasions I had to use the power button as the aborted Windows 7 install did not allow the PC to reboot. Since than I have experienced the occasional hang where I needed to use the Power button to reboot the system. Also, I had a message two days ago that suggested that I did 'something' as there was possible corruption. When I did that it was reported that an invalid IP configuration had been fixed and something else. That may have explained why I was having problems with accessing the Internet and I was unable to connect to my WiFi Router. That issue has not returned. I have already run sfc /scannow at least one. I am running it now as suggested. Fast Starup is turned on. I run commands from Command Prompt (Admin).

sfc /scannow has finished. The /LimitAccess command gave an 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>dism /online /cleanup-image /ScanHealth /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0


Error: 87

The limitaccess option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>

Will run sfc /scannow again tomorrow.

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

Nolly1959 said:

....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>

...Can I now conclude that I have a Healthy Windows 10 system?

Finally! :) - yes, it would appear so...

Any idea what fixed the DISM issues?

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...

...what many are not realizing is that both DISM /Online and DISM /Image: (run offline, after booting from install media) do actually repair the component store, if there is any other issue (aside from the FlightSigning package)...

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

Nolly1959 said:

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

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.