Microsoft Security Re o e Center says yesterday's Office Updates were a "mistake"

The following post a ears now on the Microsoft Security Re o e Center blog, in re o e to the di earing Office security updates.

Information on accidental posting of pre-release security updates for Office for Mac

We've seen some questio from customers about some security updates that posted for a while today for Office for Mac that they didn't see any security bulleti for.

I wanted to let you know that these weren't security updates related to this month's release or the two Word i ues we've written about in Security Advisory 929433 and on our weblog: those investigatio are still underway and we'll release updates for those i ues once we've met the a ropriate quality bar. The updates posted in error were pre-release binaries that had been staged internally as part of our testing for an upcoming release. Due to human error, they were accidentally published to the public we ites before our full testing release proce was complete. As soon as we discovered the error, we moved quickly to addre it and remove the pre-release binaries from our public sites. Once our investigation into this i ue is complete and we have security updates that meet our quality bar for release, we'll release those final security updates for all products affected along with a security bulletin. We're also taking ste to e ure a mistake like this doe 't ha en again. We recommend that anyone who may have i talled these pre-release updates to uni tall them. I'm sorry for any confusion this might have caused.

Thanks.
Mike

*This posting is provided "AS IS" with no warranties, and confers no rights. *
Published Wednesday, December 13, 2006 2:09 AM by MSRCTEAM

Well i 't that lovely? By the way - there is no way to "uni tall" an Office update. If you did i tall the update that briefly a eared yesterday, the only way to revert is to restore your Microsoft Office a lication folder from a recent backup or just drag a fresh copy from your original Office i tall CD, and then a ly the most recent available updates (recent as of the day before yesterday, that is). If you did i tall the update before it was pulled yesterday, and you don't notice any problems, you could just wait it out until the next valid update is released.

Thanks, Steve!