Microsoft Update - Causes Blue Screen??

Hi,

I went over to a client's house to update all of their computers and had had
a pretty good experience with Microsoft Update thus far, so I updated their
machines to Microsoft Update. Two days later, all three machines
continuously rebootted and crashed - blue screen. Can't even get into Safe
Mode. All three had up to date Virus - one was McAfee, one was Norton and
one was Avast!, so I'm pretty sure it wasn't a virus that affected all three
machines since all were updated, patched and protected. (I can't read the
error message, something about Stop:C000269 was all I could get.)

Is there an update to something in Microsoft Update that would have caused
blue screen of death?? (Note - I updated the computers using Windows Update
before I installed Microsoft Update, so it had to be a patch that was is NOT
in Windows Update but IS in Microsoft Update.) All three are 18 month old
Dell Optiplexes and all had the latest BIOS update.

Jeremy...

There is nothing specific in Microsoft Update that would cause such an
issue.

You say that all three systems had the latest BIOS updates... did you
get those BIOS updates from Microsoft Update?
If not, when were the BIOS updates installed?

Did you update any drivers from Microsoft Update?
Particularly the video drivers?

If you installed all updates from WindowsUpdate before opting-in to
Microsoft Update, then there should not have been any content at MU
available for "automatic" (Express) installation, only content available
would have to be accessed through "Custom" updates, which would require you
to select the updates, download, and install them.

Since you can't even get into Safe Mode, the first thing you want to try is
"Last Known Good Configuration". If it was something installed right before
the restart, the "Last Known Good Configuration" should allow you to boot
into the pre-patch system state.

If "Last Known Good Configuration" doesn't work, then you're pretty much
stuck with performing a "repair" installation, but the repair installation
should leave the %windir%\SoftwareDistribution folder intact (though I think
it will overwrite your current AU client, which you'll have to update
again).

If you look at the %windir%\SoftwareDistribution\ReportingEvents.log after
the "repair", you'll be able to see a chronological list of updates
installed on the system. I believe there may also be an entry in that log
acknowledging the Opt-In to Microsoft Update, but if not, the
%windir%\WindowsUpdate.log should have an entry that can give you a time fix
as to exactly when that happened.

Then, use the ReportingEvents.log to itemize the updates installed from
Microsoft Update.


"Jeremy" <> wrote in message
news:E2819310-60D3-4A4D-B936-...
> Hi,
>
> I went over to a client's house to update all of their computers and had
> had
> a pretty good experience with Microsoft Update thus far, so I updated
> their
> machines to Microsoft Update. Two days later, all three machines
> continuously rebootted and crashed - blue screen. Can't even get into
> Safe
> Mode. All three had up to date Virus - one was McAfee, one was Norton and
> one was Avast!, so I'm pretty sure it wasn't a virus that affected all
> three
> machines since all were updated, patched and protected. (I can't read the
> error message, something about Stop:C000269 was all I could get.)
>
> Is there an update to something in Microsoft Update that would have caused
> blue screen of death?? (Note - I updated the computers using Windows
> Update
> before I installed Microsoft Update, so it had to be a patch that was is
> NOT
> in Windows Update but IS in Microsoft Update.) All three are 18 month old
> Dell Optiplexes and all had the latest BIOS update.