Windows 10: task manager - local system service host with high CPU usage
task manager - local system service host with high CPU usage
Can anyone explain what is happening here?
From the moment I switch ON my desktop until switching OFF (working for 12 hours) the local system service host is always between 30% to 40% regarding CPU usage.
Why? How to stop it?
This does not happen in my Microsoft Surface Pro machine. Both machines, desktop and Surface have the same software installed so it's hard to believe this CPU usage is software based.
I believe you were talking about this?
So let me see if I'm reading this correctly, it's Windows update that is creating the problem here, correct?
Yes. I would leave it to finish and then reboot.
EDIT - you can reset it if it never seems to finish but there were lots of updates yesterday, I'd leave it for a few hours or overnight...
Windows Update - Reset in Windows 10 - Windows 10 Forums
Hello! I'm new here so I will make this short. I installed Windows 10 (10130 build) and I love it. The only problem that I'm having with it is this Photo Background app that eats my cpu(30-40%)! When I start up windows I need to kill it in task...
Hey guys! First post for me. :) Been taking up the problem of system and service host: local service eating all the ram. So I've been clicking some stuffs at the settings when suddenly I solved my problem unexpectedly! So here's how you do it. :)
Read more: Microsoft System Center Configuration Manager next up to get the service treatment | ZDNet
See also: System Center Configuration Manager: Support for Windows 10 and Microsoft Intune - System Center Configuration Manager Team Blog -...
Hello guys I've had this issue that has really been getting on my nerves for the past couple of weeks now ever since upgrading to windows 10 from windows 7. For some odd reason at random times this Service Host: Local Service...
in Task Manager, the "System" sometimes starts eating 14~20% CPU and that persists until a reboot.
"System interrupts" (which is a pseudo process?) seems to do the same.
It doesn't happen from boot, and I don't know what triggers...