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.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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.
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.
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.
Even though KB4056892 is showing hidden by the Hide/Show troubleshooter ... I went ahead & used DISM to remove the Staged Package from this 1709 x64 system.
from an elevated command prompt ran:
dism /get-packages /Online
pertinent results at the end:
Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6
State : Installed
Release Type : Security Update
Install Time : 1/12/2018 12:01 PM
Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
State : Staged
Release Type : Security Update
Install Time : 1/12/2018 3:12 AM
16299.192.1.9 I am afraid of so I removed it.
back in the elevated command prompt i ran (copy all the bolded text as one line, command may be wrapped when displayed on MC; if your results from the previous DISM command are the same):
dism /Online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
pertinent results at the end:
Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
[==========================100.0%==========================]
The operation completed successfully.
Windows Update Completed successfully, downloaded some defender updates, and left no pending updates.
Could anybody provide more information?
PS>.\err 0x800F0845
NERR_RedirectedPath lmerr.h
| 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
Same issue here, but with an AMD Sempron 3200+ processor and 32-bit Win10 Pro. I had to do a reset to fix....