SP2 vs Explorer.exe - Close, but no Cigar

[Selden McCabe]

I've posted about this before, but I think I'm MUCH closer to the solution.
Ever since installing SP2, the following happen:
1. Double-click My Computer - the flashlight waves for about 5 minutes
before anything appears.
2. Open the browser, type www.microsoft.com - searches forever, but type
http://www.microsoft.com and it goes right there.
3. If I enable the ShellHardwareDetection service, boot up takes about 15
minutes. After boot up, clicking on just about anything takes 5-10 minutes
before anything happens. So for now I've disabled that service.

I've been through all previous posts with related issues, and googled this
issue, and followed all the various advices without much success. But now I
think I'm Really Close...

What I've discovered is I'm getting a DCOM timeout in the System event log
each time I double-click My Computer. The event log shows
"{A1F4E726-8CF1...did not register..." I think this is related to the WIA
service, or some service or software that lets windows know what icons to
use for different file types.

There's an interesting discussion thread closely related to this topic at:
http://forums1.itrc.hp.com/service/...493758+1103817371960+28353475&threadId=736485

If I roll back SP2, the problem goes away. So I think this may be some
hardware or software that is not compatible with SP2.

I've used ShellExView to disable ALL non-Microsoft context handlers and
browser helpers. I've un-installed all non-essential programs using the
Add/Remove app. (There are a few that won't uninstall, and some claim that
the Windows Installer is not configured properly... could this be a clue?)

There are no questional devices showing on my device manager.

So my question is: how can I troubleshoot this problem? How can I figure
out what hardware or software is causing the problem?

Any sort of advice would be greatly appreciated!

---Selden McCabe

 

[Rock]

Selden McCabe wrote:

I've used ShellExView to disable ALL non-Microsoft context handlers and
browser helpers. I've un-installed all non-essential programs using the
Add/Remove app. (There are a few that won't uninstall, and some claim that
the Windows Installer is not configured properly... could this be a clue?)

Have you tried disabling the Microsoft context handlers one at a time
with ShellExView? I recollect two threads where the OPs found one of
these MS handlers was the problem. I think it was a different handler
in each case, but don't remember what they were other than one of them
had to do with video files.

 

[Selden McCabe]

Thank you, Rock, for the suggestion!

After playing around with all the context handlers, I found one that, when
disabled,
fixed this behavior. It's one of the handlers having to do with scanners
and cameras.

The only thing left is the ShellHardwareDetection service. If I turn this
back on,
clicking on anything (start menu, etc.) takes a good 15 minutes before
anything happens.

I can live without that service, but it bothers me that something is lurking
under the hood...

If I ever figure it out, I'll post it here in case anyone else is having the
same problem.

Thanks again for your suggestion -- that was the key!

---Selden

 

[Rock]

Thank you, Rock, for the suggestion!

After playing around with all the context handlers, I found one that, when
disabled,
fixed this behavior. It's one of the handlers having to do with scanners
and cameras.

The only thing left is the ShellHardwareDetection service. If I turn this
back on,
clicking on anything (start menu, etc.) takes a good 15 minutes before
anything happens.

I can live without that service, but it bothers me that something is lurking
under the hood...

If I ever figure it out, I'll post it here in case anyone else is having the
same problem.

Thanks again for your suggestion -- that was the key!

---Selden

You're welcome Selden, glad I was able to help, and thanks for posting back.