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-18T20:35:41+00:00

    MELERIX

    Ok, now I'm confused.  KB4073291 does appear in the catalog with today's date.

    Does KB4073291 solve the unbootable state problem caused by KB4056892.

    Looking at the description for KB4073291 it does not read like it addresses this "Bricked" problem.

    https://support.microsoft.com/en-nz/help/4073291/january-18-2018-kb4073291-os-build-16299-201

    Symptom

    Windows Update History reports that KB4054517 failed to install because of Error 0x80070643.


    When calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions.

    When calling CoInitializeSecurity, the call may fail when passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error returned on failure is STATUS_BAD_IMPERSONATION_LEVEL.


    The link (from yesterday) that addresses the unbootable state, still points to a catalog area still only having X64 fixes....

    Support Notes

    https://support.microsoft.com/en-us/help/4073290/unbootable-state-for-amd-devices-in-windows-10-version-1709

    Catalog

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4073290

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-18T04:14:22+00:00

    KB4073290 downloaded and installed from the Windows Catalog link above.

    I'm now running Windows 10 Pro version 1709, build 16299.194.

    I have up-paused Windows Updates. Checking for updates now reports that the Computer is up to date.

    Thanks for the fix,

    Dave.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-17T22:39:56+00:00

    I too am having issues, similar with my older AMD processor.

    This all started at the beginning of the year

    I don't get STOP errors,  My issues manifest when I insert a USB the stick is not recognized.

    I reboot my computer to see if that helps and I get BSOD inaccessible boot device.

    upon restoring the latest restore point (from 1/10) I can eventually get windows back up and running

    but the issue happens again.

    Today I restored to my NYE restore point 1/1 before the patch install

    the wushowhide.digcab didn't see the KB4056892, so I couldn't hide it.

    in update install history I see KB4056892, installed on 1/7  but I know it is not.

    (my system was brought back to 1/1 via system restore). maybe that helps

    I disabled windows update, anyhoo

    fingers crossed.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-17T20:41:45+00:00

    Same problem with my i7 4770k..

    Any news on an update?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-17T20:40:20+00:00

    Here's a naive question:

    My computer is in an unbootable state and cannot do updates. It has an AMD Athlon 64 x2 microprocessor. Is the assumption that I have reinstalled Windows 10 and ripped out all my software and have been slogging through all the attempted restarts skipping KB4056892 all this time and now I'll reinstall one more time and then do the updates?

    I've been using another computer while watching this thread and hoping to hear an answer that involves a list of steps to take to take my computer from its unbootable state to a bootable state. 

    One person suggests (after having success with this tactic) taking the boot HD out of the machine, plugging it into a (W10 compliant) machine with an Intel chip, booting up, then rolling back KB4056892 and saying no automatic updates. I can do that, but my question is, how confident can I be that Windows, when it sees my chip and motherboard and devices, will not take with it assumptions it got from booting up on some other machine, leading to problems?

    Others suggest making a recovery boot disk on another machine that is not crashed and booting up using that, then doing a rollback on the updates on the affected boot HD using command prompt commands. I'm worried about this because I was already theoretically able to do this from the command prompt in the Win10 diagnosis and recovery state, but the instructions given did not work.

    Was this answer helpful?

    0 comments No comments