sfc and DISM both fail, windows 10 version 1803

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

Looks like I forgot to list the errors of the 2nd dism log earlier. It had the same pattern of "unable to set the dll search path" followed by the set of "failed to load the provider".

thanks,

pete vh

OK,

Spent a couple days backing up files, creating new disk image (acronis, took forever), made recovery drive of this install, using Windows tools. Then reran all the Windows update methods, intel driver updates, etc. All failed again.

Then went back into the Use dism to repair windows 10 image procedure. Mounted the 1803 iso, got the data, ran through step 6. This was using the /limitaccess modifier. That failed at 32% with the same WOF driver msg as before. The dism log has errors as follows:

2019-11-14 09:09:18, Warning               DISM   DISM OS Provider: PID=5132 TID=7632 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

2019-11-14 09:09:18, Warning               DISM   DISM Provider Store: PID=5132 TID=7632 Failed to load the provider: C:\Users\pete\AppData\Local\Temp\01AB1E1B-10A2-4F28-9C35-3BF984C6388A\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2019-11-14 09:09:19, Warning               DISM   DISM Provider Store: PID=5132 TID=7632 Failed to load the provider: C:\Users\pete\AppData\Local\Temp\01AB1E1B-10A2-4F28-9C35-3BF984C6388A\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2019-11-14 09:09:20, Warning               DISM   DISM Package Manager: PID=5132 TID=7632 CBS AddSource failed with HRESULT=0x80070003! - CDISMPackageManager::Internal_Finalize

2019-11-14 09:09:20, Warning               DISM   DISM Package Manager: PID=5132 TID=7632 CBS AddSource failed with HRESULT=0x80070003! - CDISMPackageManager::Internal_Finalize

2019-11-14 09:09:20, Info                  DISM   DISM Package Manager: PID=5132 TID=7632 CBS session options=0x20100! - CDISMPackageManager::Internal_Finalize

2019-11-14 09:20:29, Info                  DISM   DISM Package Manager: PID=5132 TID=5812  Error in operation: (null) (CBS HRESULT=0x80071160) - CCbsConUIHandler::Error

2019-11-14 09:20:29, Error                 DISM   DISM Package Manager: PID=5132 TID=7632 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80071160)

2019-11-14 09:20:29, Error                 DISM   DISM Package Manager: PID=5132 TID=7632 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80071160)

2019-11-14 09:20:29, Error                 DISM   DISM Package Manager: PID=5132 TID=7632 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)

2019-11-14 09:20:29, Error                 DISM   DISM Package Manager: PID=5132 TID=7632 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)

The cbs log has:

2019-11-14 09:20:27, Error                 CSI    00000007 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #1400968# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 604 ('\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 = @0xe036fb060, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-11-14 09:20:27, Error                 CSI    00000008@2019/11/14:14:20:27.943 (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-14 09:20:28, Error                 CSI    00000009 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #1400967# from Windows::Rtl::SystemImplementation::CFile::ReadFile(Flags = 3, Buffer = {l:0 ml:376832 b:}, Offset = 0, Disposition = 0)[gle=0xd000a2a7]

2019-11-14 09:20:28, Error                 CSI    0000000a (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #261# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd000a2a7]

2019-11-14 09:20:28, Error                 CSI    0000000b (F) HRESULT_FROM_WIN32(4448) #260# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 2f8 (''), disp = 0)[gle=0x80071160]

2019-11-14 09:20:28, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80071160 - Unknown Error]

2019-11-14 09:20:29, Error                 CBS    Session: 30776053_468109235 failed to perform store corruption detect and repair operation. [HRESULT = 0x80071160 - Unknown Error]

Tried to run again, this time without limitaccess. Failed again. cbs log:

2019-11-14 09:26:31, Error                 CSI    00000007 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #1400956# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 2cc ('\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 = @0xeaca1faf40, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-11-14 09:26:31, Error                 CSI    00000008@2019/11/14:14:26:31.012 (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-14 09:26:31, Error                 CBS    Session: 30776055_1689398497 failed to perform store corruption detect and repair operation. [HRESULT = 0x80071160 - Unknown Error]

Will take a look at the other logs, but they will probably be summaries of the above. Any thoughts on what the WOF driver is and what the compressed file resource table might be?

thanks,

pete vh