Explorer.exe Process Uses Many CPU Cycles When Windows Is Idle

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q317751
This article has been archived. It is offered "as is" and will no longer be updated.
Under certain circumstances, the Explorer.exe process uses an excessive number of CPU cycles when Windows is idle, and as a result, Windows performance is degraded.

NOTE: To view the CPU cycles that the Explorer.exe process uses, right-click a blank area on the taskbar, click Task Manager on the shortcut menu that appears, and then click the Processes tab.
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English-language version of this fix should have the following file attributes or later:
   Date         Time   Version      Size     File name   ---------------------------------------------------   15-Feb-2002  13:39  5.1.2600.28  293,888  Msctf.dll   15-Feb-2002  13:39  5.1.2600.28  209,920  Msutb.dll				

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.
CPU load

Article ID: 317751 - Last Review: 12/07/2015 08:57:20 - Revision: 3.5

Microsoft Windows XP Home Edition, Microsoft Windows XP Professional

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbenv kbbug kbfix kbqfe kbwinxpsp1fix KB317751
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)