File Explorer Excessive CPU

Hi,

To address your concern, we suggest that you disable sdclt.exe in Task Scheduler. To do that, follow these steps:

1. Type task scheduler in the search box.
2. Click on Task Scheduler.
3. Expand it to: Task Scheduler > Microsoft > Windows > WindowsBackup.
4. Disable ConfigNotification.

Let us know how it goes.

I opened the Task Scheduler.  When I expand as you stated and then clicked on WindowsBackup - it was empty - no tasks.  Nothing named ConfigNotification.

I did notice the following:  When I start File Explorer, the three threads appear and CPU jumps to 75%.  After about 45 minutes, the three threads disappear and CPU usage drops to near 0.   If I exit file explorer and then execute it again, the three threads are back and remain using 75% CPU for another 45 minutes until they disappear and CPU drops to normal.

Perform a clean boot to find out if the "threads" are associated to non Microsoft services. Please refer to this link on how to perform a clean boot.

You may also run a full system scan using your antivirus software.

Post back if you need further assistance.

Did a Clean Boot (Disabled all non-MS services using MSCONFIG and all programs in STARTUP).  Same three threads exist and take over 75% CPU.

Running MCAFEE full scan.

Hi,

Update us once you have run a full scan using your antivirus software. You can also try to use the Windows Defender Offline by checking the steps on this link.

Keep us posted for the results.

Regards.

Full scan showed no problems (McAfee Total Protection).  Malwarebytes shows no problems.

I don't know why EXPLORER.EXE exhibits this behavior, nor why it seems to come and go.  It happened on an older computer where I formatted the disk and did a clean install of a purchased Windows 10 on a flash drive.  That was solved by doing a Repair Install of a downloaded ISO from Microsoft.  Eventually, after several updates it returned and I did another repair install.  On my current laptop (new purchase with Windows 10), I again had the issue after setting up the new computer (before I loaded any software on it).  Again, resolved by doing a Repair Install.  And now it has returned again.

The biggest difference this time is that I execute Windows File Explorer, immediately jump to 75% CPU and then I wait.  Somewhere between 45 to 60 minutes, the threads causing the issue disappear and EXPLORER.EXE returns to near zero CPU.  So my resolution is simply to start Windows Explorer, wait 1 hour and never close it.

Hello,

May we know the build of Windows that you are using?

You may know the build of Windows by pressing the Windows key + R, then typing winver, and press Enter.

We look forward for your response.

Regards.

Windows 10 Home, 64 bit OS, 16gb Ram

Version 1607

OS Build 14393.693

Two of my three laptops exhibit this problem with File Explorer: Lenovo (formatted and using a purchased Windows 10 installed from Flash Drive) and Acer (new PC with Windows 10 pre-installed).  The Gateway (updated from Windows 8.1) has never exhibited this problem.  All three on same Version and Build.

Phil

Hi,

Any hardware change or updates made prior to this issue? Let's perform the steps on this link and check if the issue persists.

Thank you.

Been thru:

1. Clean Boot
2. Safe Mode
3. SFC
4. DISM scan health
5. Dism Restore health
6. Process Explorer

In the past, only ISO install repair worked.  But eventually the issue reappears.  I am sure that if I do another Install repair using the ISO, the problem will go away.

Rather than waste my time doing install repairs, I can live with either of the following:

1. Use a third party file explorer (biggest issue with this is that Windows 10 does not allow me to set a default file explorer - so eventually some process will start Windows file explorer and the CPU usage climbs)
2. When I first log in to Windows, start file explorer, wait 45 minutes for the three offending processed to stop running and never close file explorer. (This is the solution I can live with)

Doing an internet search tells me I am not the only one having this problem and since I have it on 2 of 3 laptops but have a workaround, this issue can be closed.