While preparing new template images for Microsoft Windows Server 2008 R2, after the first round of installing Windows updates this happened:
The same thing happened last week on a production server running Remote Desktop Services, and luckily that server recovered from this traumatic experience. I’m not sure which update/updates is/are causing this behaviour in the first place.
It seems a progressive approach is the key. Just let Windows decide which updates to apply at each step. You’ll cross the finish line eventually.