After installation of KB4056892 boot failure, after roll-back error 0x800f0845

"To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time:

January 3, 2018—KB4056892 (OS Build 16299.192)

Unfortunately, I believed this and resumed updates - KB4056892 installed on my HP Pavilion laptop with a Turion 64 X2 and I had to do another restore.  If Microsoft paused this update, they didn't implement it correctly

JH - I too fell for this official statement from MS and for the 5th time since Sunday morning, had to restore my HP with Turion X2. Turned off WiFi and the laptop - now waiting until my Intel PC shows a confirmation that MS is not pushing download upon us with an AMD chip or that a fix has been found. Getting tired of Windows updating with some control from us.

I've got an old Asus box with an Athlon 64 4400+

This is what I've been able to do without a reload:

Machine starts and locks up. (This is probably where you are now)

I hold power till it shuts off, then turn it on.

It starts, then ends up with the same lockup at the Windows logo.

I hold power till it shuts off, then turn it on.

It starts, then finally says it's going back (forget the last wording)

It does stuff for a while, then either puts itself to sleep or reboots,

If it sleeps, wake it up.

After it boots, will then uninstall the update, which takes a while.

It may go to sleep at this point. Wake it up then reboot it. If don't wake, kill the power again.

Bring it up, should then come up normal!

Quickly log in, then download wushowhide.diagcab from Microsoft (search for it, easy to find)

Run it, then tell it to hide the update (KB4056892) and at this point you should be good.

Still unsafe to reboot. I had it reinstall again and had to redo the above steps. But I am posting it from the Athlon 64 X2 4400+ machine right now. So you're not dead, but it's a weird set of steps.

JH

I have been watching this and other threads and in one asked "How will we know when it is safe"?

It appears the 'hold off' is either not implemented as yet or not implemented correctly.

Not knowing when it is "safe" is just wasting our and Microsoft's cycles. That in and of itself is a problem.

If this is still going on tomorrow (1/10/2018) I will probably open yet another tread asking if the hold off is implemented and/or not working.  I will append a pointer in the threads I am following.

You know you have been around these things too long when the humor just takes over......

I mean, heck, why don't they just give us a call?

"To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time:

January 3, 2018—KB4056892 (OS Build 16299.192)

Unfortunately, I believed this and resumed updates - KB4056892 installed on my HP Pavilion laptop with a Turion 64 X2 and I had to do another restore.  If Microsoft paused this update, they didn't implement it correctly

I’m in the same boat (Athlon 64 X2 6000 on a Asus M2N-E motherboard).  What i can’t figure out is how to prevent the updates.  I have a restore point, which seems to work, but after the first reboot it immediately does some updates which borks the system, and I’m back to square one.  How do I get the restored system to not do any updates?

I even downloaded an ISO of the Fall Creators Update, but my machine hangs when booting off of it (with a really weird orange screen).