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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-05T17:14:54+00:00

    Thanks for info, I will try another AMD Athlon machine later today. This issue is very painful especially in production. Luckily, it usually roll-backs the update after several (IIRC two) unsuccessful boot attempts. MS QA is getting worse and worse. Anecdotally I could probably live without this buzzword update because my AMD doesn't seem vulnerable to the Meltdown and the Spectre mitigations it's bringing don't help much.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-05T17:42:18+00:00

    Could anybody provide more information?

    PS>.\err 0x800F0845

    as an HRESULT: Severity: FAILURE (1), Facility: 0xf, Code 0x845

    for hex 0x845 / decimal 2117 :

      NERR_RedirectedPath                                           lmerr.h

    1 matches found for "0x800F0845"

    https://msdn.microsoft.com/en-us/library/windows/desktop/aa370674%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

    2117 The operation is invalid on a redirected resource. NERR_RedirectedPath

    This may only be a clue because the 0xF Facility code supposedly means SetupAPI.  Often though there is some commonality between the sets of codes.

    See if this is being reported by SetupErr.log.  Then use that timestamp to find some context in SetupAct.log

    HTH

    Robert Aldwinckle

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-05T18:21:42+00:00

    Thanks for info. This seems very helpful and promising. My machine has some junctions, so it could be related. I will check the logs thoroughly later today. I could understand if it fails and writes the error, but it crashes hardly very early during the post-install reboot, nothing was reported. I had to powerdown the machine because it didn't react to anything. When repeated for several times (IIRC two times) it detected that something is wrong, started auto-repair and rolled back the update. Then it booted OK. Then I could see the error in the windows update.

    Was 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-05T21:11:32+00:00

    my machines affected are AMD Athlon 64 X2 too, and with Windows Defender only, so this means the update broken some compatibility with AMD CPUs ? :S

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments