Windows 10 Recovery Tools - Bootable Rescue Disk

  1. lx07's Avatar
    Posts : 5,479
    2004
       #131

    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...

    Windows 10 Recovery Tools - Bootable Rescue Disk-capture.png

    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...)
      My Computer

  2. Kyhi's Avatar
    Posts : 3,566
    Windows 3.1 to Windows 10
    Thread Starter
       #132

    Update Image Health
    to revision 12.08.2015

    Added better descriptions to command options
    Added better information while processing commands
    Added support for Exporting 3rd Party System Driver
    Added support for Retrieving Windows Product Key ( ShowKeyPlus)

    Refer back to Post 3 for the revised program
      My Computer

  3. Superfly's Avatar
    Posts : 3,337
       #133

    This works for me in PS:

    Get-Content -path $env:windir'\logs\cbs\cbs.log' | Select-String -Pattern '[SR]' | Set-Content $env:USERPROFILE'\Desktop\sfcdetails.txt'
      My Computer


  4. Posts : 69
    Windows 10 LTSB
       #134

    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?!
    Attached Thumbnails Attached Thumbnails Windows 10 Recovery Tools - Bootable Rescue Disk-before-deleting-08-12-2015-16-17-08.png  
    Windows 10 Recovery Tools - Bootable Rescue Disk Attached Files
      My Computer

  5. Kyhi's Avatar
    Posts : 3,566
    Windows 3.1 to Windows 10
    Thread Starter
       #135

    the FIND string reports the following results

    Attachment 52658
      My Computer

  6. Superfly's Avatar
    Posts : 3,337
       #136

    butterfly said:
    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?!

    Nope - how is PS damaged.?
      My Computer


  7. Posts : 69
    Windows 10 LTSB
       #137

    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?
      My Computer


  8. Posts : 69
    Windows 10 LTSB
       #138

    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
      My Computer

  9. Superfly's Avatar
    Posts : 3,337
       #139

    butterfly said:
    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
    Sorry I didn't note your sfc report

    I note a "hash mismatch" - I would guess an upgrade to 10586 or dism/restorehealth will fix that.
      My Computer

  10. Kyhi's Avatar
    Posts : 3,566
    Windows 3.1 to Windows 10
    Thread Starter
       #140

    Do you have the techbench win10 10240 Pro ISO ??

    dism restorehealth / source
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:53.
Find Us




Windows 10 Forums