From the official Microsoft website a user reports:
IT
Iron TechMonkey
I'm glad you and other people are exploring this and sharing details from a workstation manager's point of view but this whole scenario is shocking even to a cynical old IT Pro. On a consumer machine with default settings Microsoft should not be telling people that they have to now suddenly manually manage their recovery partitions (having never done that before) just to work around a failed Microsoft update. they should be handling that through a different update which fixes the first problem and then apply
I have read in another thread that this same pattern happened months ago where the problematic update disappeared but now it has come back. So, Microsoft seems to have twice delivered a broken update and failed to manage things that their own routines should manage. I have doubts that the official resolution for this is for regular end-users is to manually fiddle with recovery partitions when that is so far out of the range of their experience. in fact that is something that end-users are typically Specificallytold not to mess with, so I'm going to wait to see if Microsoft can fix their cr@p
Thanks again to you and everyone else who has been exploring this. My sympathies to the non-administrative users who have been convinced to reinstall their entire operating systems only to find that the error continues. If the update is that important than Microsoft can fix it