Run SFC Command in Windows 10  

You might see if you may be able to install them after uninstalling your current AMD graphics drivers and restarting.

With that many issues, you might consider doing a clean install of Windows 10 to start fresh.

Clean Install Windows 10 Windows 10 Installation Upgrade Tutorials

Sure, you could reset Windows instead to try and avoid a full clean install.

Reset Windows 10 Windows 10 Installation Upgrade Tutorials

It should automatically detect your key and activate. Especially if the key is linked to your Microsoft account.

Find Product Key in Windows 10 Windows 10 Installation Upgrade Tutorials

Link Microsoft Account to Windows 10 Digital License Windows 10 Installation Upgrade Tutorials

[Updated 4 March 2020 - unnecessary use of elevation removed, additional shortcut added]

I always do the same jobs with SFC so I have set them up as shortcuts both for convenience and to avoid typos. It occurred to me that other users might like to do the same so here are the shortcuts I use.
- My shortcuts are all set to run minimised [right-click on each shortcut, Properties, Run - select Minimised]
- Shortcuts 1 & 2 must be set to run as Admin [right-click on each shortcut, Properties, Advanced, set Run as Admin]. The others are just normal shortcuts.

For those shortcuts that create output files
- I send the output to D:\Desktop but you'll need to substitute your own full folder path to a folder in which your user account can write files [test it in a command window by entering Dir >"D:\Desktop\TestFile.txt"]
- My examples [unnecessarily] enclose "the output path in quotation marks" so that they are ready in case your paths contain spaces. If yours do not include spaces then the pair of " around the path can be removed but they do no harm if left in. Do not remove any of the others such as the very final " at the end of the line because that is an essential part of the pair that begins with the FindStr command.
- Each shortcut does its job then closes because its output file is the only thing of interest
- The output file will be blank if there are no results to display
- The extracts are normally short enough to be read easily and to be posted in a forum thread if necessary [unlke the CBS log itself, which is far too long to comprehend or to expect others to review].
- Each line in each output file has its own date-time stamp. If you make multiple extractions [such as Irreparables & Could not reproject ones] then you can use the date-time stamp to relate entries to each other.


Shortcut 1 - Run SFC
- My shortcut is called SFC - ScanNow
- It is set to run as Admin [right-click on shortcut, Properties, Advanced, set Run as Admin].
- The SFC window remains open when SFC finishes so you can have a look at its completion report
- I normally use a variant of this 'baseline' shortcut - see #2 below

Code:

%windir%\system32\cmd.exe /k "%windir%\System32\sfc.exe /ScanNow"

Shortcut 2 - Run SFC with completion indicator
- In this variant, the Taskbar tab label changes when SFC finishes so I do not need to keep opening the SFC window to find out if it has finished or not.
- The Taskbar label starts off as SFC - ScanNow
- When SFC finishes, the Taskbar label changes to Administrator: SFC complete {or as much of that as will fit in the Taskbar tab}. The difference is hard to ignore and that makes it a very good completion indicator

- My shortcut is called SFC - ScanNow
- This variant is the shortcut that I actually use to run SFC.
- It is set to run as Admin [right-click on shortcut, Properties, Advanced, set Run as Admin].
- The SFC window remains open when SFC finishes so you can have a look at its completion report

Code:

 %windir%\system32\cmd.exe /k "%windir%\System32\sfc.exe /ScanNow & Title SFC complete"

Shortcut 3 - Extract all SFC results
- My shortcut is called SFC Results 1 All
- Choose your own path & filename. I include the computer name because I use the same shortcuts on several computers but you can omit that if it is not useful for you.

Code:

%windir%\system32\cmd.exe /c "%windir%\system32\findstr.exe /c:"[SR]" %windir%\Logs\CBS\CBS.log >"D:\Desktop\%ComputerName%-SFCResults.Log""

Shortcut 4 - Extract list of items that SFC repaired successfully
- My shortcut is called SFC Results 2 Repairs
- Choose your own path & filename. I include the computer name because I use the same shortcuts on several computers but you can omit that if it is not useful for you.

Code:

%windir%\system32\cmd.exe /c "%windir%\system32\findstr.exe /c:"[SR] Repair" %windir%\Logs\CBS\CBS.log >"D:\Desktop\%ComputerName%-SFCResults-Repairs.Log""

- The Repairs.Log normally has 2 apparently spurious entries when no repairs were needed -
2020-03-04 16:31:13, Info CSI 00000245 [SR] Repairing 0 components
2020-03-04 16:31:13, Info CSI 00000247 [SR] Repair complete


Shortcut 5 - Extract list of items that SFC could not repair
- My shortcut is called SFC Results 3 Unrepairables
- Choose your own path & filename. I include the computer name because I use the same shortcuts on several computers but you can omit that if it is not useful for you.

Code:

%windir%\system32\cmd.exe /c "%windir%\system32\findstr.exe /c:"[SR] Cannot repair member file" %windir%\Logs\CBS\CBS.log >"D:\Desktop\%ComputerName%-SFCResults-Unrepairables.Log""

Shortcut 6 - Extract list of items that SFC "could not reproject"
I have never found a decent explanation of this type of failure but, because each entry includes "source file in store is also corrupted", I believe that it can serve as an explanation for a corresponding entry in the irrepairables list.

- My shortcut is called SFC Results 4 Non-Reprojectables
- Choose your own path & filename. I include the computer name because I use the same shortcuts on several computers but you can omit that if it is not useful for you.

Code:

%windir%\system32\cmd.exe /c "%windir%\system32\findstr.exe /c:"[SR] Could not reproject" %windir%\Logs\CBS\CBS.log >"D:\Desktop\%ComputerName%-SFCResults-Non-Reprojectables.Log""

I hope this is useful for somebody,
Denis