[10v1709b16299 x64] WRP found corrupt files but was unable to fix some of them

[gunhunter]

I was running the sfc /scannow on command prompt to repair corrupted files but after the verification progress completed, there is an error message displaying window resource protection found corrupt files but was unable to fix some of them. I will include my CBS compressed folder as well. Can you help me to check out from my CBS logfile whether the files are actually corrupted or the SFC just gave the false positive. I am currently using Windows 10 Pro 64-bit. Thank you very much.

 

[zcomputerwiz]

2018-01-22 01:52:43, Info                  CSI    00007d90 [SR] Verify complete
2018-01-22 01:52:43, Info                  CSI    00007d91 [SR] Repairing 2 components
2018-01-22 01:52:43, Info                  CSI    00007d92 [SR] Beginning Verify and Repair transaction
2018-01-22 01:52:44, Info                  CSI    00007d93 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\zh-hk\zh-hk\ChtAP.sdc from store
2018-01-22 01:52:44, Info                  CSI    00007d94 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\zh-hk\zh-hk\chtzhy.spd from store
2018-01-22 01:52:44, Info                  CSI    00007d95@2018/1/21:17:52:44.436 CSIPERF - FileMapsCreated 124ms
2018-01-22 01:52:44, Info                  CSI    00007d96 CSIPERF - FilePI Commit 125ms
2018-01-22 01:52:44, Info                  CSI    00007d97@2018/1/21:17:52:44.447 Primitive installers committed for repair
2018-01-22 01:52:44, Info                  CSI    00007d98 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\zh-tw\zh-tw\ChtAP.sdc from store
2018-01-22 01:52:44, Info                  CSI    00007d99 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\zh-tw\zh-tw\chtzhy.spd from store
2018-01-22 01:52:44, Info                  CSI    00007d9a@2018/1/21:17:52:44.594 Primitive installers committed for repair
2018-01-22 01:52:44, Info                  CSI    00007d9b [SR] Repair complete
2018-01-22 01:52:44, Info                  CSI    00007d9c [SR] Committing transaction
2018-01-22 01:52:44, Info                  CSI    00007d9d Creating NT transaction (seq 1)
2018-01-22 01:52:44, Info                  CSI    00007d9e Created NT transaction (seq 1) result 0x00000000, handle @0x56c
2018-01-22 01:52:44, Error                 CSI    00007d9f (F) STATUS_OBJECT_NAME_NOT_FOUND #45398344# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation|AllowTransactionalConflict|0x00000400), handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0xa9be97c798->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[36]'\??\C:\WINDOWS\System32\zh-hk\zh-hk\'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa9be97c7f0, as = (null), fa = (FILE_ATTRIBUTE_DIRECTORY), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2018-01-22 01:52:44, Error                 CSI    00007da0@2018/1/21:17:52:44.681 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(2938): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2018-01-22 01:52:44, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2018-01-22 01:52:44, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20180121171459.log to WER report.
2018-01-22 01:52:44, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2018-01-22 01:52:44, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-01-22 01:52:44, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-01-22 01:52:54, Error                 CSI    00007da1 (F) STATUS_OBJECT_NAME_NOT_FOUND #45398343# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemDirectory(flags = (SharingViolationIsOk|TransactionalConflictIsOk|DeletePendingIsOk), da = (FILE_GENERIC_READ), dn = [l:36 ml:45]'\??\C:\WINDOWS\System32\zh-hk\zh-hk\', sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
[gle=0xd0000034]
2018-01-22 01:52:54, Info                  CSI    00007da2 Error STATUS_OBJECT_NAME_NOT_FOUND while executing operation HardLinkFile on [l:181]'\SystemRoot\WinSxS\amd64_microsoft-onecore-t..-dictionaries-zh-hk_31bf3856ad364e35_10.0.16299.15_none_8b3df0c77dcfde67\zh-hk\ChtAP.sdc, \??\C:\WINDOWS\System32\zh-hk\zh-hk\ChtAP.sdc'

2018-01-22 01:52:54, Error                 CSI    00007da3 (F) STATUS_OBJECT_NAME_NOT_FOUND #45398051# from ApplyTransactionPOQsToSil(...)[gle=0xd0000034]
2018-01-22 01:52:54, Error                 CSI    00007da4@2018/1/21:17:52:54.816 (F) onecore\base\wcp\componentstore\com\store_transaction.cpp(1448): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function ApplyTransactionPOQsToSil expression: (null)

Please run SFCFix to see if it will automatically correct this issue.

• First download and run a copy of the tool from https://www.sysnative.com/forums/downloads/sfcfix/.
• Work through any on-screen prompts and then await completion (runtime can be upwards of 15 minutes depending on the options you selected during the on-screen prompts).
• Once it has finished, if there are any unrepaired corruptions (the tool will notify you if it has succeeded in repairing all corruptions if they're simple in which case we're no longer needed) or unresolved problems with your computer, you need to post us the complete logfile which opens on exit. Simply copy (Ctrl-A, Ctrl-C) and paste (Ctrl-V) the entire logfile (SFCFix.txt) into your reply.