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-23T00:32:32+00:00

    why so many users have athlon and me the only with turion?

    You're not alone - I have an HP Pavilion with a Turion 64 X2 Mobile TL-56 and it locks up at the Windows logo on reboot

    I am right with you as I have the amd turion tl-60 2.00Ghz and have the same issue.

    I should add that this laptop runs perfectly fine using an SSD and I do not want to dump it.

    Microsoft - please fix this update.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-22T01:32:07+00:00

    Blubi wrote:

    //...

    3.

    boot the machine into Windows 10 Repair Mode, Advanced Options, select Command Prompt

    4.

    execute the following:

    Dism /Image:C:\ /Add-Package /PackagePath:<path to the package>\windows10.0-kb4073291-x86_898d588fa98a78fdb7f121f14b74f51df2a9416d.msu /norestart /scratchdir:C:\Temp

    //

    Implementing this instruction after downloading the .msu file and copying it to the , I got the message:

    Deployment Image Servicing and Management Tool

    Version: 10.0.14393.0

    Error 1639: The command-line is missing a required servicing command.

    I have tried doing similar fixes from other posters and the same result. 

    I wonder if this is a difference between my version and the Pro version or some other problem. I am running Win 10 home 10.0.14393 

    Webb

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-20T21:04:13+00:00

    I made the update mentioned by you above, in update to settings, I checked and download update even over metered data connections!

    Everything runs smoothly!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-20T19:09:07+00:00

    Thanks for all the comments and the links  some of you guys posted. I installed the new update that is supposed to replace the old one without any problems :) :)

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-20T08:31:31+00:00

    Apparently MS has released a fix to this update, yet again my AMD laptop is pulling this update:

    2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)

    How do I stop this?!!!!! Very angry with the shambolic solution to the problem. I have not updated my laptop all January and I cannot use this laptop at all. Machine is rendered unusable!!! 

    I do not have any antivirus apart from the standard Windows Defender.

    Was this answer helpful?

    0 comments No comments