Have I seen issues with background tasks chewing up way too much processor? Absolutely. Regarding your specific screenshots...
In the first screenshot, there are several things that are problematic.
1. CPU usage running at around 20%. As you noted, that's high for background processes.
2. 4GB of memory... that's kinda low for a modern computer. If you can upgrade this to 8GB, you'll see much better performance. If you can't, then ignore.
3. Disk 0 at 100% write. Something is churning your disk. I suspect I know what it is. More on that later. I think this is the real reason your system is running like crap.
Second screenshot.
Most of the processes listed there are normal. There are a few standouts, though.
1. Skype. Unless you use it, this doesn't need to be running. Disable it or remove it. There's stuff on the internet on how to do that in Win10.
2. Antimalware - if this is actively scanning the system, that may be the issue. Just leaving the system alone and letting this do its thing may cause your problems to go away.
3. Microsoft Windows Search Indexer - This may not be doing anything, or it may be scanning your disk for changed files. You can disable file indexing to improve performance, though it'll make search much slower. If you're fighting for performance, disabling this is a must. It should also be disabled on SSDs as it causes unnecessary wear and tear. SSDs are already pretty fast.
4. McAfee Scanner service - McAfee is terrible. So is Norton. Kill it with fire. This may be actively scanning your hard drive, but even if not, it should be destroyed.
If you notice, there are 3 things in that list that may be actively scanning your drive for various reasons. Any 1 can cause significant performance issues. All 3 going at once would be unbearable and, since they interfere with one another, would take a really long time to go away.
Another option is to upgrade your hard drive to an SSD, if it isn't already one. SSDs are so much faster than spinning disks that these kinds of issues don't really occur with them. Assuming it is a disk access problem you're seeing. From the info provided, though, it certainly looks like it.Statistics: Posted by Satis — Fri Sep 16, 2016 11:16 am
]]>