Windows 10: System file checker not working

My system got very slow from past week. I searched and tried lots of tips from internet. Someone the sfc command is not working. Can anyone help me out ? And how can I improve my PC performance ?

:)

 

System File Checker

Hello,

Try these steps:

http://www.yourwindowsguide.com/2016/04/run-sys...

 

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?”

 

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: