sfc and DISM both fail, windows 10 version 1803

Hi,

Back at this again after the holiday. Msoft has continued to try to update this machine to 1903 & 1909 with no success.

Reran sfc and dism again this AM. There are no servicing stack error msgs in the cbs log that I can see. It still has these msgs which seem to get us back to ncbservices:

2019-12-06 12:14:50, Error                 CSI    00000007 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #1400878# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 164 ('\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 = @0x690f8fb060, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-12-06 12:14:50, Error                 CSI    00000008@2019/12/6:17:14:50.911 (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]

The dism log also has the same as before:

2019-12-06 12:07:46, Warning               DISM   DISM OS Provider: PID=12264 TID=11348 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       

I don't know how to trace that back to a specific kbxxx update file to reinstall. This install is now up to 17134.1099. Other msgs show the DismCore.dll rev is 17134.1.

There are multiple dism msgs like

2019-12-06 11:14:25, Info                  CSI    00000001 Shim considered [l:126]'??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.1063_none_c3f457ba6965bb0b\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2019-12-06 11:14:25, Info                  CSI    00000002 Shim considered [l:123]'??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.1063_none_c3f457ba6965bb0b\wcp.dll' : got STATUS_SUCCESS

Since they are info, I had assumed that the process used the alternate choice and continued.

• Would it be useful to put any files on what now appears to be onedrive?
• Do you think that it might fix the current problem if I uninstalled the last 4 kbxxx updates and reinstall all since 1 Aug 2019? Is there a significant risk in doing that?

thanks again,

pete

Hi,

It looks like there are a number of messages that pop up in separate places, all of which could relate to a common problem.

The systems log repeats the following msg about every 5 min during normal system use:

The NcbService service terminated with the following error:

NcbService is not a valid Win32 application.

This is sometimes accompanied by:

The Connected Devices Platform Service service depends on the NcbService service which failed to start because of the following error:

Connected Devices Platform Service is not a valid Win32 application.

Running sfc /scannow generates:

2019-11-24 15:39:00, Error                 CSI    000028ab (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #36210529# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = a18 ('\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 = @0x296af7b4f0, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-11-24 15:39:00, Error                 CSI    000028ac@2019/11/24:20:39:00.847 (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]

The dism logs don't have a related msg, but does have dll problems:

2019-11-29 12:40:18, Warning               DISM   DISM OS Provider: PID=46804 TID=66256 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

These are followed by several failure to load provider msgs, then to failure to repair corruption.

pete

Hmmm,

Another problem. /scannow failed again at 44%, with the "couldn't perform requested operation" msg. The new section of sfcdetails.txt looks the same as the previous run. But near the end of the cbs log, we find

2019-11-25 14:34:55, Info                  CSI    00002813 [SR] Beginning Verify and Repair transaction

2019-11-25 14:34:56, Error                 CSI    00002814 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #36210529# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 3d8 ('\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 = @0x2e40e7b490, data = {l:0 b:}, byteoffset = 0, key = (null))

[gle=0xd000a2a7]

2019-11-25 14:34:56, Error                 CSI    00002815@2019/11/25:19:34:56.370 (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-25 14:34:56, Info                  CBS    Added C:\windows\Logs\CBS\CBS.log to WER report.

2019-11-25 14:34:56, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2019-11-25 14:34:56, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-25 14:34:56, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-25 14:34:56, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-25 14:34:56, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-11-25 14:34:57, Error                 CSI    00002816 (F) c000a2a7 [Error,Facility=(system),Code=41639 (0xa2a7)] #36210528# from Windows::Rtl::SystemImplementation::CFile::ReadFile(Flags = 3, Buffer = {l:0 ml:376832 b:}, Offset = 0, Disposition = 0)[gle=0xd000a2a7]

So that's 1 file not found, maybe 2?

pete

You only need the latest one of a SSU..

You said earlier the SFC would not complete.  If it does not, then if you look at the listing, starting from the bottom up, you will see a "Cannot repair member file" or something similar...

Hi,

The findstr string doesn't seem to generate anything useful. It yields blocks of "verifying (x) components", "beginning verify and repair...", and "verify complete". If x=1, it tests 4-5 components and always completes. If x=100, it loops through many times, but the last loop never completes. The file just starts over again later with a new run, not even a space between entries.

The dism runs do contain error msgs related to servicing stacks. See the extracted msgs above from 14 Nov.

Not sure how to track between those error msgs and the installed updates. I have looked at the list of 1803 updates for the past few months and confirmed what can be uninstalled and what can't. Control panel shows 2 windows code kb files and 2 for .net framework that can be uninstalled. There are also 2 ssu updates that can not be backed out. Based on the windows catalog pgs, it looks like there are about 15 updates to be installed. Maybe some of those were completely overwritten by later updates, so the list appears to be longer.

thanks,

pete