Windows Explorer Problem...Could it be Symantec?

[Paul Engel]

I have XP SP2. It has been installed for weeks and has behaved nicely. This
morning I uninstalled Symantec SystemWorks 2003 and installed SystemWorks
2005. Now, every time I try to open Windows Explorer, it closes down w/ the
message to send a message to Microsoft. I have read a few other accounts
here about the Win Explorer failing under SP2...and it seems to be a
mystery.

If there is anyone else out there w/ this problem that is using a
Symantec/Norton product would pipe in, that would be helpful. Or, if you
have SP2 in and also have SystemWorks 2005 installed and running, but DON'T
have a problem w/ Windows Explorer, it would help to hear from you, too.

 

[Guest]

Choose between Windows Firewall or the SystemWorks Firewall. You can turn
the Windows Firewall off.

 

[R. McCarty]

No first hand experience with 2005 Symantec products, However
I have earned a "Masters Degree(?)" in working with earlier versions.
For some reason Symantec products don't always upgrade to newer
releases very well. It appears to be Registry remnants, that I feel
may be part of their Activation/Protection scheme.
Symantec has stand-alone tools for cleaning up after uninstalling.
(RNav, RNis and SymCln). Depending on how much you're willing
to try I would uninstall 2005 then download the SymCln for 2004
also remove LiveReg and Live Update from Add/Remove programs.
(This assumes you only have SystemWorks and no other Symantec
product on your PC)
Do a search for all "Symantec" folders on your system drive and
delete them. That still leaves some Symantec services mapped to
run. You'll find those under Device Manager - Non Plug and Play
category, such as SymEvnt, etc.
It's not a straightforward process and can get "Messy". This is one
of the primary reasons Symantec products are now on my list of
"Are they worth the Hassles" category. The steps I listed above I
wouldn't try unless you've got a System Image that you can fall back
on, if something doesn't pan out. I was hoping that the 2005 product
line wouldn't exhibit these traits, but your post seems to indicate
that the "Old Issues" are still there.

 

[Paul Engel]

Did that on installation.

Choose between Windows Firewall or the SystemWorks Firewall. You can turn
the Windows Firewall off.

 

[Paul Engel]

Here's some more info on this. I looked at the error that was being
transmitted to MS. Here it is:

AppName: explorer.exe AppVer: 6.0.2900.2180 ModName: adblocker.dll
ModVer: 1.0.0.1 Offset: 00007022

Looks like something in an adblocker.dll is involved. Wonder if that
conflicts w/ Symantec's ad blocking.

I don't have time to keep messing with this. May just uninstall like R.
McCarty suggests. What a PAIN!

 

[Paul Engel]

I have fixed this problem. When I tried to install an IE plug-in, apparently
it needed to use my Win Explorer and encountered the problem. Instead of
just closing out, it brought up my IE Add-ons manager. It had pinpointed the
Adblocker.dll, which belonged to SpyAssassin. I disabled SpyAssassin and my
Win Explorer works again! You get to your Add-on manager on the IE Options,
Programs tab. There is a button.

I am guessing that SystemWorks/AntiVirus was trying to do the same thing as
SpyAssassin with respect to ad blocking and it triggered a conflict w/ Win
Explorer.

I'm also posting this separately in case this thread has rolled off.

Paul