Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


September 30, 2003

Why does my Windows XP machine's CPU usage climb to 100 percent when I right-click a file or folder within Windows Explorer?

RSS
Subscribe to Windows IT Pro | See More Performance Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!

A. XP contains a known bug that causes the CPU usage to spike to 100 percent when you access the context menu under certain configurations. This bug causes file-copy operations to halt, network connections to slow, and streaming media (e.g., audio, video) to become distorted. To work around this bug, you need to disable the GUI's transition effects by performing the following steps:

  1. Start the Control Panel Display applet.
  2. Select the Appearance tab.
  3. Click Effects, then clear the "Use the following transition effect for menus and tooltips" check box.
  4. Click OK to close all dialog boxes.

Another solution that often works is to left-click the file or folder before right-clicking to display the context menu.

End of Article



Reader Comments
Not helpful. My system is locked at 100 percent cpu usage at startup. I tried the above fix and still have the same.

Doug McClure April 17, 2004


I don't understand why this is even an issue.

MAC... May 21, 2004


no help, thanks anyway

Anonymous User March 22, 2005 (Article Rating: )


Its caused by some sort of torjan that injects tis self into the windows "explorer.exe" your best bet is to re-format your computer

Anonymous User April 06, 2005 (Article Rating: )


Turn off transition effect as already mentioned but also use windows classic folders instead of the web folders which can cause 100% cpu usage

Anonymous User June 22, 2005 (Article Rating: )


I had the same problem and I've disabled all menu related effects and it seems to be fine now!

Anonymous User August 15, 2005 (Article Rating: )


yeah. the windows classic folders did it for me. That's nuts that it happens. Hope it's fixed for SP3.

Anonymous User August 26, 2005 (Article Rating: )


You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
Confirmed: Battery Life Issues Not Windows 7's Fault

Microsoft on Monday issued a lengthy statement about the recent Windows 7 battery controversy, echoing my assessment from earlier in the day, but backing it up with hard, cold evidence. ...

Microsoft Warns of Windows Version Expirations

Microsoft warned that this year will see three out-of-date Windows versions slip into retirement. ...

Battery Life Issues Almost Certainly Not Windows 7's Fault

While Microsoft is still investigating a notebook battery life issue that was supposedly caused by Windows 7, some interesting trends have emerged. ...


Windows OSs Whitepapers Protecting Microsoft SharePoint

Related Events Deep Dive into Windows Server 2008 R2 presented by John Savill

Windows, Unix, Linux Interoperability

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2010 Penton Media, Inc. Terms of Use | Privacy Statement