Windows 10: How often should I run System File Checker (sfc scannow) ?

Hi guys,
How often should System File Checker (sfc scannow) be run?
Im curious how others use SFC. Do you run SFC directly before performing a System Backup with Macrium or any other backup software? also....
Do you run SFC before creating a System Restore Point?
Is it advisable to run SFC on a regular basis?

Im asking these questions because in the past even when my system hasn't been showing any errors or problems at all Ive run sfc just to check out of curiosity and its told me that Windows Resource Protection has found corrupt files that couldn't be fixed. Ive then had to run DISM to repair system files.
On one occasion, earlier this week, even though my PC isn't having any problems at all I ran sfc verifyonly . I got the message that Windows Resource Protection has found corrupt files that couldn't be fixed. I ran DISM which told me that nothing need fixing so I typed findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt into Command prompt and everything was OK there...no errors reported at all. So I ran sfc /scannow which said Windows Resource Protection has found corrupt files that couldn't be fixed...very confusing! I rebooted and ran sfc /scannow again. This time everything was OK-I got the message windows resource protection didn't find any integrity violations.

:)

 

System File Checker Problem

The computer is not running slow and no BSOD screens. All my computer specs are listed, if anything is missing that I need to add, let me know if needed to resolve this problem.

1st - I ran the sfc /scannow command:





So I rebooted and ran the DISM restore health:





It completed successfully and I rebooted. So I ran the sfc /scannow command again and it fixed the corrupted files:





I then rebooted and ran the sfc /scannow command again and it found no violations:





I shut down the computer for maybe a half hour and all of the sudden the sfc /scannow found corrupt files again when I ran it. The screenshot isn't necessary because we already know what it looks like from my first image.

This is part of my CBS log that I think points to the culprit; but I'll attach the whole log for anyone that can help:

 

System File Checker

To make a long story short, when I contacted Microsoft a few days ago about a problem I’ve been having, one of the possible solutions they gave me was to use the System File Checker tool. When I asked Microsoft’s Virtual Agent about it, she came
back with “…To run it:

• Select Start Windows logo Start button, and in the search box, enter
  Command Prompt. Press and hold (or right-click) Command Prompt (Desktop app) from the search results and select
  Run as administrator.
• Enter DISM.exe /Online /Cleanup-image /Restorehealth (note the spaces before each "/").
• Enter sfc /scannow (note the space between "sfc" and "/").”

After the steps, she provided a link to learn more about the tool (System file check (SFC) Scan and Repair System Files & DISM to fix things SFC cannot).
However, that did not help me much.

Regarding steps 2 and 3, do I have to press “enter” after “…Restorehealth,” or do I type “…Restorehealth sfc /scannow” AND THEN press “enter?”

 

sfc /scannow "Windows Resource Protection could not start the repair service"

Hi,

Windows Resource Protection could not start the repair service is an error which may occur if you are trying to run the System File Checker tool (SFC /SCANNOW) to scan and repair Windows system files. To resolve this error, we suggest that you follow the
steps below:

• Press the Windows + R keys to open run command box.
• In the run command box, type services.msc, and press
  Enter.
• In the list of services, double click the Windows Modules Installer service.
• Set the startup type to Auto, and click OK.
• Restart your computer.
• After the restart, you'll be able to run the sfc /scannow command without any problems.

We would appreciate it if you could get back to us and provide us your feedback.