Windows 10 Recovery Tools - Bootable Rescue Disk

butterfly said:

[B]I tried to use the following comand (after sfc /scannow in elevated cmd) to extract only the SR rows from the CBS.log:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"
But while it actually works in Windows 7 , under Windows 10 simply continues to blink and the sfcdetails.txt is empty.

It certainly works for me in Windows 10. I copied your findstr like this

Code:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"

and it worked perfectly even while sfc /scannow was still running...



Try deleting cbs.log and trying again. Maybe something is locking it for you for some reason.

Also check the size of the file cbs.log (if it is zero bytes it might explain the findstr not working...)

Hi lx07,
This is a bit frustrating.
So the command is correct; cbs.log is not zero size.

Attached is a SR filtered version after exporting that Windows 10 cbs.log into Windows 7 and running the findstr from that PC... I could not find another workaround. Now I deleted those cbs.logs and running again sfc.

Edit: Thanks Superfly; I still have to test your command in PS. Actually according to the sfcdetails it appears the PS is damaged.
Any idea about the damage?!

Thank you for your example Kyhi!
I will begin to have more practice with your Image Health utility!

Meanwhile above I already attached my sfcdetails... which of the 12 options (or sequence) is suggested to fix those SR errors?

Superfly said:

Nope - how is PS damaged.?

I really don't know.. no virus or strange things. I am actually able to open PS.
It's my understanding it could be damaged reading a simple line like this :
[SR] Could not reproject corrupted file [ml:140{70},l:138{69}]"\??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SmbShare\en-US"\[l:40{20}]"SmbLocalization.psd1"; source file in store is also corrupted