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

Hi everyone,

We are currently running through an investigation regarding the error code 0x800f0845 being received after installing the KB4056892 update.

Please wait for further announcements for the fix. In the meantime, we strongly encourage everyone to send a feedback to us using the Feedback Hub.

You can either vote on an existing submission or submit a new issue. When you submit a feedback item, we gather additional details and information about your issue that will help us in determining the cause and to be able to address it. Feedback items regularly receive Microsoft responses on the submissions in the Feedback app so you can see what we are doing about your feedback. Please re-visit frequently to see the status of your feedback items.

You can follow these steps in submitting a new feedback:

1. Search for Feedback Hub in the Cortana search field, then click the app.
2. Click Feedback found at the upper-left part of the window, then press + Add new feedback.
3. Tick Problem, share any details you think are relevant, then choose an appropriate category and subcategory.
4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you're done.
5. Click Submit once you've completed the form and monitoring.
6. Click Continue using Feedback Hub.
7. Click My feedback at the top, then find the item you have submitted (it may take a while to appear).
8. Open the item you have submitted, then click Share.
9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>).

We appreciate your patience regarding this matter.

If you have other queries, feel free to create a new post.

Regards.

Bob,

You have just frightened me.  a bit long, but let me explain.

The "Bricked"  AMD X2 6000+ is basically a high class "grunt work" machine.  Signal generator. DVD Burner, that type of stuff.  Things you wouldn't even tie up an AMD FX 6300 doing.

Although everything in its shiny new LianLi case except MB,CPU,Memory would serve a Ryzen system well, I expected it to die from "sift down".

So what does the  AMD FX 6300 (everything in its LianLi case except MB,CPU,Memory would serve a Ryzen system well ) do?

Light audio editing, web surfing, documenting, anything you wouldn't tie up an AMD FX 8150 with.

So what does the AMD FX 8150 (everything in its LianLi "ying and yang" case except MB,CPU,Memory would serve a Ryzen system well ) do.

Builds presentations, audio editing, multiple audio track mix downs, Video conversions and some 'light' video editing (while helping heat the house). 

By now you should see where this is going.  The plan was to replace the 8150 with Ryzen 1700x at least (Threadripper if I can afford it) around 3Q18/1Q19  at which time workload shifts one system to the left with the 6000+ and its ASUS MB going in a box in the closet.

KB4056892 sure messed up that plan.

Keep in mind that the 6000+ system is old. How old?  Old enough that it once was where the audio editor and video rips were done.  It has not had an easy life.  Ironic it should go end of life because of an Intel issue. 

Now you tell us that the new AMD systems are affected.  Now you see what is frightening.

The 8150 system survived the fix but not without problems.  See.........

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/kb4056892-breaks-asus-ai-suite-ii-on-amd-fx/f1d88d90-42a4-4476-b2ea-fe9cec00bf82?tm=1515361378804

By the way I am not seeing appends in that thread , but do get the e-mails of appends made.  That's odd.

None the less, looking around AMD forums the only mention of KB4056892 is that it exists. 

I do not know if Athlon 2's ironic death  would trouble them . 

If this is affecting their flagship.....................

If I can be of any assistance  to you working this "Ryzen" problem, let me know.

you can recover you Windows using a System Restore Point previous to the update, and then you can pause Windows Updates until next update or until we have some news about if Microsoft have fixed the bug or not.

http://news.softpedia.com/news/windows-10-cumulative-update-kb4056892-meltdown-spectre-fix-fails-to-install-519238.shtml

...but the update does not create a restore point... Windows 10 has disabled by default this... and the user does not imagine the the update could be catastrophic...

How can one stop Windows Updates? Please explain..

Thanks,

 Angelo.

It's good habit to enable system restore at less for system volume - it helprd to me so many times...

Same issue with a machine running a AMD Turion 64 X2 Dual Core Mobile Technology TL-60. No AV software but WD.

KB4056892 failure on 18 month old Surface

I had to reset my Win 10 Surface Pro 4 today following a network driver problem.  I then dutifully checked for updates and had a very lengthy encounter with KB4056892.  On restart my machine continuously hung at blue screen and "preparing to install update".  It required a hard restart and auto update began trying to install the update again.  Next restart presented the same problem and round the loop we go again!

I tried downloading the update direct from the MS site.  Same problem occurs.

This fairly lengthy conversation seems to point the issue at old hardware.  My Surface Pro is nearly 18 months old so very nearly obsolete!  However, I found a mechanism for a fix within this conversation. 

1.Turn off auto updates

2. Run wushowhide.diagcab which can be found at https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-windowand turn off KB4056892
3. Restart - you system will hang again because it has already started to try and install KB4056892 - hard restart to interrupt blue screen
4. Login then restart again - should restart happily?
5. Turn on auto updates but wushowhide is now keeping KB4056892 at bay.

I think Microsoft have a major issue here?  I look forward to an update that correct this issue so that I do not have to live with the auto updates telling me that I have got an update to install!!