Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Search "EXPLORER CRASH"

Status
Not open for further replies.

murphyg

Technical User
Feb 5, 2004
23
GB
When clicking in start>Search Explorer crashes,
This is due to having the ScriptScan feature installed ( Due to ScriptProxy.dll) BTW - HOTFIX 211873 doesn't fix this Either)
System summary as follows
Windows Xp sp1 with VSE8.0i,
W2k Sp4 with VSE8.0i,
4400 Engine and 4413 dat, patches 1,4,5,6,7,8,9.

This can be replicated in the following way,

Install VSE8.0i Raw, no Buffer overflow (All other features installed)
Clicked Search (Explorer crashed)
Removed ScriptScan Feature > Rebooted
Added Buffer overflow feature (Search OK)
Rebooted (Search OK)
Install 4400 engine
Install 4413 Dat
Install patch 4
Install patch 7 Including Patch 1 > reboot required
Install Patch 8
Install patch 9
Click search all is ok
The install ScriptScan Feature > Reboot needed.
Click Start>Search (Explorer Crashed)
Remove the ScriptScan Feature
Click Start>Search
At this point all is ok

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 13/12/2004
Time: 20:06:55
User: N/A
Computer:*REMOVED*
Description:
Faulting application explorer.exe, version 6.0.2800.1106, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Again a simple fix is to Un-Register the scriptProxy.dll

regsvr32 /u c:\program files\network associates\viruscan\scriptproxy.dll

If you use the ScriptScan feature unfortuatly you will have to reboot or try fix below.

untick scriptscan
Unregister scriptproxy.dll
Re register vbscript.dll ( To reset back to defaults)
Stop the framework and mcshield services
manually kill explorer.exe (as this is holding scriptproxy.dll open)
restart the services

A poor way around the problem

BTW - I have two cases open with Mcafee ref: SCRIPTPROXY.DLL
 
The first thing I would advise it to not install all the patches. The only reason you would need the patches is if you're seeing the problem they fix. Remember patches are not hotfixes!! They don't need to be applied to all computers.
 
Do you think I'm Stupid.........

Well Mister firstly, We have installed the patches as they have fixed problems we have had.
Secondly HOTFIX 211873 ( Which hasn't been released yet properly) was created for me, as I found a problem with scriptProxy.dll and the running of VB scripts
Thirdly I do know the difference between Hotfixes and patches.

Its people like you that give 'IT' a bad name, Help & Knowledge sharing is what its about and not stating the obvious.
I won't bother posting here again.

Hope the mediator see's this.

:-(


 
Man... talk about a short fuse. With an attitude like that I'm glad you won't be posting here again. Just like you, I was trying to help. And it's kind of hard to imagine you were seeing 4 different problems that 4 different hotfixes would resolve. I have no clue as to what knowledge you have of McAfee products so there is no need to respond in the manner you have. If you can't accept a little help in trying to resolve your problem then maybe you need to go somewhere else.
 
Somebody missed their prozac dosage today :-( Lighten up MurphyG people here are just trying to help :)
 
I'm with mattmsudawg... don't want help, don't ask for it..


Living la vida ePO
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top