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

Anonymous
2018-01-04T22:13:27+00:00

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.

0 comments No comments

494 answers

Sort by: Most helpful
  1. Anonymous
    2018-01-09T17:57:58+00:00

    Thank you. 

    I am most interested in how this works out.  I liked the ASUS utilities and, well, setting up Speedfan is a good deal more complex than "load and go".   In short, not for the casual user.

    In my case I am dealing with somewhat older MBs.  Nether  AI SUITE 1 (M5A88-V EVO) or AI Suit 2 (M5A97) will even attempt to install no matter how much you lie using compatibility.   It appears they make a second check to determine OS version.   Even PC Probe 2 on the currently  "Bricked" PC  will eventfully come back with "UNSUPPORTED OS"  no matter what you do with compatibility.  It may get farther, but it aren't going there.

    For the M5A97 system, all of the Speedfan configurations are still in place, leftover from the early Insider Program days.  Speedfan initializes and it should be a simple matter of disabling the ASUS tasks  and  turning off Q fan in BIOS.

    At least this is where I will find out if Speed fan controls hardware  in a legal fashion  and does not try to stick its fingers into ring 0.

    I will get to this after I deal with the "Bricked" device and place updates here.

    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

    At least on newer motherboards this is not really a Microsoft problem.  Let us not go there for the moment.

    Think more along the lines of two threads...

    1. How can you  get your ASUS Utilities working again.
    2. What to do if you can't.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-09T17:41:04+00:00

    I too am having this issue and I have been checking for any updates around the cumulative variety since it first started for me last month with the previous cumulative update 2017-12 1709 windows 10 x64, etc. where they first released the show and hide by-pass.  

    Have been very diligent checking daily for any updates similar to that one which caused me to reset my computer after reading the problems the previous update had.  I also noted the additional problem on this new update, (this forum included).

    After i went to bed last night this update was downloaded and attempted to be installed. When I woke this morning, my comp which is an HP AMD A4-5000 APU was on the welcome screen with my login showing indicating I had gotten some updates. After doing so it notified me of the failure.

    What bothers me is that I ran this show and hide feature and have been doing so daily and it did not even register that this was pending.

    if you offer people the chance to upgrade their systems from as far back as windows 7 with windows 10, then maybe you should check that far back on whether it is compatible with those systems that were available then before you do so.

    My system is a bit newer since I had it upgraded from windows 8.1 home. But I wonder at the constant trouble this is causing and if it happens again whether i can keep resetting/rolling back my computer without causing more harm down the road.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2018-01-09T15:37:04+00:00

    When you run Windows as a guest under your GNU/Linux host, and the Windows guest gets the update in question, does Windows still boot?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-09T11:27:46+00:00

    Alex

    If you don't have a AMD CPU then installing 16299.192 would be a good thing basically. so in other words, if you got a Intel CPU chances are the update will work fine. It worked fine on my i3-2120 computer but I had a problem with the update on my 10 year old laptop which has a AMD CPU.

    you can always create a restore point manually just in case or if you got another computer with a big enough hard drive to store a image you can use CloneZilla to make a image of your current 16299.125 computer as a extra precaution so if anything acts up, and say it fails to restore your computer to 16299.125 using Windows 10's built in repair mode(when it failed for me it takes 2-3 reboots before it enters automatic repair mode), you can use CloneZilla to restore the computer to exactly the state it was prior to running the update since it creates a exact duplicate of your hard drive when it images it. CloneZilla works great for imaging a computers hard drive and what's even better is it can store those images on a different computer through Samba connection (it supports v2 and higher so you ain't got to worry about the connection failing like it would if you only had Samba v1 which Windows 10 does not like as Samba v1 disabled by default). it asks you which Samba version you want to use if you use the samba portion of CloneZilla just select anything v2 or higher and it should work.

    Was this answer helpful?

    0 comments No comments