sfc and DISM both fail, windows 10 version 1803

Hi,

Not sure you would have been notified of the later posts.

pete

Note that the above should have said x64.

Also, should probably go through and uninstall the updates one at a time starting with the newest, then reinstall from the oldest.

pete

How about a different approach -

1. sfc & dism worked in the past.
2. It appears that something has been corrupted in this computer.

The Windows control panel updates pages lists all the installed Windows updates, including 4 in the last month. The last few were all successful, as far as I can tell. Do you think it would be productive to go into msoft catalog pages, download the last 6-8 x86 KB files and install them in order? Will Windows let you load a previous update? Do you think there is much chance that reinstalling some of the older changes might fix a problem that wouldn't have been overwritten by a recent KB? Are these all partial or are they really cumulative? It looks like some newer versions are smaller than some previous.

thanks again,

pete

Hello all,

Haven't given up on this. Spent a couple days trying to solve the original "windows 10 updates fail" (separately documented). No progress there. Still looks like conflicts between Lenovo, Intel graphics driver package, and windows builds 1809 and up. Tried 1909 also - same results.

Have retried sfc and all the various permutations of dism, ending with using the mounted 1803 rev 1 iso image from tech bench. dism still fails at about the same place. The command prompt window again says

The WOF driver encountered a corruption in the compressed file's resource table.

In the dism log, the first error msg is

11-22 09:31:12, Warning            DISM   DISM OS Provider: PID=10444 TID=13116 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

then a few lines later

11-22 09:31:12, Warning               DISM   DISM Provider Store: PID=10444 TID=13116 Failed to load the provider: C:\Users\pete\AppData\Local\Temp\41C09921-5A9B-400E-94ED-C765E4B0E151\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

then

11-22 09:31:12, Warning               DISM   DISM Provider Store: PID=10444 TID=13116 Failed to load the provider: C:\Users\pete\AppData\Local\Temp\41C09921-5A9B-400E-94ED-C765E4B0E151\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

then

11-22 09:32:02, Error                 DISM   DISM Package Manager: PID=10444 TID=13116 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80071160)

2019-11-22 09:32:02, Error                 DISM   DISM Package Manager: PID=10444 TID=13116 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80071160)

2019-11-22 09:32:02, Error                 DISM   DISM Package Manager: PID=10444 TID=13116 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)

2019-11-22 09:32:02, Error                 DISM   DISM Package Manager: PID=10444 TID=13116 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)

2019-11-22 09:32:02, Info                  DISM   DISM Package Manager: PID=10444 TID=13116 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2019-11-22 09:32:02, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80071160

dism then quits.

It looks like sfc and dism are both working, but have bad data for where to find the files to analyze. Any thoughts?

thanks again,

pete

Hi again,

Just reran dism online, cleanup, restore using the mounted iso, did not limit access. Failed at the same point with same corrupted resource table msg.

will keep digging,

pete vh