Because Click-to-Run (a/k/a virtualized) is not the normal distribution method for Office software, I'm not at all confident that "Microsoft would use the usual tool" to distribute a future update to it.
My gut tells me that we're seeing side-effects of New And Different distribution method(s) for click-to-run (virtualized) software.
For future use, I've bookmarked the link from Doug Robbins dated today. (As a community, we can hope that, although the link's hosted by HP, there's nothing HP-specific in the solution; my own laptop happens to be an HP product.)
Please also notice the comment (via the HP link) about being careful to NOT uninstall the Microsoft Office Program Manager* ... because uninstalling that component "requires you to perform a recovery to reinstall Microsoft Office Starter 2010."
- Complicated by the fact that the do-not-uninstall component is NOT labeled as "Microsoft Office Program Manager," but is "noted by the entry of Microsoft Office 2010."
- That "recovery" could be the "factory restoration" that Victoria mentioned (is anyone able to confirm or deny my "educated guess" on that?) ... a "restoration" which has been associated with deleting Office-based documents on
customer systems.
So, how customer-unfriendly can Microsoft get this month?
- The suspicious-looking "click-to-run update" popup (which looks more like malware) ...
- Missing KB articles on Patch Tuesday, leaving customers unable to make informed decisions about multiple updates across multiple products
- The poorly-documented, non-standard, and clearly risky behavior of the Click-To-Run update deployment
- Losing at least some customer documents (many, on some systems) ... which, of course, re-emphasizes the value of always having recent backups.
The good news? We still have three weeks 'til the next Patch Tuesday... which opens new opportunities for unexpected behavior.
In light of this month's activity, I will make sure to run a full backup shortly before January 13!