Austinian wrote:

...but that's no excuse for this.

To make things even more "rich" with this update, there's actually a second screw up mentioned in the Microsoft KB article.

LINK