Share via

Ran sfc /scannow have corrupt files and cbs.log file please advise

Michael Smith 0 Reputation points
2026-05-15T19:21:15.9833333+00:00

I am having issues with windows spontaneously opening internet. I opened command prompt as admin and ran sfc/scannow which prompted corrupt files that were not able to fix. I have the CBS.log file. Please advise

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

2 answers

Sort by: Most helpful
  1. Ivan B 111.3K Reputation points Independent Advisor
    2026-05-15T20:06:51.4233333+00:00

    Hi ,

    Search for msinfo32.exe in the search bar, take a screenshot, and post it here so we can see the correct laptop model or desktop configuration.

    Please upload the logs to OneDrive or Google Drive.

    Thanks

    Was this answer helpful?

    0 comments No comments

  2. Q&A Assist
    2026-05-15T19:21:35.5566667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Run the built-in repair tools in this order and re-check for corruption.

    1. Run DISM to repair the component store
      1. Open an elevated Command Prompt (Run as administrator).
      2. Run:
              DISM.exe /Online /Cleanup-image /Restorehealth
        
      3. Wait for the command to complete (this can take several minutes).
    2. Run System File Checker again
      1. In the same elevated Command Prompt, run:
              sfc /scannow
        
      2. Wait until verification reaches 100% and check the result message.
      3. If it now reports that corruption was found and successfully repaired, or that no integrity violations were found, the system files are healthy.
    3. If SFC still reports unrepairable corruption
      • View the SFC details from CBS.log to identify the problematic files:
        1. In an elevated Command Prompt, run:
                  findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
          
        2. Open sfcdetails.txt from the desktop to see which files could not be repaired.
      • For entries that SFC cannot fix, replace the corrupted file manually with a known good copy as described in the System File Checker guidance.
    4. If corruption persists even after DISM and SFC
      • The official guidance is to contact technical support, as persistent corruption may indicate deeper system issues that require advanced troubleshooting or repair.

    These steps address the “Windows Resource Protection found corrupt files but was unable to fix some of them” result and should be completed before further investigating symptoms such as spontaneous browser or internet windows opening.


    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.