Woody Leonhard of Infoworld summarizes the current state of Microsoft KB 2919355, the ambiguously-titled 'Windows 8.1 Update' (not to be confused with the update _to_ Windows 8.1).
In short: Microsoft has frozen two discussion threads on KB2919355 issues (after 103 and 116 pages of comments), and updated the Knowledge Base article with workarounds for seven major errors... some of which don't work.
In last week's Patch Tuesday, Microsoft changed their deadline for this Update until June (formerly they were requiring all Windows 8.1 and Server 2012 systems worldwide to have installed the Update in order to receive new patches).
Meanwhile, if you run a WSUS server, you may notice that the package for KB291355 (last reissued for the third time on 6 May) was apparently silently reissued over the weekend with a new release date of '15 May 2014', but there's no indication of any software updates in the KB article. The article revision number, however, now stands at '21.0'. Yes, twenty-one revisions. With no changelog.
Anyone else with interesting stories about your deployment issues with this Update?
Not smug - accurate. I'm always incredibly irritated by the never ending updates to my Vista VM instance - in particular the auto-restart thing that I invariably forget about, the multiple mouse-clicks that every installer demands, the need to reboot after every friggin' upgrade.
Somehow updates to my primary Mint box are utterly easy, have never demanded a reboot, and thus far haven't managed to break anything. Windows updates seem to be a big ugly hassle, and always offer somelevel of expectation that something critical will stop working.
Someone should do a business case looking at lost productivity due to Windows updates.