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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-21T19:35:15+00:00

    @BeastMstr

    I was able to re-activate Win 10 which was unbootable staying at the windows logo, same as you mentioned.

    My machine is an AMD Athlon 64 x2 5600+ with Windows 10 Pro, Version 1709

    I did the following:

    1.

    download the windows10.0-kb4073291-x86_898d588fa98a78fdb7f121f14b74f51df2a9416d.msu from Microsoft: https://www.catalog.update.microsoft.com/Search.aspx?q=windows%2010%201709%20cumulative%20update%20

    2.

    store the package onto the partition with the unbootable Win 10

    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

    5.

    reboot

    Hope this helps

    Cheers Blubi

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Monkey57 3,535 Reputation points
    2018-01-13T16:24:24+00:00

    On a AMD X2 L310 processored device, DISM stopped the looping.  Note the odd times in the 'results' below.  Even though MS had stopped the update, it was still Staged and on the system.... After KB4056892 (16299.192) was removed with DISM, & it is not being pushed by MS;  'Windows Update' is now running normally, after multiple checks and reboots..  

    On an Auto restoring AMD X2 L310 processored device this stopped the looping:

    Even though KB4056892 is showing hidden by the Hide/Show troubleshooter ... I went ahead & used DISM to remove the Staged Package from this 1709 x64 system from within Windows.

    from an elevated command prompt ran:

    dism /get-packages /Online

    pertinent results at the end:

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6

    State : Installed

    Release Type : Security Update

    Install Time : 1/12/2018 12:01 PM 

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    State : Staged

    Release Type : Security Update

    Install Time : 1/12/2018 3:12 AM

    16299.192.1.9 locked the device; so I removed it:

    Back in the elevated command prompt i ran (copy all the bolded text as one line, command may be wrapped when displayed on MC;  if your results from the previous DISM command are the same):

    dism /Online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    pertinent results at the end:

    Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    [==========================100.0%==========================]

    The operation completed successfully.

    Windows Update Completed successfully, it downloaded some Defender updates, and left no pending updates.  Even after rebooting device multiple times over many hours.

    see also:

    Opteron185 replied on January 9, 2018 1/9/2018 8:11:49 PM (on page 18 of this same question)

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?page=18#LastReply

    "If you can boot into your recovery environment and open a command prompt, you can follow its instruction starting from step 3.

    2)  USB boot your system into the recovery environment - pull up a Command Prompt

    3)  At the command prompt - first determine what drive letter your boot volume is assigned.  On mine, it was E:.  It will likely be C: D: or E:.  You might find that do a c: - then doing dir - hitting enter or d: - dir - enter - will be easiest to figure out which drive it is.  You could also go into diskpart and look at the Volumes (diskpart (enter) - list volumes (enter) )

    4)  Substitute the correct drive letter in each of these commands (where e:\ is your Windows volume)

    dism /image:e:\ /get-packages

    5)  After you run this command - it will show a list of packages.  Look for the most recently installed - it likely will say "Install Pending"

    6)  Take that Package identity from those results and run the following command (where package name is the package you want to remove):

    dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf385ad364e35~amd64~~15063.850.1.10 "

    The package you need to remove (KB4056892), for 1709 x64  is -> Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-07T03:13:30+00:00

    Same issue.  Love it when Microsoft creates more problems with updates.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-05T21:07:53+00:00

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-05T07:29:10+00:00

    As said in another thread, I have the same issue on an old AMD Athlon 64 X2 5200+ and Asus M3N78 Mb. I made a clean installation 4 days ago: until the update, it is working like a charm. Thanks for sharing Jaroslav, hoping they will fix the fix soon.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments