sfc and DISM both fail, windows 10 version 1803

You can use Rufus to convert an .iso for use on a usb drive:

https://rufus.ie/

1803.iso here:

https://tb.rg-adguard.net/public.php

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products).

Please do not download any repair tool which is offered by this site other than the ones I mention/recommend..

Thoroughly research any product which is mentioned here before you decide to download and install it.

Hi,

I'll take another look at the procedure, but it looked like it would take us back to the original problem. Using media creation tool, update assistant or other methods results in the latest version of 1903. It appears that that is not compatible with this machine. Have not found a way to get a .iso of 1803. The package I found, downloaded and installed successfully was a .msu, which appears to be and update package, not an image.

Will look again. For a usb drive, I think I need a .img not a .iso?

thanks again,

pete vh

Step 6 or 7 on Ten forum refers to running the cmds using the Windows 10 iso as the source file rather than the Windows installation on the PC,

Those other cmds may work if run before the restore health cmd as this will rectify any Windows problems

What was the outcome of resetting the update components?

Hi,

It looks like the procedure used is largely the same: always run from command prompt, admin mode. Have been using sfc /scannow. With dism, had been running

dism /online /cleanup-image /restorehealth modifiers.

Several other threads have mentioned /checkhealth, /scanhealth, /analyzecomponentstore, /startcomponentcleanup.

I'm tryng to go through those qualifiers in place of /restorehealth, and compare system, applications, CBS, and DISM logs for each.

During normal ops, the system log has a msg every few minutes that says NcbService is not a valid win32 application, but it shows up in the services list in task manager, as stopped. But it seems that when scannow and dism are run, there are often error msgs related to the ncbservice.

Anyhow, thanks for the ref to tenforum. They also had a link to a docs page on msoft that had better info on dism than I had been able to find.

pete vh

If you use the ten forums way of running sfc & dism & it still fails then either the update isn’t compatible or there’s a windows problem which requires a clean install.