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

Unfortunately, as this is an older (but still perfectly functional laptop) it is no longer supported by HP.

There have been no bios or driver updates for this machine for several years. But it runs Windows 10 fine and runs all the software I need it to. I always allow the O/S to install the latest updates - but of course that was the cause of the problem as Microsoft's update was buggy! 

Microsoft should have a system built into the O/S such that if an update fails to install the user can have the option to disable it. They should not send out updates that break machines with no easy option to  recover. I may have now got my machine to work, but I suspect many others will have been less fortunate (and I am fairly tech savvy).

Yes, it does help to check regularly for updates to your device. Not only from Microsoft but also from your computer manufacturer (who will often have BIOS and CPU updates before they are available from Microsoft).

I'm pleased to say, I've now got my system working again (HP Pavilion dv7-2110sa with AMD Turion X2 CPU...

After the initial lockup problem following Windows automatic installation of the dodgy KB4056892 (OS Build 16299.192), I installed the  "Show or hide updates" troubleshooter package and used this to prevent the KB4056892 patch until Microsoft fixed the issue.

The latest patch KB4058258 is supposed to resolve the problem so tonight I ran the "Show or Hide Updates" troubleshooter again and disabled the block on KB4056892. Windows immediately started to download the troublesome update again! However, BEFORE it rebooted the machine again, I manually downloaded the latest update KB4058258 (OS Build 16299.214) from the Microsoft Update Catalogue Website from here: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4058258

I manually ran this update. And thankfully after the PC has been rebooted twice, all is now well.

It's good Microsoft eventually got round to fixing this. But we should never have got into this situation in the first place. Before releasing the original patch it should have been thoroughly tested on a wide variety of hardware and processor platforms!

Good to hear you have resolved the boot issue with your machine. But I'm curious, if you had booting troubles, how were you able to install and run the "Show/Hide Updates" utility? I can run this while on build 1607 because the system boots fine. That wouldn't have worked though using build 1709 (non-bootable). But based on earlier discussions above, perhaps I need to find and uninstall KB4056892 since it is not part of build 1709. Then, install patch KB4057142. THEN, attempt to re-install 1709 and hope for the best.

Crap, I have this issue too with an older AMD HP. After the update it does not even get as far as the login screen but freezes on the windows bootup splash screen, no HDD activity nothing.

Rolling back works but it installs with the same issue again! Should I just add this buggy update to an exeption not to install or is there a fix? Will it recieve updates afterwards automatically or are they dependent on this update? I lose access to the computer this evening and only have a short while to troubleshoot in the evening :(

Much to my dismay, I seem to also have the same issue. Everything was working fine once I rolled back from 1709 to 1607. However, it obviously detected being out of date and eventually started the upgrade process again. At this point I guess I'm not quite sure which update(s) I should block such that when 1709 goes to reinstall, I don't encounter the same non-boot issue. Or, is it simply a matter of installing patch KB4058258 before the 1709 update self-initiates? Again, much appreciated to those who are sticking around and helping the rest where this issue continues to persist.

I'm pleased to say, I've now got my system working again (HP Pavilion dv7-2110sa with AMD Turion X2 CPU...

After the initial lockup problem following Windows automatic installation of the dodgy KB4056892 (OS Build 16299.192), I installed the  "Show or hide updates" troubleshooter package and used this to prevent the KB4056892 patch until Microsoft fixed the issue.

The latest patch KB4058258 is supposed to resolve the problem so tonight I ran the "Show or Hide Updates" troubleshooter again and disabled the block on KB4056892. Windows immediately started to download the troublesome update again! However, BEFORE it rebooted the machine again, I manually downloaded the latest update KB4058258 (OS Build 16299.214) from the Microsoft Update Catalogue Website from here: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4058258

I manually ran this update. And thankfully after the PC has been rebooted twice, all is now well.

It's good Microsoft eventually got round to fixing this. But we should never have got into this situation in the first place. Before releasing the original patch it should have been thoroughly tested on a wide variety of hardware and processor platforms!

So just for my understanding, you're suggesting that I install KB4057142 while currently using the Win 10 1607 build, then attempt to re-install build 1709 and hopefully that will eliminate the boot failure issue(s)?

yes, that is my idea, I hope it solve the issue for you.