This is Christopher Budd. Today, July 5, 2007 is the Thursday before the scheduled July bulletin release day, July 10, 2007. As we do each month, today we’ve posted our Advance Notification for the July 2007 release.
Next Tuesday, we’re currently planning to release six security bulletins:
· Three Microsoft Security Bulletins affecting Microsoft Windows with a Maximum Severity rating of Critical. These updates will require a restart and will be detectable using the Microsoft Baseline Security Analyzer.
· Two Microsoft Security Bulletins affecting Microsoft Office with a Maximum Severity rating of Critical. These updates will not require a restart and will be detectable using the Microsoft Baseline Security Analyzer.
· One Microsoft Security Bulletin affecting Microsoft .NET Framework with a Maximum Severity rating of Critical. This update will require a restart and will be detectable using the Microsoft Baseline Security Analyzer.
Additional details about the bulletins and the affected versions can be found in the Advance Notification posted on the web.
We are also planning to release an update to the Microsoft Windows Malicious Software Removal Too.
Finally, we are planning to release four high-priority non-security updates on Microsoft Update and one on Windows Update.
I want to remind everyone that we provide this information to help with your advance planning for the Tuesday release. This information can change between now and the release on Tuesday. Should things change or we have new information about the release, we will let you know through this weblog.
Remember that I’ll be hosting our monthly Security Bulletin webcast with Mike Reavey on the day after release, Wednesday July 11, 2007 at 11 AM Pacific Time. We’ll be reviewing the bulletins and, most importantly, taking your questions on the air and reading answers that our subject matter experts have put together. If you can’t make the live webcast, remember you can listen to it on-demand after it’s done. You can register for the live or on-demand webcast here:
*This posting is provided “AS IS” with no warranties, and confers no rights.*
Updated to correct the severity rating for .Net Framework from “Important” to “Critical”.