The patch to prevent this was released on April 11. Get a copy of the latest Stinger as a bandaid till you can get your system up to snuff with all the latest critical patches from MS.

"Critical" updates are pretty accurately named. As all of their updates (with a few telling exceptions) are now able to be rolled back, this "screwing up your machine" isn't the concern it once was. Also, I don't remember any of the critical updates in the past year or so actually breaking any windows functionality. They may break compatability with old/poorly written third party apps but the trade off is severe. The loss of productivity, the cost in salary of idled workers, the time support workers spend on emergency patching. All of these because of a wide spread infestation by the virus of the month that takes advantage of the security hole these patches are meant to close.

We actually had entire buildings of workers without network access. We shut down our VPN concentrators. This affected literally thousands of our employees worldwide. The cost must be significant. If I was in upper management, I'd be talking to our lawyers. But then again, if I was in upper management, we'd have a saner policy regarding patch implementation.

During a meeting discussing the results of testing, it was brought up that NT4 servers with anything less than service pack 6a showed these symptoms. I don't remember any other breakage found. As the instructions for the patch stress having the latest service pack, I'm not sure I'd class this as 'breakage'. I haven't read the bugtrak thread though so there may well be other things I haven't heard of.