KB835732 - great job microsoft! ( lots of "file or directory is missing and corrupt " errors after i

  • Thread starter Thread starter Bogdan Lipski
  • Start date Start date
B

Bogdan Lipski

Hi,
This for anybody else who has a chance to encounter this and has no
clue what hit him/her (like I did not for almost 1 full day.....)

On my test machine with:
P4 - 2.4Ghz
Asus Motherboard - P4S533MX (sis651/962)
(newest drivers for everything)
1GB RAM
and windows 2000 Server SP4 with all other patches except this one
system works stable. after installing this very patch through
liveupdate hell breaks out:
- lots of "file or directory is missing and corrupt" shortly before
windows login prompt appears
- BSOD's
- service's failing to start
- C: drive missing and corrupt

and so on.....

you can only imagine how "stupid-work-intensive" was the process of
narrowing it down to one single, f****** patch arriving though
windowsupdate.
that was one of the nasties suprises I ever got from microsoft through
windowsupdate, will definetely not take this update system for granted
anymore... (not even for test machines)


Have a nice day guys.
Bogdan

ps. one more thing - if you wonder why your promise ultra100/133
controller works like snail - don't wonder anymore...
 
Il 16/09/2004, alle ore 17:17, Bogdan Lipski ha scritto:
system works stable. after installing this very patch through
liveupdate hell breaks out:
Click to expand...

Where were you 4 months ago? ;)
http://snipurl.com/95a0

The "funny" thing is that, as of today, I still have not found any
solution for this problem. So I still have some workstations which need to
be updated manually, I had to turn off automatic updates because of this.

Amongst the machines I manage, three have absolutely identical hardware,
and started with the same software (evolving some minor Windows-unrelated
differences afterwards).
One of them had no problem with the patch, while the two others did.
For other reasons, I recently had to wipe the two latter machines, and
took the opportunity to clone the HD from the first one on them.
Now they all three work fine with that patch. So it really must be a
software affair, but I really can't understand the cause.

Any clue is welcome.
 
Back
Top