I fire up the Token Windows Laptop more or less monthly, to download data from our gaggle of Onset Computer Hobo dataloggers. As a result, the laptop gets broadsided with Windows updates from the Mother Ship and, although I look at ’em before installation to see wassup, I don’t really remember any particular update from month to month.
It seems that, in order to solve the really-disable-Autorun-dammit problem, the patch described in KB967715 must update a registry entry that’s nailed down by some other program. As a result, the patch either doesn’t install, installs-but-fails-quietly, or installs-but-fails-loudly.
It eventually percolated to the front of my dim consciousness that I’d seen all of those outcomes over the last few months…
A bit of trawling turned up the usual collection of uninformed blather, plus what seems to be the Definitive Answer direct from the Mother Ship. Go there for the details.
Update 967715 may be reoffered if the HonorAutorunSetting registry setting that is described in this article is not added to the registry hive. This issue may occur if some other program that is installed on the computer blocks the update from writing the registry entry. Such software may block the update during the installation of the update or may remove the registry entry after the computer is restarted.
(“Registry hive”? WTF?)
Basically, you download the patch as an executable file, save it somewhere convenient, reboot in Safe Mode (hold F8 down as Windows starts up, then pick Safe Mode from the menu), clickety-click on the patch program, and give it permission to have its way with your PC.
So far, it’s all good. Maybe I won’t have to remember this for another month…
Memo to Self: if all else fails, MS doesn’t charge for security-related patch assistance phone support.