[SOLVED] What does this mean in sfc /scannow ?

Apr 18, 2020
27
2
35
0
My sfc /scannow log ends with these:

2020-12-01 08:16:33, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:33, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201126065941.cab to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201118125643.cab to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201115091758.cab to WER report.
2020-12-01 08:16:33, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CSI 00000253 [SR] Verifying 100 components
2020-12-01 08:16:33, Info CSI 00000254 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:34, Info CSI 00000255 [SR] Verify complete
2020-12-01 08:16:34, Info CSI 00000256 [SR] Verifying 100 components
2020-12-01 08:16:34, Info CSI 00000257 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:34, Info CSI 00000258 [SR] Verify complete
2020-12-01 08:16:34, Info CSI 00000259 [SR] Verifying 100 components
2020-12-01 08:16:34, Info CSI 0000025a [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:36, Info CSI 0000025b [SR] Verify complete
2020-12-01 08:16:36, Info CSI 0000025c [SR] Verifying 100 components
2020-12-01 08:16:36, Info CSI 0000025d [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:36, Info CSI 0000025e [SR] Verify complete
2020-12-01 08:16:36, Info CSI 0000025f [SR] Verifying 100 components
2020-12-01 08:16:36, Info CSI 00000260 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:37, Info CSI 00000261 [SR] Verify complete
2020-12-01 08:16:37, Info CSI 00000262 [SR] Verifying 100 components
2020-12-01 08:16:37, Info CSI 00000263 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 00000264 [SR] Verify complete
2020-12-01 08:16:38, Info CSI 00000265 [SR] Verifying 12 components
2020-12-01 08:16:38, Info CSI 00000266 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 00000267 [SR] Verify complete
2020-12-01 08:16:38, Info CSI 00000268 [SR] Repairing 1 components
2020-12-01 08:16:38, Info CSI 00000269 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 0000026a [SR] Cannot verify component files for Microsoft.FlightSimulator.SimConnect, version 10.0.61259.0, arch x86, versionScope neutral, pkt {l:8 b:67c7c14424d61b5b}, type [l:5]'win32', manifest is damaged (false)
2020-12-01 08:16:38, Info CSI 0000026b [SR] Repair complete
2020-12-01 08:16:38, Error CSI 0000026c@2020/12/1:05:16:38.158 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2020-12-01 08:16:38, Error CSI 0000026d@2020/12/1:05:16:38.159 (F) onecore\base\wcp\componentstore\csd_core.cpp(584): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null)
[gle=0x80004005]
2020-12-01 08:16:38, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:38, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:38, Info CSI 0000026e [SR] Committing transaction
2020-12-01 08:16:38, Info CSI 0000026f Creating NT transaction (seq 1)
2020-12-01 08:16:38, Info CSI 00000270 Created NT transaction (seq 1) result 0x00000000, handle @0x364
2020-12-01 08:16:38, Info CSI 00000271@2020/12/1:05:16:38.159 Beginning NT transaction commit...
2020-12-01 08:16:38, Info CSI 00000272@2020/12/1:05:16:38.159 CSI perf trace:
CSIPERF:TXCOMMIT;41
2020-12-01 08:16:38, Info CSI 00000273 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2020-12-01 08:18:39, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2020-12-01 08:18:39, Info CBS TiWorker signaled for shutdown, going to exit.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-12-01 08:18:39, Info CBS Execution Engine Finalize
2020-12-01 08:18:39, Info CBS Execution Engine Finalize
2020-12-01 08:18:39, Info CBS Deleting the contents of directory: \\?\C:\WINDOWS\CbsTemp
2020-12-01 08:18:39, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp successful
2020-12-01 08:18:39, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2020-12-01 08:18:39, Info CBS Ending the TiWorker main loop.
2020-12-01 08:18:39, Info CBS Starting TiWorker finalization.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-12-01 08:18:39, Info CBS CBS Engine already deactivated
2020-12-01 08:18:39, Info CBS CBS Engine already deactivated
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CoreResourcesUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: SessionManagerFinalize
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: WcpUnload
2020-12-01 08:18:39, Info CSI 00000274 Direct SIL provider: Number of files opened: 246685.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: DrupUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CfgMgr32Unload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: DpxUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: SrUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsEsdUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsEventUnregister
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: AppContainerUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2020-12-01 08:18:39, Info CBS Ending TiWorker finalization.
2020-12-01 08:18:39, Info CBS Ending the TrustedInstaller main loop.
2020-12-01 08:18:39, Info CBS Starting TrustedInstaller finalization.
2020-12-01 08:18:39, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2020-12-01 08:18:39, Info CBS Ending TrustedInstaller finalization.

Please help.
 
Reactions: xenthia

xenthia

Distinguished
Sep 20, 2012
173
16
18,595
4
My pc has so many problems right now that im so confused and angry, hope this isn't something bad.
Well being angry and confused is bad, but Windows 10 is a pretty good Operating System, probably just not a super one, because of some user privacy violations and hidden contracts with big corporates but if you are an average user these should not worry you.

Also that sfc output seems to have taken care of most errors for you, but if you want to be sure, you can also try:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

run them in that order in an Admin level command prompt or PowerShell window. Hope this solved your problem.
 
Apr 18, 2020
27
2
35
0
The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. ... Windows Resource Protection did not find any integrity violations.
Look at my logs, it gives errors.
 

xenthia

Distinguished
Sep 20, 2012
173
16
18,595
4
My sfc /scannow log ends with these:

2020-12-01 08:16:33, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:33, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201126065941.cab to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201118125643.cab to WER report.
2020-12-01 08:16:33, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20201115091758.cab to WER report.
2020-12-01 08:16:33, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-01 08:16:33, Info CSI 00000253 [SR] Verifying 100 components
2020-12-01 08:16:33, Info CSI 00000254 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:34, Info CSI 00000255 [SR] Verify complete
2020-12-01 08:16:34, Info CSI 00000256 [SR] Verifying 100 components
2020-12-01 08:16:34, Info CSI 00000257 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:34, Info CSI 00000258 [SR] Verify complete
2020-12-01 08:16:34, Info CSI 00000259 [SR] Verifying 100 components
2020-12-01 08:16:34, Info CSI 0000025a [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:36, Info CSI 0000025b [SR] Verify complete
2020-12-01 08:16:36, Info CSI 0000025c [SR] Verifying 100 components
2020-12-01 08:16:36, Info CSI 0000025d [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:36, Info CSI 0000025e [SR] Verify complete
2020-12-01 08:16:36, Info CSI 0000025f [SR] Verifying 100 components
2020-12-01 08:16:36, Info CSI 00000260 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:37, Info CSI 00000261 [SR] Verify complete
2020-12-01 08:16:37, Info CSI 00000262 [SR] Verifying 100 components
2020-12-01 08:16:37, Info CSI 00000263 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 00000264 [SR] Verify complete
2020-12-01 08:16:38, Info CSI 00000265 [SR] Verifying 12 components
2020-12-01 08:16:38, Info CSI 00000266 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 00000267 [SR] Verify complete
2020-12-01 08:16:38, Info CSI 00000268 [SR] Repairing 1 components
2020-12-01 08:16:38, Info CSI 00000269 [SR] Beginning Verify and Repair transaction
2020-12-01 08:16:38, Info CSI 0000026a [SR] Cannot verify component files for Microsoft.FlightSimulator.SimConnect, version 10.0.61259.0, arch x86, versionScope neutral, pkt {l:8 b:67c7c14424d61b5b}, type [l:5]'win32', manifest is damaged (false)
2020-12-01 08:16:38, Info CSI 0000026b [SR] Repair complete
2020-12-01 08:16:38, Error CSI 0000026c@2020/12/1:05:16:38.158 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2020-12-01 08:16:38, Error CSI 0000026d@2020/12/1:05:16:38.159 (F) onecore\base\wcp\componentstore\csd_core.cpp(584): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null)
[gle=0x80004005]
2020-12-01 08:16:38, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:38, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2020-12-01 08:16:38, Info CSI 0000026e [SR] Committing transaction
2020-12-01 08:16:38, Info CSI 0000026f Creating NT transaction (seq 1)
2020-12-01 08:16:38, Info CSI 00000270 Created NT transaction (seq 1) result 0x00000000, handle @0x364
2020-12-01 08:16:38, Info CSI 00000271@2020/12/1:05:16:38.159 Beginning NT transaction commit...
2020-12-01 08:16:38, Info CSI 00000272@2020/12/1:05:16:38.159 CSI perf trace:
CSIPERF:TXCOMMIT;41
2020-12-01 08:16:38, Info CSI 00000273 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2020-12-01 08:18:39, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2020-12-01 08:18:39, Info CBS TiWorker signaled for shutdown, going to exit.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-12-01 08:18:39, Info CBS Execution Engine Finalize
2020-12-01 08:18:39, Info CBS Execution Engine Finalize
2020-12-01 08:18:39, Info CBS Deleting the contents of directory: \\?\C:\WINDOWS\CbsTemp
2020-12-01 08:18:39, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp successful
2020-12-01 08:18:39, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2020-12-01 08:18:39, Info CBS Ending the TiWorker main loop.
2020-12-01 08:18:39, Info CBS Starting TiWorker finalization.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-12-01 08:18:39, Info CBS CBS Engine already deactivated
2020-12-01 08:18:39, Info CBS CBS Engine already deactivated
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CoreResourcesUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: SessionManagerFinalize
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2020-12-01 08:18:39, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: WcpUnload
2020-12-01 08:18:39, Info CSI 00000274 Direct SIL provider: Number of files opened: 246685.
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: DrupUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CfgMgr32Unload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: DpxUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: SrUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsEsdUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: CbsEventUnregister
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: AppContainerUnload
2020-12-01 08:18:39, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2020-12-01 08:18:39, Info CBS Ending TiWorker finalization.
2020-12-01 08:18:39, Info CBS Ending the TrustedInstaller main loop.
2020-12-01 08:18:39, Info CBS Starting TrustedInstaller finalization.
2020-12-01 08:18:39, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2020-12-01 08:18:39, Info CBS Ending TrustedInstaller finalization.

Please help.
Hi there how are you. I'm gonna try my best to explain things I can understand in this log to you.

2020-12-01 08:16:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] >>>> this means that windows error reporting could not log the previous events or logs because the SCM.EVM file was not found. This can mean either faulty settings in your Windows Event Viewer or that your hard disk is damaged (either physically or logically). Whatever the reason that file is not append-able or writable. One thing you can do for that error is open Event Viewer and try to look for which log writes to that file cause I couldn't find it on my Windows 10 machine Event Viewer. Here is a link that might help you though if you are using a different version of windows: https://superuser.com/questions/543569/viewing-windows-scms-evm-files

and the rest of the log seems to look like that the repair process has found corrupt files and it has repaired them.

May I ask please what version of Windows you are using?
 
Apr 18, 2020
27
2
35
0
Hi there how are you. I'm gonna try my best to explain things I can understand in this log to you.

2020-12-01 08:16:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] >>>> this means that windows error reporting could not log the previous events or logs because the SCM.EVM file was not found. This can mean either faulty settings in your Windows Event Viewer or that your hard disk is damaged (either physically or logically). Whatever the reason that file is not append-able or writable. One thing you can do for that error is open Event Viewer and try to look for which log writes to that file cause I couldn't find it on my Windows 10 machine Event Viewer. Here is a link that might help you though if you are using a different version of windows: https://superuser.com/questions/543569/viewing-windows-scms-evm-files

and the rest of the log seems to look like that the repair process has found corrupt files and it has repaired them.

May I ask please what version of Windows you are using?
10 Pro 2004 Build 19041
 

xenthia

Distinguished
Sep 20, 2012
173
16
18,595
4
My pc has so many problems right now that im so confused and angry, hope this isn't something bad.
Well being angry and confused is bad, but Windows 10 is a pretty good Operating System, probably just not a super one, because of some user privacy violations and hidden contracts with big corporates but if you are an average user these should not worry you.

Also that sfc output seems to have taken care of most errors for you, but if you want to be sure, you can also try:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

run them in that order in an Admin level command prompt or PowerShell window. Hope this solved your problem.
 
Apr 18, 2020
27
2
35
0
Well being angry and confused is bad, but Windows 10 is a pretty good Operating System, probably just not a super one, because of some user privacy violations and hidden contracts with big corporates but if you are an average user these should not worry you.

Also that sfc output seems to have taken care of most errors for you, but if you want to be sure, you can also try:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

run them in that order in an Admin level command prompt or PowerShell window. Hope this solved your problem.
CheckHealth says No component store corruption detected.
The operation completed successfully.

ScanHealth says No component store corruption detected.
The operation completed successfully.

RestoreHealth says The restore operation completed successfully.
The operation completed successfully.

Hope I don't have any problems. Thanks.
 

xenthia

Distinguished
Sep 20, 2012
173
16
18,595
4
CheckHealth says No component store corruption detected.
The operation completed successfully.

ScanHealth says No component store corruption detected.
The operation completed successfully.

RestoreHealth says The restore operation completed successfully.
The operation completed successfully.

Hope I don't have any problems. Thanks.
Well then in that case all appears to be good to go unless you are infected with a very nefarious highly engineered virus, which if is the case no one can help you but God :D. Cheers. please feel free to pick one of my answers as the solution if they helped you and you feel like your problem is solved. It would make me happy and also if anyone has the same problem and finds themselves in the same situation can find some help here. Thanks. :beercheers:;)
 
Apr 18, 2020
27
2
35
0
Well then in that case all appears to be good to go unless you are infected with a very nefarious highly engineered virus, which if is the case no one can help you but God :D. Cheers. please feel free to pick one of my answers as the solution if they helped you and you feel like your problem is solved. It would make me happy and also if anyone has the same problem and finds themselves in the same situation can find some help here. Thanks. :beercheers:;)
Cheers mate. Thanks for helping.
 

ASK THE COMMUNITY

TRENDING THREADS