Author Topic: Odd new sfc issue  (Read 931 times)

0 Members and 1 Guest are viewing this topic.

Offline best1syn2oil

  • Newbie
  • *
  • Join Date: Dec 2013
  • Posts: 37
  • Karma: 0
    • View Profile
Odd new sfc issue
« on: December 14, 2018, 05:07:26 PM »
Windows 10 Pro 64 bit
Samsung 500GB SSD

Whenever I run sfc in the Windows environment, it always says it found corrupt files and was not able to repair some of them.  DISM appears to repair the component store, but running sfc again always results in the same message.  However, if I run sfc in safe mode it finds no integrity violations.  Would sfc be more likely to produce an accurate result in safe mode?  On occasion, sfc has found issues in safe mode, but it fixed them all with one exception where I had to clean up the component store first.  Today sfc found issues, so I immediately rebooted into safe mode and ran it again...found no violations.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10014
  • Location: UK
  • Karma: 122
    • View Profile
Re: Odd new sfc issue
« Reply #1 on: December 15, 2018, 02:08:05 AM »
Run it again in normal mode and if it finds corruption then copy & past this cmd to the prompt -

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfcdetails.txt

This will put an icon onto the desktop which when double clicked on will open the CBS log in Notepad which you can then copy & paste into the reply box.

This is a reduced CBS log where it tells you what it could and couldn't repair.
Tom.