List of current issues
High CPU usage because of BACKGROUND TASKS OF MICROSOFT WINDOWS SYSTEM PROTECTION
Steps taken, but unsuccessful?
Nothing because I did not know what I can do...

JB007

Level 17
Verified
Hello,
Since 3 weeks I hear my PC fan running very fast, only Saturday morning. It is my work PC, so I'm doing the same tasks every day.
When I go to the task manager I can see that the problem is "BACKGROUND TASKS OF MICROSOFT WINDOWS SYSTEM PROTECTION".
These "Background tasks" are using the processor between 35 and 40% :unsure:
This issue persists about 4 hours and then my PC works again normally.
Can you help me to solve this issue ?
Thanks

CPU.PNG
CPU1.PNG
CPU3.PNG
 

JB007

Level 17
Verified
Last edited:

venustus

Level 45
Verified
Trusted
Content Creator

JB007

Level 17
Verified
Can you recall which process was causing this problem?
Hello @yitworths
"Background tasks of Microsoft Windows system protection"

Okay!Would like to see what is happening when it is running.
It will automatically trigger when it needs to check authenticity of Windows or Office.Do you have Office installed?

When that process is running again open up Process hacker and post a screenshot:)
Yes @venustus , I have Office 2007 installed on this PC.
Kaspersky detects "Process hacker" as malware:eek:
PROCESS HACKER.PNG


and also DrWeb, Sophos, Panda and ZoneAlarm...
PROCESS HACKER1.PNG
 

yitworths

Level 10
Verified
May be kaspersky was scanning every step of srtask during that time. I can't ensure it as you said this continued to happen for 4 long hours. If high cpu usage problem limited to srtask, then you may try to disable it's scheduled task (obviously if you don't need it).
More info would be helpful. Are you facing this problem every now & then or was that the first time?
 

harlan4096

Level 62
Verified
Staff member
Malware Hunter
Agree, but sometimes there are some scheduled tasks not shown in AutoRuns, I've found this cases many times testing malware at MWHub, and I had to use Comodo AutoRuns, and even that, sometimes also neither in Comodo AutoRuns are shown, so finally I had to use and find the malicious task with Nirsoft TaskSchedulerView tool...