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

494 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-12T18:01:00+00:00

    Michael

    The fx-6300 system updated, including KB4056892, with no obvious problems.

    I did notice an "imbedded (?)"  AMD update that is not shown in update history but was shown by the show/hide diag.

    I am going to 'sleep' this fx-8150 device, move over to the fx-6300 system, try to get some work done and see if anything else got broken.

    You can check Update History to see if KB4056892 did install.

    If you are seeing other problems such as MB utilities, system stability and so forth, it might be best to start a different thread.  That will reduce the "Bricked" thread confusion and indicate to Microsoft that there are additional problems.

    If you do open a separate problem, please feel free to point me to it by appending here.

    Hang in there.  We will get over this sooner or later.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-12T17:34:05+00:00

    Simply put is that in their own words MS knows the hardware drivers are not updated but continues to force updates that they also know will disable the IS and then blames the hardware that was not updated.  Nice reply then.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-12T17:31:14+00:00

    Michael

    Oh, why did you not tell me this just 10 minutes ago. :)

    Ignoring a "Bricked" Athlon X2 6000+ system, I have just gotten the AMD fx-8150 system flying in more or less 'loose'  formation.  

    So....  I unblocked the backup AMD fx-6300 system.  It is likely committing suicide as I write this.

    Oh, well  "you have to get over this sooner or later, why not start now".

    I am going to let whatever happens happen.  I will reply here with results.

    If KB4056892 is severally damaging the newer AMD fx-nnnn systems, systems still being sold, we should address this in a new thread.

    Get back to you if I can. :)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-12T17:12:53+00:00

    its happening to us all ;( i think its killing me softly   windows 10 64-bit asus MD Amd fx-6300 six-core processor . started my pc left the room ,cameback just my curser on a blackscreen  ,restart , error popup : user name and password not correct ????? 3 sec  later  loggin screen ???

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-12T16:24:09+00:00

    I had same problem back in December after the Fall update. At first system hung up at Blue logo. Later learned to get by that by restarting several times. Also tried Recovery USB that I had made. Eventually (last night) put in a new hard drive and did a clean install. Have wasted good part of 3 weeks on this :(  

    Only just found out the details regarding problems with old AMD processors. In my case Athlon 64 X2 TK-57. Admittedly quite old, but it had been running Win 10 fine for about 2 years.

    My license is for Win10 Home, so when I re-installed from iso I chose that. I assume Pro version would not have been allowed.  Problem with Home is that you can't easily stop updates.  My concern now, is the problems will start all over again if MS/AMD screw up again. Current version is 1709 Build 16299.15.  Only been running for a few hours and that may change!

    Was this answer helpful?

    0 comments