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

got the update again after restart and another rollback fixed issue with network.

NO they have not. I can attest to the fact that my computer is stuck in a continuous boot loop that never ends, no matter what you do. Tell me, will you be paying us back for the WEEKS we spent getting NO HELP by Microsoft ? Or maybe because you read a few things you think we have all been helped. Because this thing is pages and pages long and gets longer every single day. More and more people angry with machines that aren't usable anymore due to negligence. Maybe Microsoft should reach out to us, apologize for the weeks of anguish visited upon us by them. This is a PR nightmare and instead of making it good, they stay silent, or maybe as their mouth piece, you can let them know. We are thousands strong, thousands that are already looking to other systems like Linux. As you can read I am one of many who are growing more and more angry by the day, so maybe think about that before you come on here and pretend to have a fix. Either HELP or get off this thread.

Can one of you write out just how to fix this for those of us who may not be as savy in the tech department. I would like to get my machine back this year, and since Microsoft is doing nothing, I would like directions on how to do it, step by step, please Help us

Dear Wiley Colons,

On p. 37 above (Jan 21) Blubi states a method that worked to revive his AMD Athlon x2 64 chip based computer. That method worked for me (I have the same chip) when I figured out what version of Windows 10 I had and downloaded the proper "patch" from Microsoft's Cumulative Updates page. 

MrCurlyWirly on p. 39 above (Jan 26) offered a fuller step-by-step recipe (with bold formatted steps) which he called Resolution #B and which I actually followed to the letter, except for the filename of the patch file. If your computer is an AMD Athlon 64x2, this ought to work, providing you select the proper patch from the proper Cumulative Update page. A few things will be required: 1. Use of another machine (which you appear to have). 2. A USB memory stick with a few GB of memory on it. 3. A machine that has some GBs free on it. I had to get rid of some stuff on my very full HD (using the command prompt only, e.g. cd TEMP, dir, del this or that) in order to make room for the update. 4. A basic ability to understand and use DOS commands. If you do not have 4. maybe you need a friend to do this fix for you.

The person above on this page of replies who said the fix is "easy" may not be speaking for everyone. The recipe must be followed literally to the letter or you will get an error message or a file-not-found message. But it does work and the actual implementation sitting at your keyboard takes a half hour or less. The computer will spend a good while installing the update. 

One thing I will mention, as a person who has forgotten most of what he ever knew about doing command line instructions from the c: prompt, is that if there seems to be a space between a \ or / character and the character after or before it in the command example, it is probably there. You can check by attempting to select it with your mouse.

Good luck!

Webb

you just need to install KB4058258 and the problem will be fixed.