Windows Server 2012 R2 Stuck on "Undoing Changes"

linktoinsanity · 12 Apr 2016 at 12:44

Hi there,

I have a Hyper-V virtual machine which is a new load, which we ran Windows Updates on, stuck on a screen saying "We couldn't complete the updates. Undoing Changes. Don't turn off your computer" However it has sat there for hours now.

I have tried following a guide on this site here: https://social.technet.microsoft.co...all-on-generation-2-vms?forum=winserverhyperv

And it does not seem to make any difference. Even booting the machine up in Safe Mode makes no difference. Does anyone have any ideas?

Googling just links back to the same thing I have tried. Thanks.

Glanza · 12 Apr 2016 at 12:58

I've just got the exact same problem as you, fired up a fresh Hyper V with a clean install of 2012 r2 this morning, ran Windows Update and it's done the same 'We couldn't complete the changes'

Get the feeling a update has broken it yet again. I've got nothing set up on mine so worse case will be deleting it and starting again.

linktoinsanity · 12 Apr 2016 at 13:11

Thanks for your reply. At least this shows the issues is more widespread than just us.

Have you tried the secure boot fix? It's does not work for us, but might for you?

We would prefer not to have to start again after getting a certificate installed and working, however it looks like that may be our only option too.

Unless of course, someone else has another fix?

nutcase · 12 Apr 2016 at 13:44

I learned a long time ago on a new install to only do a couple of hundred MB of updates at a time to avoid this.

tribz · 14 Apr 2016 at 08:16

That has been my fix also when a server does this, just do a handful of updates at a time.

Glanza · 14 Apr 2016 at 08:58

Tried secure boot fix didn't resolve it. Ended up leaving one over night and it fixed itself and needed a few updates after.

The other one I started from scratch but did the updates in batches of 50 till it was upto date.

Annoying but luckily nothing lost apart from a hour of my time.

linktoinsanity · 14 Apr 2016 at 09:34

We resolved it by restoring a backup from before that morning's restart. It still had installed most of the updates, but not that troubled one. I removed and hid the update that I read caused the issue. It's been fine since.