please someone help check my CBS.log after running sfc /scannow (i have a problem with user profile service failed the sign-in)

Question

please someone help check my CBS.log after running sfc /scannow (i have a problem with user profile service failed the sign-in)

anonymous 0

https://drive.google.com/file/d/1XCZub_Ic2QpY5-O3vil9Xjj-5R7RSZAZ/view?usp=sharing

0 comments

2 answers

Your answer

Answer 1

EmilyS_726 27,560 Volunteer Moderator

The log file didn't contain anything that indicates the SFC scan found something.

Don't think the User Profile service error was caused by corrupted system files.

I would suggest that you go to Event Viewer > Windows Logs > application

Look for errors from User Profile Service at the time the sign in failed, and post the event ID and full error msg.

anonymous 0 Reputation points

2026-09-11T20:13:02.7766667+00:00

here take a look
anonymous 0 Reputation points

2026-09-11T20:40:39.49+00:00

i already did "reset this pc", but then the problem occurs again after i shut down my pc sometimes
EmilyS726 264.9K Reputation points Independent Advisor

2026-09-11T21:27:49.6166667+00:00

The screenshots confirm a corrupted or inaccessible user profile:

Event 1511: Windows cannot load VICTUS and signs in with a temporary profile.

Event 1512: Windows cannot unload the user’s registry hive because access is denied.

Events 1508/1515/1542 further support a profile-registry problem.

What type of Reset did you do? Keeping data I assume?

Answer 2

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:
```
   findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
```
This creates sfcdetails.txt on the desktop and makes the SFC results easier to read.
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:
```
   DISM /Online /Cleanup-Image /RestoreHealth
```
Then verify again with:
```
   DISM /Online /Cleanup-Image /ScanHealth
```
After that, review C:\Windows\Logs\CBS\CBS.log again.
If DISM reports source-missing or unresolved corruption, the supported repair path is to provide source files and rerun DISM with /Source, for example:
```
   DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
```
This requires copying the correct versions of the corrupted files into C:\temp\Source first.
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: