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

I also have this issue issue...

16299.125 works fine but once I update to 16299.192, while it installs fine it's once you reboot the PC it gets to the Windows 10 loading screen and simply freezes and I have to hard power off and back on and it does the same thing but on the third boot it goes into automatic repair mode and returns Windows 10 back to 16299.125 and things work again but not long after it wants to install 16299.192 again which obviously won't work and will repeat the same process.

my fix... I installed Mint Linux (v18.3 Cinnamon x64) for the time being and I might consider staying with Mint Linux. but at least it's nice to know that Windows 10 will likely be fixed in case I never need to go back to it. but one thing I like about Mint Linux is that the touchpad on the laptop actually works with scrolling web pages etc (like on the right side of the touchpad) which does not work in Windows 10. but outside of that Windows 10 runs great outside of this major issue. but thankfully I have a CloneZilla image of 16299.125 which I can simply restore if I want to go back to Windows 10 once they sort this issue out and then update and that should be that.

side note: even clean installing Windows 10 16299.15 and then using the 600MB update file to bring it to build 16299.192 has this exact same freezing issue at the Windows 10 loading screen.

p.s. the above info is for a HP DV5-1002nr Laptop (10 years old) which has a AMD CPU (i.e. AMD Turion 64 X2 RM-70 @ 2Ghz). my main computer works fine with the 16299.192 update which has Intel i3-2120 CPU.

My experience with "2018-01 Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4056892)" on desktop PC, powered by Athlon 64 X2 4200+ CPU, Windows Version 1709 (OS Build 10.0.16299.125):

Update is downloaded and installed, but after the restart PC freeze/stuck at booting stage with Windows 10 logo on the screen, with no hard drive activity on LED indicator. Need two forced reset button hits, to invoke the Windows Repair to fix this.

I am glad that after the repair, the PC was successfully booted(Windows repair successfully fixing this thru rollback faulty KB4056892).

Download, and install manually KB4056892 from Microsoft Update Catalog, but the same stuck/freeze Windows boot screen issue. So we wait for fix.

But since Windows 10, there is a scheduled restart outside of active hours, so the faulty update will be auto installed - rollbacked again and again, creating a loop situation. Giving more control of the users to control/disable/enable the Windows Update process is not a bad idea.

These freezing/stuck boot/blue screen issues from Windows Update have been increasing in the recent months. Microsoft where is your testing team? Is this team existed? What they actually do? There is a strong effort to fix/patch Meltdown/Spectre vulnerability, but please, when another Meltdwon/Spectre like vulnerability comes in the future, don't fix one issue and broke many other things, as has happened and continues to happen to date.

I'm sure the inconvenience could have been saved if you had a reliable test team, that has just a PC/Notebook with one processor from each generation Intel/AMD CPU, to install the KB4056892 first on them, though you are Microsoft and you can afford it in the name of the company.

I gave a longer reply to someone else. I have "solved" the problem by pausing updates. Waiting for Microsoft fix.

BTW, I am using Microsoft Defender for now, which addresses the security issue. I will go back to Kaspersky when I get a chance to turn off the license on my old computer.

Essentially same as everyone else: Update partially installs, usually pauses at 2% or 8%, screen goes black with no apparent CPU or disk activity although "power on" light is lit, on/off front panel button has no affect, must use back-plane power rocker switch to turn off, turn back on, a little activity with blank screen, must use power rocker switch in back again, this time it starts and backs out of update and eventually I am back in business, except that faulty update is still downloaded and ready to install, which it does again in the middle of the night and I repeat process next day. So now I have postponed all updates and am waiting for Microsoft to fix this. Fortunately, with the new CPU and solid-state C drive this all cycles much faster than my old computer, but it is still annoying obviously. I leave my computer on overnight to record certain TV shows, which I now miss when the update/restart happens.

Adding my bricked Pavilion machine with AMD Turion X2 processor to the list. Was able to get it backup restored and running again but have had to disable WU service to ensure the problem doesn't come back. Might try the show/hide fix later but would like to see a true fix as soon as one can be found.