Question

Q: After installation of KB4056892 boot failure, after roll-back error 0x800f0845

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?



* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

There is no antivirus installed, except  MS Defender and the update sneaked-in automatically through the Windows update.

Did this solve your problem?

Sorry this didn't help.

14 people were helped by this reply


seems is the same bug that is affecting Insiders in Build 17063.

check if this help you… enter in your BIOS options and check if there are options for HPET or Virtualization, and disable one of them or both if needed, then Windows should be able to boot again without stuck in Windows logo during startup.

Did this solve your problem?

Sorry this didn't help.

9 people were helped by this reply


As said in another thread, I have the same issue on an old AMD Athlon 64 X2 5200+ and Asus M3N78 Mb. I made a clean installation 4 days ago: until the update, it is working like a charm. Thanks for sharing Jaroslav, hoping they will fix the fix soon.

Did this solve your problem?

Sorry this didn't help.

4 people were helped by this reply


Thanks for info, but it doesn't seem to be related. I tried disabling both Virtualization and HPET and all combinations like Virtualization only and HPET only, but still the same, no boot. I rolled back the update and disabled automatic updates through the gpedit because otherwise the machine is unusable.

Did this solve your problem?

Sorry this didn't help.

14 people were helped by this reply


Same issue here, but with an AMD Sempron 3200+ processor and 32-bit Win10 Pro.  I had to do a reset to fix....

Did this solve your problem?

Sorry this didn't help.

2 people were helped by this reply


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.

Did this solve your problem?

Sorry this didn't help.

8 people were helped by this reply


 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
---

Did this solve your problem?

Sorry this didn't help.

2 people were helped by this reply


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.

Did this solve your problem?

Sorry this didn't help.


There is a German thread https://answers.microsoft.com/de-de/windows/forum/windows_10-update/windows-startet-nicht-mehr-während-neustart/2cb98e1d-57c7-40c8-ab8a-2347319614c9?auth=1

Did this solve your problem?

Sorry this didn't help.

4 people were helped by this reply


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

Did this solve your problem?

Sorry this didn't help.

7 people were helped by this reply


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
Question Info

Views: 58,722 Last updated: May 22, 2018 Applies to: