windows explorer crashes after installing updates

I installed the 9 new security-updates for XP that came out on the 12th
october..
after applyting these updates "windows explorer" has crashed several times
... .... for no
reason...it justs happens and I cant reproduce the crash in any way.
everything was perfect before installing

Error signature
appname : explorer.exe modname : ole32.dll

I think it might have something to do with the KB902400, because it the only
patch that updates ole32.dll
anyone else experienced this?

I have found during this past year that many of the updates coming in on the
Auto Update site give problems. Either downloading or installing or giving
error messages or screwing something up on my computer.

So I have generally taken to seeing which ones are there to be updated and
then finding them either on a MS download site or go to the MS Updates
catalog http://v4.windowsupdate.microsoft.co...en/default.asp and get
them from there.

Another trick that works for me is to download and SAVE them first to a
folder I keep them in and then Install them one by one later. Many folks
claim you should also keep your AV off while installing and /or downloading
them.

Most of these problems started when MS offered Microsoft Updates instead of
only Windows Updates. I, in fact then disabled Microsoft Updates and only use
Windows Updates and go to Office Updates to get them seperately. My Windows
Update site works fine now but as I said often things screw up in the process
of DL and Installing the updates so I use the procedure discribved above.

Good Luck.

--
Dan in Milwaukee, Wisconsin


"Morten S" wrote:

> I installed the 9 new security-updates for XP that came out on the 12th
> october..
> after applyting these updates "windows explorer" has crashed several times
> ... .... for no
> reason...it justs happens and I cant reproduce the crash in any way.
> everything was perfect before installing
>
> Error signature
> appname : explorer.exe modname : ole32.dll
>
> I think it might have something to do with the KB902400, because it the only
> patch that updates ole32.dll
> anyone else experienced this?
>
>
>
>
>
>

I have WinXP SP2. When I installed all the updates the other day(13th I
think) my IE was screwed
up. There were no drop down menu items on top toolbar showing but they would
drop down if I scrolled over them, my start menu lost all its small icons,
any folders I went to showed icons only and I could not change it back to
list like I normally have them, and a few other things were "changed" I don't
remember. So after reading the posts here, I UNINSTALLED all of the days
updates ( I had 8 of them) and then reinstalled one by one (this time with my
AV off) except I did not reinstall KB896688( only downloaded and saved it).

What I finally did was went to KB896688 on MS downloads site and then DL it
from there to SAVE and then decided to try it again installing from my own
computer and now my IE and computer all works fine. I also made sure I had
my AV disabled this time when saving it and when installing it with nothing
else
running or open. I think what happened when trying to DL all 8 from WIN
Update site, something was corrupted in the process of DL or installation.

If you scroll down here on this discussion board you will see many folks are
having all sorts of problems with this months updates from MS especially I
think if you try to take them all from the WIN Update site using Express and
doing all of them at once.

To Remove: Start/Control Panel/Add Remove Program. Tick where it says "Show
Updates" at
the top right of the window. Click on the update and then on remove.

OR you run a SEARCH for Files. If so then>>> Look for the updates from
this month
KB896688, 904706,905414,905749,901017,900725,902400 and 890830(but this one
you can't uninstall). Put it in the "All or part of file name" window and it
will bring up the "uninstaller" for that update. Right click on it and OPEN
it and follow instructions. Preferably maybe do one at a time on the search
and start with 896688 as it has caused most of the problems it seems.

Someone else said they felt 902400 was the problem with their system.




--
Dan in Milwaukee, Wisconsin


"Morten S" wrote:

> I installed the 9 new security-updates for XP that came out on the 12th
> october..
> after applyting these updates "windows explorer" has crashed several times
> ... .... for no
> reason...it justs happens and I cant reproduce the crash in any way.
> everything was perfect before installing
>
> Error signature
> appname : explorer.exe modname : ole32.dll
>
> I think it might have something to do with the KB902400, because it the only
> patch that updates ole32.dll
> anyone else experienced this?
>
>
>
>
>
>

"Morten S" <> wrote in message
news:4353766b$0$41145$...
>I installed the 9 new security-updates for XP that came out on the 12th
> october..
> after applyting these updates "windows explorer" has crashed several times
> .. .... for no
> reason...it justs happens and I cant reproduce the crash in any way.
> everything was perfect before installing
>
> Error signature
> appname : explorer.exe modname : ole32.dll


Please capture the complete Error Signature.
You select it by dragging your mouse over the text
(or possibly by doubleclicking on a word and pressing Ctrl-a)
and then copy it to ClipBoard by pressing Ctrl-c.


>
> I think it might have something to do with the KB902400, because it the only
> patch that updates ole32.dll


Have you tried confirming that all modules in that patch were updated
correctly? E.g. try using MBSA 1.2.1 and its mbsacli command line
tool to verify the versions of the modules. (It's not clear to me that
MBSA 2.0 contains the equivalent function without resorting to scripting.
E.g. if the newer one is only checking the registry and not the module
versions it would not be a complete check and more importantly
for your purposes here it would do nothing to check if a regression
had occurred.)


HTH

Robert Aldwinckle
---

Im 99.9% sure the error has something to do with update KB902400 (its the
only one that updates the ole32.dll file)

I removed this update and I dont get the error anymore...
anyway, here is the error in event view'er

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 17.10.2005
Time: 09:58:01
User: N/A
Computer: MORTENPC
Description:
Faulting application explorer.exe, version 6.0.2900.2180, faulting module
ole32.dll, version 5.1.2600.2726, fault address 0x0005f292.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 78 70 ure exp
0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
0020: 65 20 36 2e 30 2e 32 39 e 6.0.29
0028: 30 30 2e 32 31 38 30 20 00.2180
0030: 69 6e 20 6f 6c 65 33 32 in ole32
0038: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0040: 2e 32 36 30 30 2e 32 37 .2600.27
0048: 32 36 20 61 74 20 6f 66 26 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 35 66 32 39 32 0d 0a 5f292..


"Robert Aldwinckle" <> wrote in message
news:%...
> "Morten S" <> wrote in message
> news:4353766b$0$41145$...
>>I installed the 9 new security-updates for XP that came out on the 12th
>> october..
>> after applyting these updates "windows explorer" has crashed several
>> times
>> .. .... for no
>> reason...it justs happens and I cant reproduce the crash in any way.
>> everything was perfect before installing
>>
>> Error signature
>> appname : explorer.exe modname : ole32.dll
>
>
> Please capture the complete Error Signature.
> You select it by dragging your mouse over the text
> (or possibly by doubleclicking on a word and pressing Ctrl-a)
> and then copy it to ClipBoard by pressing Ctrl-c.
>
>
>>
>> I think it might have something to do with the KB902400, because it the
>> only
>> patch that updates ole32.dll
>
>
> Have you tried confirming that all modules in that patch were updated
> correctly? E.g. try using MBSA 1.2.1 and its mbsacli command line
> tool to verify the versions of the modules. (It's not clear to me that
> MBSA 2.0 contains the equivalent function without resorting to scripting.
> E.g. if the newer one is only checking the registry and not the module
> versions it would not be a complete check and more importantly
> for your purposes here it would do nothing to check if a regression
> had occurred.)
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>

"Morten S" <> wrote in message
news:4355d2f5$0$41147$...
> Im 99.9% sure the error has something to do with update KB902400 (its the only one that updates the ole32.dll file)


That's assuming that the cause of the crash is the location of the crash,
which is not necessarily true.


Was drwtsn32 capturing any diagnostics for these crashes?
If so you could get more clues from the Stack Back Trace
which corresponds to your Event log entry.

Stack Back Trace is the label of the section in the English dump.
If your OS is written for another language you might have to translate that
label. To be sure you could use the Help for drwtsn32.exe, since it has
an article titled Using the Dr Watson log file which would show you the layout
of a dump.


FYI

Robert
---