There seems to be something in the MS updates done this morning (5/9/07) that triggered this behavior for those of us not previously affected.

It was caused by one of the following three updates:...