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-12T01:12:47+00:00

    As I complained to Microsoft On line Help, they connected me to a technician who could not solve the problem, the he said it has to go to someone higher and I have to agree on an appointment for them to contact me which was on Monday between 8 and 10 Am.  She called, and asked to create on the not affected Lap top a contact way for her to control my computer.  I agreed and she installed a bootable file on a USB Memory 16 GB, which I later on attached to the computer affected by that update and by the way ALL MY COMPUTERS have AMD X Chips.

    As she went on my computers she discovered numerous "Defects" or "Mistakes" some during the time it was XP as mine developed from XP, to 7, to 8, to 8.a to current Windows-10.

    She said the only solution is to reload Windows-10 from the USB memory and to create the computer afresh.  Meaning that it will stay x86 (i.e.32 bit) and I am still struggling in the re-loading of the software and some of the data she could not keep.

    MY ADVICES:

    1.  It is not related to AMD-X chips.

    2.  It MIGHT BE (not necessarily so), to Windows-10 32 bit (X86).

    1. As per her action, you have to take the difficult job of Recreating your Windows-10, using a Bootable USB (8 GB or more) or DVD, best if developed on the affected computer as then it will have the same License information as your existing computer (or you have to pay for a new Windows-10 license).

    AGAIN, I REPEAT IT AS IT WAS MENTIONED WRONGLY ON THE FORUM, IT IS NOT BECAUSE OF AMD-X chips, but related to existing problems in your computer since early days you started using it and were not detected before this most recent update in 2018.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-12T01:12:06+00:00

    https://answers.microsoft.com/en-us/profile/5f0ae50f-f8f4-4baa-948f-0c527af42e3b

    MaroBeyUT

    Why are you posting this over and over?

    I don't believe any of this crap that Microsoft have told you.

    You didn't say that what you did has worked.

    Others have posted that installing a new copy of Windows 10 has not fixed the issue.

    In my case, my AMD computer that was made unbootable when trying to install this update was a brand new install of Windows 10 version 1709. In was not an upgrade from any previous version of Windows.

    Sorry.  I am new to this forum and tried maybe now I see it, not the best way.

    What I posted is exact description of what happened in my computer which was XP, then 7, 8, 8.1 and then Windows-10.

    What MS lev-2 technician did, WORKED and I am using the computer now and has restarted it already more than 8 times and am sending this reply from it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-12T01:06:20+00:00

    https://answers.microsoft.com/en-us/profile/5f0ae50f-f8f4-4baa-948f-0c527af42e3b

    MaroBeyUT

    Why are you posting this over and over?

    I don't believe any of this crap that Microsoft have told you.

    You didn't say that what you did has worked.

    Others have posted that installing a new copy of Windows 10 has not fixed the issue.

    In my case, my AMD computer that was made unbootable when trying to install this update was a brand new install of Windows 10 version 1709. In was not an upgrade from any previous version of Windows.

    Sorry I am new to the forum and tried replying to as many as I could.

    The solution I posted worked and if you are willing to do the same, I expect it will work as it did by the second level technician from Microsoft did to my computer.

    My computer has AMD X chip and is 32-bit because some Apps I have are old, since the 32-bit era (XP and 7).

    What is funny is why the previous too many updates workrd in presence of the same errors MS Lev-2 Technician said exist?

    Definitely in my personal opinion it is something that MS should not have created in this newest update of 2018-1

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-12T01:01:16+00:00

    It worked and the computer is running perfectly.  But I have to spend a lot of time now trying to install all the apps and relate them to their data.

    I have plenty of data on additional three hard drives.

    Some apps are no longer able to work on the new Windows-10 that MS Rep installed a fresh.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-12T00:57:46+00:00

    https://answers.microsoft.com/en-us/profile/5f0ae50f-f8f4-4baa-948f-0c527af42e3b

    MaroBeyUT

    Why are you posting this over and over?

    I don't believe any of this crap that Microsoft have told you.

    You didn't say that what you did has worked.

    Others have posted that installing a new copy of Windows 10 has not fixed the issue.

    In my case, my AMD computer that was made unbootable when trying to install this update was a brand new install of Windows 10 version 1709. In was not an upgrade from any previous version of Windows.

    Was this answer helpful?

    0 comments