Microsoft’s Patch Process
Friday, September 28th, 2007An interesting report appeared today, courtesy of the Windows Secrets newsletter, indicating that anyone who’s used the Windows Repair feature on the XP or Vista installation media may have been excluded from up to 80 recent official Microsoft patches, some of which were fairly serious. There’s no conspiracy or other nefarious plot involved; the problem seems to be that use of the repair option rolls certain files back to version that are too old to work properly with recent Windows Update versions. As a result, the 80 most recent updates simply won’t be applied. This could expose user systems to known exploits or other problems.
According to the article, “after using the repair option from an XP CD-ROM, Windows Update now downloads and installs the new 7.0.600.381 executable files. Some WU executables aren’t registered with the operating system, preventing Windows Update from working as intended. This, in turn, prevents Microsoft’s 80 latest patches from installing.” Happily, the files can be re-registered by hand in order to work around the problem. Details of the manual file correction process are supplied in the article.
Windows Secrets also broke the story of Microsoft’s “stealth updates” process, which raises the larger question of whether any vendor should be permitted to install updates on user systems without first informing the owner. This update process installs patches on systems even when users have opted out of the automatic patch delivery process available under XP and Vista. It’s at least worrisome, and at most legally actionable, that “updates to the WU executables seem to be installed regardless of the settings — without notifying users.” Not only does it raise issues of privacy and security, but many corporations explicitly forbid the installation of patches that have not been tested and approved for internal use. Such companies typically bundle groups of patches together, test them against their own internal product suites, and only release them to the general user population once it’s been ascertained they won’t cause crashes or other problems.
Then there’s the problem of accountability. What happens if you leave your PC, which is connected to an always-on DSL or cable connection, only to return later to find the system unusable? If you run diagnostics and find that Microsoft’s auto-update utility installed patches even after you’ve opted out of the service, can you sue Microsoft for damages? I suspect the answer is “yes.”
It’s important to note that none of these patches are known to have caused problems with user systems – yet. However, if Microsoft is able to install updates without the user’s knowledge or consent, there’s no way to know what use will be made of this ability in the future. Also, will a hacker manage to slip malicious code into an official patch, thereby causing it to be distributed to the whole installed Windows base? Will someone figure out how to commandeer this process and use it to push malware to user systems? These revelations have opened the proverbial can of worms, and only time will tell what the consequences are.