Same issue with a machine running a AMD Turion 64 X2 Dual Core Mobile Technology TL-60. No AV software but WD.
After installation of KB4056892 boot failure, after roll-back error 0x800f0845
Hi,
I have older AMD Athlon 64 X2 6000+, Asus MB, after installation of KB4056892 the system doesn't boot, it only shows the Windows logo without animation and nothing more. After several failed boots it do roll-back then it shows error 0x800f0845. Unfortunately, it seems it's not easy to disable the automatic updates without gpedit tweaks, so it tries installing and rolling-back the update over and over. The sfc /scannow shows no problem, in-place upgrade also doesn't seem to help. I can try full reinstall, but I doubt it will change anything. It seems like the update is binary incompatible with my old CPU. I understand that making the machine unbootable is the best protection from remote exploitation, but I would rather have the OS working. Especially if my CPU is not vulnerable to the Meltdown attack and the MS mitigation attempts for Spectre is more than questionable. I could find only some German and Italian people reporting the same issue (well the CPU is quite pre-historic and the KB update is very fresh), but no info / acknowledgment from the MS so far. I have Czech localization. Could anybody provide more information?
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
494 answers
Sort by: Oldest
-
Anonymous
2018-01-08T16:23:16+00:00 -
Anonymous
2018-01-08T16:55:12+00:00 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.
...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...
-
Anonymous
2018-01-08T17:15:42+00:00 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.........
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.
-
Anonymous
2018-01-08T17:20:22+00:00 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:
- Search for Feedback Hub in the Cortana search field, then click the app.
- Click Feedback found at the upper-left part of the window, then press + Add new feedback.
- Tick Problem, share any details you think are relevant, then choose an appropriate category and subcategory.
- 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.
- Click Submit once you've completed the form and monitoring.
- Click Continue using Feedback Hub.
- Click My feedback at the top, then find the item you have submitted (it may take a while to appear).
- Open the item you have submitted, then click Share.
- 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.
-
Anonymous
2018-01-08T17:26:10+00:00 Hi!
The update KB4056891 (version 1703) is affected too, it causes the same problems as KB4056892 by version 1709.
Regards
Roman