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.


Have to manually start explorer.exe.

  • Please log in to reply
2 replies to this topic

#1 mzurita8


  • Members
  • 16 posts
  • Local time:07:58 AM

Posted 16 August 2010 - 03:20 PM

Hi i was referred to this part of the forum by someone in the Am I Infected Forum. I'm having a problem where explorer.exe will not load unless I manually run the task in task manager, also when I boot the computer My Documents folder comes up instead of explorer.exe, any help would be appriciated, thanks!

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,556 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:58 AM

Posted 16 August 2010 - 04:37 PM

See http://support.microsoft.com/kb/555294, appears to me that it will solve your situation.

The above involves editing the registry, which is potentially a dangerous task without due diligence.

Because of this, the first consideration that should be made by any user...is to perform a backup of the registry. A good tool for doing such backup is ERUNT Registry Backup Tool - http://www.snapfiles.com/get/erunt.html.

Once you have made a backup of your registry, using ERUNT, then you can proceed to follow the instructions provided by Microsoft.

Let us know how it goes, please :thumbsup:.


#3 mzurita8

  • Topic Starter

  • Members
  • 16 posts
  • Local time:07:58 AM

Posted 17 August 2010 - 05:35 PM

It turns out it's associated with the virus that I thought I had removed, thanks for your help though!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users