sfc and DISM both fail, windows 10 version 1803

Hi,

Multiple attempts to update to the latest and greatest have all failed - using update assistant, media creation tool, settings/update, direct download of the update file, troubleshooter, with or without Malwarebytes active, etc. The original problem with the Windows update failure was described in a separate thread. That was tentatively resolved as a compatibility issue starting at 1809, and this thread was opened to address the remaining issues with sfc and DISM. Since they still remain after a successful update to the Oct 2019 release of 1803, a new attempt at update seems unlikely to solve the problem.

I haven't found very good documentation on DISM, but another thread mentioned the options of /analyzecomponentstore & /startcomponentcleanup. They seemed to have found an error, but /restorehealth still didn't get any further before failing. Will try to research other commands.

thanks,

pete vh

Are you running any third party antivirus?

Are you connected to the internet via WiFi or Ethernet?

Is the Time & Date correct?

Run the Windows update troubleshooter - https://support.microsoft.com/en-gb/help/10164/...

Reset the update components:

Open cmd prompt/powershell with admin & enter:

net stop wuauserv

net stop cryptSvc

net stop bits

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 Catroot2.old

net start wuauserv

net start cryptSvc

net start bits

Restart the PC & try updating again.

Try regedit in the search bar & right click on it to choose run as admin, then find: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate & delete the entries WUServer and WIStatusServer in the right pane.

Restart the computer and try to install the updates again.

You can also try the mini update tool:

http://majorgeeks.com/files/details/Windows_upd....

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). Thoroughly research any product advertised on the site before you decide to download and install it.

Saltgrass,

Found the following near the end of the CBS.log file:

2019-11-06 08:01:12, Info                  CSI    000028d6 [SR] Beginning Verify and Repair transaction

2019-11-06 08:01:13, Error                 CSI    000028d7 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #36272606# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 1278 ('\Device\HarddiskVolume5\Windows\WinSxS\amd64_microsoft-windows-n..orkconnectionbroker_31bf3856ad364e35_10.0.17134.1_none_422fdc892e0c33b3\ncbservice.dll'), evt = 0, apcr = NULL, apcc = NULL, iosb = @0x4cd2f7b2e0, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-11-06 08:01:13, Error                 CSI    000028d8@2019/11/6:13:01:13.098 (F) onecore\base\wcp\sil\ntsystem.cpp(3533): Error c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile expression: (null)

[gle=0x80004005]

2019-11-06 08:01:13, Info                  CBS    Added C:\windows\Logs\CBS\CBS.log to WER report.

2019-11-06 08:01:13, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20191106125128.log to WER report.

2019-11-06 08:01:13, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20191102153236.log to WER report.

2019-11-06 08:01:13, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20191102115914.log to WER report.

2019-11-06 08:01:13, Info                  CBS    Added C:\windows\Logs\CBS\CbsPersist_20191031145713.cab to WER report.

2019-11-06 08:01:13, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2019-11-06 08:01:13, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-06 08:01:13, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-06 08:01:13, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-06 08:01:13, Error                 CSI    000028d9 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #36272605# from Windows::Rtl::SystemImplementation::CFile::ReadFile(Flags = 3, Buffer = {l:0 ml:376832 b:}, Offset = 0, Disposition = 0)[gle=0xd000a2a7]

2019-11-06 08:03:22, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

2019-11-06 08:03:22, Info                  CBS    TiWorker signaled for shutdown, going to exit.

Looks like sfc then terminated. The run had been clean up to this point.

pete vh

Hi,

Thanks for the input. Just reran sfc /scannow. It went to 44% then died with the same error code. Ran the script you provided. It went through about 100 iterations of a cycle of "verifying 100 components, beginning..., verify complete", until the last cycle. That never completed. All entries were info, no errors or warnings.

Then downloaded setupdiag. The basic log file output said it was unable to match to any known failure signatures. Will try to sort through the files in the zipped dir. A number of the xml files had an insufficient disk space string in them. Not sure if that was a perceived condition or just one of several potential responses. Selecting properties for C: show about 60% free. Will start digging, but the narrative for the diags indicates it could be above my skill level.

thanks again,

pete vh

Hi,

Depending on the method used, update tries to run setup, goes through all the search, download, verify, etc, then states that it can't tell if the computer is ready for update and says run setup again. Or, if I just go to the msoft site, find the update and tell it to install, it runs part way through and then gives an 0x8007002 error code. Multiple troubleshooting sessions with msoft support lead them to conclude this Lenovo is not compatible with the latest W10 build. So updating to the latest version of 1903 does not look like it will work.

sif and DISM did not fail during the update attempts; they failed between them during multiple attempts to troubleshoot.

thanks,

pete vh