Windows 10: Sppsvc.exe uses about 40% CPU when I log in to the system. Is it normal?

Hi,Yesterday I got a question about the Temp folder, now I got another problem in the past 20 days.When I log in to the system, there is one process named sppsvc.exe that uses about 30-40% CPU and after 2 minutes closes out.It runs as a service, but I have a feeling that the high CPU load is either a malware, or broken or missing system files.I've tried to do a Full Scan by my Kaspersky Antimalware Program I use Kaspersky because it was suggested by my computer manufacturer. It found 0 malware, 1 file has been skipped.It doesn't exactly use 40% CPU, sometimes it falls down to 15 or 20% and

:)

 

After update, SPPSVC used a full CPU core

Hi,

Regarding your concern, we suggest that you check this link
and follow the resolutions provided by Alex Lv.

Let us know how it goes

 

"System compressed memory" Use 40% CPU all the time

Count me in as another in which this system and compressed memory issue taking up 40% memory regardless of the fixes listed in this and similar threads.

The bonus kicker for me is that DWM.exe (windows desktop manager) is hogging up 30-50% of the CPU on a continual basis and it leaves me with a painful experience.

On an HP ENVY with decent enough specs.

Get this fixed Microsoft or i'm turning coat and going apple

 

Notepad consuming cpu 40%

Step One [/i] Run SFC (System File Checker)


Open an admin Command Prompt and type:


Code:

This should fix any system file corruption if there is any.





Step Two [/i] Run DISM (Deployment Image Servicing and Management Tool)


Using the same Command Prompt type:


Code:

This should fix any component store corruption.




Note If the sfc command fails, run this command then try Step One again. Sometimes this will fix sfc errors.





Step Three [/i] Run CHKDSK (Disk Checker)


Using the same Command Prompt, type


Code:

This will let you know if there are any errors in the file system itself. If it comes up with errors, type


Code:

This command will perform a more thorough check and attempt to fix any errors and recover any data from bad sectors (if any exist.)




Note Running this command will require you to restart. After restarting this will run. After it does, you will need to use the event viewer to view the log.


How To Read CHKDSK Log Using Event Viewer
i've done the three tests . nothing has changed