explorer.exe running at 20% CPU on your desktop
explorer.exe running at 20% CPU on your desktop
So I'm dealing with a strange issue in Windows Explorer. I already identified the root cause, but I need some guidance on resolving it. The problem is that explorer.exe consumes about 20% of my i5-8400 when desktop shortcuts are active. I've searched online for solutions, but most suggest removing unnecessary .exe files or shortcuts with missing icons since they can trigger a loop. However, I didn't notice any missing icons on my system. I experimented with my shortcut placements last night and discovered it only happens when shortcuts are positioned symmetrically on both sides of the screen.
I have a Logitech G502 Hero mouse running at 1000Hz, and I intend to keep it that way because it's essential for gaming. The impact on CPU usage seems minimal, so it probably isn't the mouse itself. The issue isn't specific to this model either—other mice haven't caused the same problem.
I attempted several fixes: reinstalling Windows, resetting BIOS, using Clean Boot and Safe Boot, adjusting shortcuts, rebuilding the icon cache, scanning for malware with Malwarebytes, clearing temp files, uninstalling potentially conflicting drivers, creating new shortcuts, using Process Explorer to pinpoint the culprit (it appears to be Windows Explorer itself), running System File Checker and CHKDSK, using an older BIOS, performing a full main drive format, testing multiple mice, adjusting power settings, and even parking/unparking the CPU.
I'm currently on Windows 10 Pro version 1909 with OS Build 18363.535. I'm unsure how to proceed further. Is this behavior typical, or am I experiencing something unusual?
I completely set up my SSD and re-downloaded Windows onto the USB drive I used previously, thinking it might have resolved the issue. But it didn’t. If this doesn’t work for others, I have no idea what’s going on. It could be a faulty CPU or driver conflict with Windows. Or perhaps my G502 mouse is causing the problem. I’ll look for a solution eventually... EDIT: I discovered my old gaming mouse (G403 wired) and the issue remains. Either a Windows glitch or a CPU problem.