The Microsoft Security Response Center Blog highlights the advance notification for security bulletins due next week (Patch Tuesday).
Good news: There’s one and only one patch.
Bad news: It’s a Critical Update for Windows.
Good news: “We don’t expect this update to cause a reboot and it can be deployed and detected with MBSA, Microsoft Update, and WSUS.”
Update: Microsoft’s Mike Reavey says there will be no patches next week:
This afternoon we revised the information in the Advance Notification to reflect a change for next week’s release. Microsoft will not be issuing any new security updates on September 13th as part of the September monthly bulletin release cycle. You can check out the revised information here.
So, why did we do this? Let me explain. Late in the testing process, we encountered a quality issue that we decided was significant enough that it required some more testing and development before releasing it. We have made a commitment to only release high quality updates that fix the issues at hand, and therefore we felt it was in the best interest of our customers to not release this update until it undergoes further testing.
I have a great deal of respect for the people who do this thankless job. If they put out a patch that causes problems on a significant number of machines – hell, on any machines – they take heat. If they delay a patch for quality reasons, they take heat. Ultimately, someone had to make a pretty tough decision here.
Ed Bott 