I don't remember Windows explorer crashes in Vista in the last few builds,
but I might have had some, John but in one build I think about 3 builds ago
from RC2 I had what I'd seen a fair amount on the web in Vista forums--IE
got corrupted or the shell did.
In XP, I've found along these lines that when you get the IE close boxes,
and the Windows explorer close boxes (sorry for any inconvenience including
the mornic one that the errors are written in hex requiring special tools
and training that PTA soccer mom and Nascar dad and the bell shaped curve of
MSFT customers don't have). An appropriate U tube would be to put Dean
Hachamovitch General Manger of IE and his team in the middle of Seattle in
barrels interviewing Seattle passersby say about 3000 of them from 8-5PM as
to how many were born with congenital knowledge of hex or the ability to
decode it.
The tin ear and basic disconnect from reality is showcased bess in the
stupid way error messages are conveyed, and metastatic and ectopic to the
four corners of Windows. The more sophisticated Event Viewer in Vista has
some nice features, and unfortunately they do absolutely nothing to take
care of the inscrutable hex messages for Windows crashes, IE, WE and Office
crashes.
I've found when faced with these, one deterrent is to crank up Task
Man>Applications tab>new> and start iexplore.exe and exploreR.exe and that
can deter about 75% of the pending Windows Explorer, IE and often
mshtml.dll or some of the other .dll labled crashes.
I often follow these by running SFC this way, depicted in MVP Mark Liron's
article for the reasons that MSFT and OEM named partners and MSFT OEM VP
Scott Valerio who is an accountant and has no experience or training
whatsoever as a software engineer (he's purely about da money dat MSFT can
vaccum and scarf up with the deal that leaves customers in a lurch without a
CD) and if someone does have an RTM or gold CD that hasn't been slipstreamed
with the latest service pack which would be SP2, then they want to scan
files from the HD at DLLCache and not a CD that is older than the service
pack--one that RTM'd in 2001.
http://www.updatexp.com/scannow-sfc.html
and by reregistering the .dlls named in this MSKB even though the title is
for another situation--that of IE not connecting to the web.
http://support.microsoft.com/kb/902932
1. Click Start, click Run, type regsvr32 urlmon.dll in the Open box,
and then click OK.
2. Click OK when you receive the following message:
DllRegisterServer in urlmon.dll succeeded
3. Repeat steps 1 and step 2 for the rest of the DLL files by
replacing the regsvr32 urlmon.dll command in the Open box with the following
commands: • regsvr32 actxprxy.dll
• regsvr32 shdocvw.dll
• regsvr32 mshtml.dll
• regsvr32 browseui.dll
• regsvr32 jscript.dll
• regsvr32 vbscript.dll
• regsvr32 oleaut32.dll
CH