kirk jim wrote:[color=blue]
> I have seen more posts like this in this newsgroup today...
>
> therefore this has happened to more people
>
>
>
> "JH" <jdh@eastlink.ca> wrote in message
> news:OxcmxIldHHA.4688@TK2MSFTNGP04.phx.gbl...[color=green]
>> I installed this security update that was coded as an important update on
>> Windows Update. After rebooting, the system went to a blue screen (error
>> in win32k.sys). It would not even boot in safe mode, so I had to boot from
>> the Vista CD, run a system restore and everything worked fine. Then, a few
>> hours later, Windows Update automatically installed the update again and on
>> reboot, again the same blue screen error. I had to run system restore a
>> second time to fix it.
>>
>> Has anyone else had this problem? Is there any solution other than
>> turning off automatic update right now? How can MS screw up so bad on an
>> update that it forces to people's systems by default?[/color]
>
>[/color]

Which is why it's a good idea to wait on updates for a few days after
they're out to see what happens to users who went for them as soon as
they're posted or foolishly have AU set to download and install without
user input enabled.

Alias