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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-18T20:57:40+00:00

    You mean KB4073290?

    KB4073290 is for x64/64bit and KB4073291 is for X86/32bit, and boot updates solved the same issue with AMD Athlon 64 and related CPUs with unbootable status caused by KB4056892.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-18T20:52:59+00:00

    You mean KB4073290?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-18T20:48:44+00:00

    Does KB4073291 solve the unbootable state problem caused by KB4056892.

    yes, it does, I've installed it in a x86/32bit machine and it solved the issue.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. 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
  5. Anonymous
    2018-01-18T20:03:44+00:00

    only my update doesn't find it and instead still installs KB..892 with locked start and autorecovery after 3x booting.

    Think I will have to install the KB..291 manually ;-(((

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments