sfc /scannow does not create CBS.log file

Hey everyone.

I used sfc /scannow command and it found corrupted files but it couldn't fix them. So it says i can manually check these corrupted files, with CBS.log; but it doesn't create CBS.log file.

I have tried these commands;
set WINDOWS_TRACING_LOGFILE=C:\TEMP\CBS.log
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log


But these commands didn't solve my problem. Also DISM commands couldn't fix what the sfc command couldn't fix.

My winver:

@Kyhi with your .bat file, detail txt is empty too



Any ideas?

Paul Black said:

Hello @Delka,

Code:

findstr /C:"[SR]" %SystemRoot%\Logs\CBS\CBS.log > %UserProfile%\Desktop\SFC_ERRORS.log

Hello, thanks for your reply, here is the result:

Paul Black said:

Change the CMD Prompt to C:\Windows\system32 and re-run the command I posted.

Code:

C:\Windows\system32> findstr /C:"[SR]" %SystemRoot%\Logs\CBS\CBS.log > %UserProfile%\Desktop\SFC_ERRORS.log

Here is the result (SFC_ERRORS.log file is empty too):

Paul Black said:

Have you looked to see if you have actually got a %SystemRoot%\Logs\CBS folder, and if so, what files do you have in there?

There is an CBS folder, but its empty.

- - - Updated - - -

Solved with DISM command - install.wim:

6 Best Solutions To Run DISM Command In Windows (2022)

4th way.
@Paul Black , thanks for your effort.

Paul Black said:

Hello @Delka,

Is there a sfc.exe file in %SystemRoot%\System32 ?



You could also look at Option 1 here => How to Repair System Files with SFC Command in Windows 10

You say that DISM /Online /Cleanup-Image /RestoreHealth also does NOT work. Are there ANY messages ?

rooscoota said:

IDK why i couldn't explain this. Let me be more clear.

-SFC /scannow works.
-SFC /scannow finds corrupted files.
-SFC /scannow could not repair the corrupted files.
-SFC /scannow says: "Check CBS.log file."
-But there is no CBS.log file. Because SFC /scannow couldnt - didnt create CBS.log file.

-And yes, there is no CBS.log file in the "%SystemRoot%\Logs\CBS" folder.

What i mean by DISM didnt, work;
Lets assume that sfc /scannow found "file 1.exe" is corrupted, and couldnt repair "file 1.exe"
What i mean is, DISM is also uncapable of repairing "file 1.exe"

And last update is:
I used DISM command with install.wim file, and i managed to repair the corrupted (file 1 .exe) files. So now sfc /scannow says "there is no corrupted files"