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

Remember, AMD is finally releasing a firmware patch so keep an eye on your manufacturer's website as well as Microsoft Updates for THAT!

https://www.theverge.com/2018/1/11/16880922/amd-spectre-firmware-updates-ryzen-epyc

The point is that they DO know ahead of time. Intel and ARM were ready and AMD could have been also but they were dragging their feet claiming the issue didn't affect them.

Those are the facts...sorry you don't like them.

KB4056892

does not work on AMD Systems. That is understood. At least, not on all of them. Some have claimed success with the install of this update, Most say it has caused them endless headaches and everybody seems to think this is Microsoft's fault. It isn't. AMD caused its customers the same problems back in 2008 when we were all trying to download and install Service Pack 3 for Windows XP.

The simple fact is: AMD provides terrible Customer Support and always has.

Let's not forget the incident in 2007: http://www.eweek.com/networking/amd-phenom-barcelona-chips-hit-by-lock-up-bug

Or the fun people had in 2000 when AMD  caused a System Shutdown when its k6-2 trued to run at over 350 Mhz.

The important thing to remember here is that ARM and HP (among others) keep their drivers up to date as the technology moves forward.

And now, finally, it can be announced: 

https://www.theverge.com/2018/1/11/16880922/amd-spectre-firmware-updates-ryzen-epyc

Well that is a load of bull.  Yes there is an issue and Microsoft knew this. However MS released a fix that disabled their own system and you say it is someone else that is to blame.  You are saying in fact that it is up to hardware manufacturers to know ahead of time what MS is going to do and they are responsible to fix it before MS wrecks their own OS. Guess they could if they went back in time. I say you must be a MS employee to even dare try to tell us that and it is am obvious attempt to shift the blame for screwing up all our systems. Keep it up and maybe we all switch to Apple.

will then see if the bad update can be started again, so it can be hidden then uninstalled

There's no need to start searching for updates, the Hide/show troubleshooter de facto do a search for updates itself.

Different suggestions work for different machines.

I should have quoted the interesting part.

The poster offers a way to uninstall the offending update in a system already compromised.

If you can boot into your recovery environment and open a command prompt, you can follow its instruction starting from 3).

3)  At the command prompt - first determine what drive letter your boot volume is assigned.  On mine, it was E:.  It will likely be C: D: or E:.  You might find that do a c: - then doing dir - hitting enter or d: - dir - enter - will be easiest to figure out which drive it is.  You could also go into diskpart and look at the Volumes (diskpart (enter) - list volumes (enter) )

4)  Substitute the correct drive letter in each of these commands (where e:\ is your Windows volume)

dism /image:e:\ /get-packages

5)  After you run this command - it will show a list of packages.  Look for the most recently installed - it likely will say "Install Pending"

6)  Take that Package identity from those results and run the following command (where package name is the package you want to remove):

dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf385ad364e35~amd64~~15063.850.1.10

Thank you for reposting Opteron185's (pg18) suggestion, I will try it on the systems that don't self restore, if it works, will then see if the bad update can be started again, so it can be hidden then uninstalled (although MS says they have stopped the update, as of last nite;  some AMD machines where still re-installing it).