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-27T02:48:22+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

    Thanks Blubi, youre a star!  Different patch, kb4073291 for you, kb4073290 for us, but at least you have logged the correct procedure.  My partners PC is back up again using this process, she is a happy camper.  A few things to add - as not everybody would be comfortable with the command prompt.

    Firstly, for those reading this:

    Problem:

    AMD 4850e Athlon x2 based 64 bit system running Windows 10 received patch KB4056892 and would get to the WIN10 logo and effectively lockup.   Initially this could be resolved by rolling back to a restore point through the advanced recovery screens, until yesterday, when all the restore points were dropped.  This only left ONE rollback option, which had identical results, a hung WIN10 logo on startup - ie a loop to nowhere.  

    Resolution #A:

    According to Microsoft..

    How to get this update


    This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.

    With the former option being just fantastic if you are locked on a logo....  and the latter being the most minimalist fix description for a complete failure in coding that I have ever seen! 

    They have disabled a customers operating system, the page should include a detailed procedure,  not just a download link.  I have to agree with a previous poster, as an IT specialist with over 30 years experience this ranks at close to #1 in the epic failures I have experienced!  I too would fire the IT dev department, and then sack whoever is managing customer liaison.  

    Most disturbing is that many people are either not IT savvy, or only have access to a single machine.  I expect they would have (in desperation) gone through 'reset my PC' meaning a very temporary fix *maybe*, and the requirement to reload ALL applications, activation keys, profiles etc etc.

    Resolution #B:

    Some more details to the resolution process: 


    Note that this which does nothing more than apply the kb4073290patch, there is no other system impact.

    Get onto another PC/Laptop and download that MSU file from the catalog from the update catalog

    Its around 600 MB so drop it onto a flash drive/memory key, or burn it to cd/dvd.

    Boot up your bricked machine

    If it goes to the locked WIN10 logo then reset it to boot again until it drops into repair/diagnosis

    advanced options > command prompt

    ..because i have some grey hair I know CMD as just a DOS emulator, others may not be so comfortable with this.

    Note if you want to copy paste (such as the long patch name..) then right hand click in the CMD top window header - select mark, highlight with the mouse, then right click in header and select copy, repeat the process to paste...

    insert your USB key (or whatever media you have chosen)

    from command prompt:

    go to the C drive - providing that is where you have installed Windows. 

    Z:&gt;C: (Go to the C drive)

    C:&gt;cd ..   (if you are in a directory and need to drop back) 

    C:&gt;md patch   (make a dir for this KB)

    C:&gt;md temp     (create another one for installing the KB)

    C:&gt;cd patch   (go there)

    C:\patch>dir e:  (find the MSU file, in my case e: is the USB drive, if you are not sure just keep checking D: E: F: etc until you find it)

    C:\patch>dir e:

    Volume in drive E has no label.

    Volume Serial Number is 0039-08C1

    *Directory of E:*

    27-Jan-18  01:14       632,139,610 windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu

    (copy the patch from the USB, in my case e:,  to the folder you created)

    C:\patch>copy e:windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu *

    C:\patch>dir  (should show the MSU file is there)

    ..then

    (use DISM to install the package - there is more info here if required:

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options)

    C:\patch> Dism /Image:C:\  /Add-Package /PackagePath:C:\patch\windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu**/norestart /scratchdir:C:\Temp**

    Once that completes:

    C:\patch>exit

    Drop back through those advanced menus until you find power off.

    Then boot the machine up.   

    Good luck, the patch worked fine for me.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-08T00:58:35+00:00

    Ciao Snoopy,

    may you explain how you have "changed update polices so Windows will download updates with notification but  not install them until YOU approve them"?

    Thanks,

      Angelo.

    Sorry, my description was not correct of what policy I set. I set it to notify me when an update was ready to be downloaded and installed. I can choose to not download it.

    This is for Win 10 pro, not sure whether it will work in other versions.

    Group Policy Editor

        Open the Run command (Win + R), in it type: gpedit.msc and press enter.

        Navigate to: Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update.

        Open this and change the Configure Automatic Updates setting to '2 - Notify for download and notify for install'

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-06T00:17:44+00:00

    I can report the same problem on Athlon X2 4200+.

    I was forced to perform a system reset as automatic repair as well as system restore also failed when the os did not boot (like AngeloGr above).

    After a reset and and then a clean reinstall (wiping c: clean), this update still freezes the system at startup. Also, windows update keeps insisting on installing this update, if i want to get other updates and there seems no way to block this update. So it seems that either i stop updates or everytime after updating reboot the system after failure till it goes into automatic repair and reverses this update (virtualization was off at all times).

    Any ideas... And MS, at least officially acknowledge the bug and that someone is looking into it.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-06T00:17:13+00:00

    you can pause Windows Update inside Advanced Options in Windows Update options.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-01-06T00:07:16+00:00

    you can recover you Windows using a System Restore Point previous to the update, and then you can pause Windows Updates until next update or until we have some news about if Microsoft have fixed the bug or not.

    http://news.softpedia.com/news/windows-10-cumulative-update-kb4056892-meltdown-spectre-fix-fails-to-install-519238.shtml

    ...but the update does not create a restore point... Windows 10 has disabled by default this... and the user does not imagine the the update could be catastrophic...

    How can one stop Windows Updates? Please explain..

    Thanks,

     Angelo.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments