sfc and DISM both fail, windows 10 version 1803

Anonymous
2019-11-03T18:38:13+00:00

Hi,

I'm running a Lenovo G510, originally delivered with Windows 8, but upgraded to 10 about 2 years ago. A failed update uncovered the fact that there may be a problem with the current installation of 1803. sfc /scannow fails with the message "windows resource protection could not perform the requested operation". DISM fails with "the WOF driver encountered a corruption in the compressed file’s resource table". CHKDSK appears to complete successfully. 

thanks in advance,

pete vh

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

47 answers

Sort by: Newest
  1. Anonymous
    2019-11-14T17:24:22+00:00

    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

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-11-14T15:23:50+00:00

    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

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-11-11T20:58:57+00:00

    Hi,

    Not much progress to report. Msoft had a new kb to 1803, so I tried that. Installed without a hitch, but /scannow still fails with the same errors. Today, tried to download graphics drivers from Intel, and 1809 via the Msoft catalog pg & 1903 via mediacreationtool. No success with any.

    pete vh

    Was this answer helpful?

    0 comments No comments
  4. Virginia M 42,075 Reputation points Independent Advisor
    2019-11-10T15:43:21+00:00

    Yes as it’ll be using the source on the version downloaded.

    If this still fails then unfortunately you’re looking at a clean install of the 1803 or if you’re willing you can try clean installing 1903.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-11-10T15:31:24+00:00

    Hi again,

    Just to review the symptoms so far::

    As noted above above, during normal operations the systems log has a message every few minutes that NcbService is not a valid win32 application, but it is in the task manager services list, as stopped.

    Ran sfc scannow this AM, It ran for several minutes, then dIed in the same ~43%, with the same resource protection error msg. Cbs log had 2 messages associated with the ncbservices.dll file. SFC then stops. The Applications log has 3 msgs from Windows error reporting. Nothing in systems log. Running dism gives a similar dll msgs. Will confirm the sequence of errors.

    I downloaded 1803 iso from tb.rz-adguard.net. The only 1803 listed was version 17134.1. Winver says that 17134.1099 is the current running version. If I try to run dism using the iso as a source, does that mean it might try to repair this installation with a file 1 1/2 years out of date?

    thanks for your patience,

    pete vh

    Was this answer helpful?

    0 comments No comments