A CBS.log review is not possible from the shared file here, but the next supported steps are clear.
- Extract only the SFC entries from CBS.log.
Open Command Prompt as administrator and run:
This creates sfcdetails.txt on the desktop and makes the SFC results easier to read.findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" - Check whether the unrepaired entries are real corruption or just expected CBS entries. Some CBS.log entries can report files such as Img11.jpg as not repaired even when SFC completed successfully. That can happen because the file change is recorded in CBS.log even though Windows Resource Protection does not protect that file.
- Since the actual problem is User Profile Service failed the sign-in, check the User Profile Service logs. In Event Viewer, go to: Applications and Services Logs → Microsoft → Windows → User Profile Service → Operational Review events from the time the sign-in failed.
- If the Operational log is not enough, enable the diagnostic log temporarily.
In Event Viewer:
- Select View → Show Analytic and Debug Logs
- Go to Applications and Services Logs → Microsoft → Windows → User Profile Service → Diagnostic
- Select Enable Log Reproduce the sign-in issue, review the events, then disable the log after troubleshooting because this logging is much more detailed.
- If SFC reported corruption it could not fix, use DISM to repair the component store.
Run an elevated command prompt and use:
Then verify again with:DISM /Online /Cleanup-Image /RestoreHealth
After that, review C:\Windows\Logs\CBS\CBS.log again.DISM /Online /Cleanup-Image /ScanHealth - If DISM reports source-missing or unresolved corruption, the supported repair path is to provide source files and rerun DISM with
/Source, for example:
This requires copying the correct versions of the corrupted files into C:\temp\Source first.DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess - If the profile issue still remains after checking the User Profile Service logs and repairing corruption, focus on the profile-specific events rather than CBS alone. CBS.log helps with system file and component store issues, but the sign-in failure is more directly diagnosed from the User Profile Service Operational and Diagnostic logs.
References:
- The CBS.log file contains entries that some files aren't repaired even after you successfully run the SFC utility on a Windows Server based computer
- Use the System File Checker tool to repair missing or corrupted system files
- Troubleshoot user profiles with events
- Fix Windows Update corruptions and installation failures