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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-08T21:40:32+00:00

    Michelle,

    I don't seem to be able to get at Feedback Hub. And I am very sure that MS appreciates our patience with this horrible situation. I am on 32-bit Win10 15063 (rolled back the last big updated since it messed me up as well). This is an AMD Opteron 180 processor which is 64 bit but cannot run 64 bit Win10 for some reason. In my case it was KB4056891 that seemed to be the cause. That's what showed up in the Windows Update Show/Hide tool and I have hidden it. I had to restore my C drive from a backup which I thankfully took on Saturday. I have spent 5 hours getting my system running again and I have still lost any changes to my C drive from Sunday. I offer a big thanks to MS for this. It is yet another reason why MS cannot be trusted to force updates down our throats. This policy must be changed and soon.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-08T21:46:18+00:00

    I've had this same problem on my AMD X2 +3800. Had to reinstall Windows 10 (1709) since auto repair failed. Froze again after installing the update on a clean install. It rolled back this time and, after the roll back was finished, i managed to pause updates to keep it from happening again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-08T21:54:41+00:00

    Same problem here with a Athlon 64 x2 4400+ Brisbane , it just locks and after a forced reboot it rollbacks.  I have a fx-4350 vishera and a a6-4455 trinity that updated without troubles.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-08T22:00:33+00:00

    Thanks, it seems I was able to log-in to the feedback hub with my liveid, but unfortunately the feedback app just shows working animation and nothing more. I will try later, but it doesn't seem like robust feedback platform to me :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-08T22:05:52+00:00

    Don't hold your breath on Microsoft fixing this. They only have to support Windows 10 on systems that the manufacturer's support it on, and no manufacturer is going to have 10 support for an ancient 939/AM2 machine.

    This is wrong assumption. Nobody said that it is not compatible. In fact the upgrade assistant showed that its compatible. If I knew it's not compatible and that the OS would kill my machines few months later, I wouldn't' buy the licenses. It's simple.

    Unfortunately what I said is truth. Microsoft has said it themselves; they only need to make sure Windows 10 works on machines that the manufacturer's support 10 natively on.

    Was this answer helpful?

    0 comments