KB4058258 shouldn't be causing boot process to fail, because it contains the previous fixes for boot process.
After installation of KB4056892 boot failure, after roll-back error 0x800f0845
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
494 answers
Sort by: Most helpful
-
Anonymous
2018-02-02T06:55:55+00:00 -
Anonymous
2018-02-02T06:52:03+00:00 It seems it was the same old network issue which resolved after next restart. But it is suspicous that kb4058258 caused a boot process to fail again. It may contain some more bugs. But everything else is fine runs better than before.
-
Anonymous
2018-02-02T03:56:58+00:00 error 0x80240034
0x80240034 WU_E_DOWNLOAD_FAILED Update failed to download.
Find that in ReportingEvents.log for the timestamp. Check WindowsUpdate.log for more context.
-
Anonymous
2018-02-02T02:11:50+00:00 Crap, I have this issue too with an older AMD HP. After the update it does not even get as far as the login screen but freezes on the windows bootup splash screen, no HDD activity nothing.
Rolling back works but it installs with the same issue again! Should I just add this buggy update to an exeption not to install or is there a fix? Will it recieve updates afterwards automatically or are they dependent on this update? I lose access to the computer this evening and only have a short while to troubleshoot in the evening :(
Much to my dismay, I seem to also have the same issue. Everything was working fine once I rolled back from 1709 to 1607. However, it obviously detected being out of date and eventually started the upgrade process again. At this point I guess I'm not quite sure which update(s) I should block such that when 1709 goes to reinstall, I don't encounter the same non-boot issue. Or, is it simply a matter of installing patch KB4058258 before the 1709 update self-initiates? Again, much appreciated to those who are sticking around and helping the rest where this issue continues to persist.
-
Anonymous
2018-02-01T21:11:39+00:00 Meltdown is not on AMD but kb4056892 made some of them to crash then why it was so?