Windows Update error FOUND!!!

For months I've been avoiding applying the 37 security updates because every
time I did, Windows Installer was corrupted, the WMI database was corrupted
and my Norton Internet Security settings all got corrupted.

All this required reinstalling WinXP Pro to repair Windows Installer so I
could remove NIS, then apply the WinXP patches...but nothing seemed to work
properly...

Finally, I managed to get the will to start all over again, and work through
installing each of the Windows Updates until I found the one causing the
problem....and I found it about 30mins ago!

I must admit that I haven't told MicroSoft and they haven't said anything
about whether this particular KB article will cause a problem, but after
creating a very satisfactory Restore Point (in fact I've created about 20 of
them to get to this point!!), testing my system for correct operation, then
installing the KB article in question, and finding my system failing as I had
experienced, there is definitely, absolutely, something terribly wrong with
that particular KB...

Unless you have reason to do otherwise, I strongly recommend NOT installing
KB902400.

You wouldn't believe the incredible relief I currently feel knowing that I
once again have a stable system, with NIS working correctly, all my apps
working, no more Events being reported as failures, warnings, etc....all due
to this damned update.

Question: What is the process for telling Microsoft about my discovery?

I sure hope this helps everyone. And I sure wish I knew about this
forum...although it wouldn't have helped!

Regards, Emonator
--
All IT roads lead to Gates!

Emonator wrote:
> I must admit that I haven't told MicroSoft and they haven't said
> anything about whether this particular KB article will cause a
> problem, but after creating a very satisfactory Restore Point (in
> fact I've created about 20 of them to get to this point!!), testing
> my system for correct operation, then installing the KB article in
> question, and finding my system failing as I had experienced, there
> is definitely, absolutely, something terribly wrong with that
> particular KB...
>
> Unless you have reason to do otherwise, I strongly recommend NOT
> installing KB902400.
>
> You wouldn't believe the incredible relief I currently feel knowing
> that I once again have a stable system, with NIS working correctly,
> all my apps working, no more Events being reported as failures,
> warnings, etc....all due to this damned update.
>
> Question: What is the process for telling Microsoft about my
> discovery?
>
> I sure hope this helps everyone. And I sure wish I knew about this
> forum...although it wouldn't have helped!

Have installed and integrated this patch onto hundreds (perhaps thousands)
of machines personally - no problem thus far.

Your mileage may vary.

Everyone has something unique about their system - whether hardware or
software - attached peripheral or strange little application - so - you may
have discovered a fluke on *your* slice of the world.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Yeah. ya probably right mate...

System: WinXP Pro 2002 5.1.2600.2180 sp2 Build 2600; AMD Athlon 64 3000+
2.01GHz, 512MB Kingston Ram; 180GB SATA

I seemed to be experiencing many of the problems that others have reported
regarding a range of applications that all of a sudden wouldn't perform, or
had access restrictions, etc. I eventually worked out that the WMI database
was corrupted and was ONLY repaired by a WinXP reinstall...Windows updates
also didn't work properly since Windows Installer was also broken.

I've literally spent 30 - 40 hours progressively working out what was wrong.
I rang Symantec and exchanged numerous emails offering suggestions...nothing.
It wasn't until I suspected that a particular update might be causing the
probs that I decided to 'binary-split' the installation of the updates to
work out which ones were failing...

Anyway. I'm just happy that my system is now very stable and happy...and I'm
totally over the moon. If that can help some one else...I'll be extra
happy... :-)

Regards, Emonator
--
All IT roads lead to Gates!


"Shenan Stanley" wrote:

> Emonator wrote:
> > I must admit that I haven't told MicroSoft and they haven't said
> > anything about whether this particular KB article will cause a
> > problem, but after creating a very satisfactory Restore Point (in
> > fact I've created about 20 of them to get to this point!!), testing
> > my system for correct operation, then installing the KB article in
> > question, and finding my system failing as I had experienced, there
> > is definitely, absolutely, something terribly wrong with that
> > particular KB...
> >
> > Unless you have reason to do otherwise, I strongly recommend NOT
> > installing KB902400.
> >
> > You wouldn't believe the incredible relief I currently feel knowing
> > that I once again have a stable system, with NIS working correctly,
> > all my apps working, no more Events being reported as failures,
> > warnings, etc....all due to this damned update.
> >
> > Question: What is the process for telling Microsoft about my
> > discovery?
> >
> > I sure hope this helps everyone. And I sure wish I knew about this
> > forum...although it wouldn't have helped!
>
> Have installed and integrated this patch onto hundreds (perhaps thousands)
> of machines personally - no problem thus far.
>
> Your mileage may vary.
>
> Everyone has something unique about their system - whether hardware or
> software - attached peripheral or strange little application - so - you may
> have discovered a fluke on *your* slice of the world.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

You should read this MS article about possible after-effects of KB902400
http://support.microsoft.com/kb/909444/

As the man said, YMMV. My XP has had KB902400 update (a security fix from last October 2005) & not had issues.

--
Maurice N
MVP Windows - Shell / User
-----

Emonator wrote:
> For months I've been avoiding applying the 37 security updates
> because every time I did, Windows Installer was corrupted, the WMI
> database was corrupted and my Norton Internet Security settings all
> got corrupted.
>
> All this required reinstalling WinXP Pro to repair Windows Installer
> so I could remove NIS, then apply the WinXP patches...but nothing
> seemed to work properly...
>
> Finally, I managed to get the will to start all over again, and work
> through installing each of the Windows Updates until I found the one
> causing the problem....and I found it about 30mins ago!
>
> I must admit that I haven't told MicroSoft and they haven't said
> anything about whether this particular KB article will cause a
> problem, but after creating a very satisfactory Restore Point (in
> fact I've created about 20 of them to get to this point!!), testing
> my system for correct operation, then installing the KB article in
> question, and finding my system failing as I had experienced, there
> is definitely, absolutely, something terribly wrong with that
> particular KB...
>
> Unless you have reason to do otherwise, I strongly recommend NOT
> installing KB902400.
>
> You wouldn't believe the incredible relief I currently feel knowing
> that I once again have a stable system, with NIS working correctly,
> all my apps working, no more Events being reported as failures,
> warnings, etc....all due to this damned update.
>
> Question: What is the process for telling Microsoft about my
> discovery?
>
> I sure hope this helps everyone. And I sure wish I knew about this
> forum...although it wouldn't have helped!
>
> Regards, Emonator