Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

WinXP Can't click Taskbar


  • Please log in to reply
2 replies to this topic

#1 Robbie90

Robbie90

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:02 AM

Posted 11 July 2011 - 01:15 PM

Hi All,

I am running Windows XP on Intel Core 2 Quad, Asus P5KC Motherboard and 4 GB DDR3 RAM, Kaspersky Antivirus and it's behind a Router.

Off late, shortly after booting, the taskbar becomes unclickable. I can still open apps via the desktop icons but when i take the curson to the taskbar it changes from arrow type pointer to a vertical line.

My suspicion is that some hard shutdowns due to malfunctioned UPS battery might have caused some Windows corruption.

Please advise what it could be and how to correct.

Thanks.

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:03:02 PM

Posted 11 July 2011 - 01:38 PM

Press ctrl+alt+del and start ending processes like Kaspersky till the issue goes away.

#3 Allan

Allan

  • BC Advisor
  • 8,575 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:02 AM

Posted 11 July 2011 - 01:47 PM

Open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming procedure, but it is the best way to determine if some process loading with the system is the cause of your problem.
After you've isolated the cause, do not use msconfig to permanently disable the process. Instead, if it is a service go to START - RUN and type: services.msc (then press enter) and disable the service OR, if it a program, you can download & run a simple app such as Mike Lin's Startup Control Panel (http://www.mlin.net/StartupCPL.shtml) to enable, disable, or otherwise manage startup programs.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users