This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
Thank you, but I reinstalled from sratch. Fortunately I have downloaded the iso file of 2017. november build, and installed a fresh windows, then updated until the buggy update. Then turned update off for some weeks, and after some weeks, when I read some forums, that the update bug was eliminated turned the update back and updated the op. sys.
If you're still on build 1607, then I would now allow Windows Update to update automatically to 1709 . It should (in theory) work for you, because Microsoft have now fixed the AMD CPU bug (as of 31 January). Windows update will install version 1709 and then subsequently install the latest cumulative update from January 31, 2018—KB4058258 (OS Build 16299.214). It should not attempt to install the earlier cumulative update. I think (hope) this should work for you. My HP Pavilion DV7-2110sa (AMD Turion X2) is running fine with KB4058258.
Just an fyi..
Have seen quite a few devices(AMD and Intel chipset) where a WU installed 1709 feature update the subsequent build update taking a stage route:
16299.125 or earlier to 16299.192 then to 16299.214
(in these cases skipping 16299.158 and 16299.201)
i.e. the route to 16299.214 may not be direct.
In some cases, using the Catalog stand-alone 16299.214 is the only direct route from 16299.125 or earlier to 16299.214.
But as always due to device and software compatibility variation - ymmv.
So just for my understanding, you're suggesting that I install KB4057142 while currently using the Win 10 1607 build, then attempt to re-install build 1709 and hopefully that will eliminate the boot failure issue(s)?
yes, that is my idea, I hope it solve the issue for you.
Good to hear you have resolved the boot issue with your machine. But I'm curious, if you had booting troubles, how were you able to install and run the "Show/Hide Updates" utility? I can run this while on build 1607 because the system boots fine. That wouldn't have worked though using build 1709 (non-bootable). But based on earlier discussions above, perhaps I need to find and uninstall KB4056892 since it is not part of build 1709. Then, install patch KB4057142. THEN, attempt to re-install 1709 and hope for the best.
Well I'm waving the white flag I think. I see no record of KB4056892 ever being attempted to be installed. KB4057142 was already recently installed successfully. I'm going to remove all video hardware from device manager and delete the corresponding drivers. Will try 1709 one last time if it is still unsuccessful, then I will need to find a way to block it from installing when I roll back to 1607.
Consequently, I did start another topic since now I believe my direct issue is pertaining to this thread less and less. :(
In my personal experience, Windows 10 starts to get sluggish on anything older than say six years, especially a laptop, as those are often made to just run well with the operating system at the time of their release but are under powered for anything newer which always tends to use more resources. At the very beginning with a clean install it is a little sluggish (hard drive being indexed, updates downloading), then ok for some time, and eventually just always sluggish (especially if you only use it occasionally, then it spends most of its time on massive feature updates downloading, preparing to install updates, scanning for malware, who knows). On such older hardware Linux mint remains responsive and if you boot up your computer and do nothing, the CPU and hard drive usage is actually zero! Windows 10 runs like a dream on a newer machine with an SSD hard drive and 6+ GB RAM and that is used frequently. But on older hardware (and you have to decide for yourself what that means), I would use Windows only if you need to run software that only runs under Windows. On such older systems you need stability over feature updates that you rarely use.
let's see if there is a query you can do with it which would be equivalent to winver...
Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion" | fl CurrentBuildNumber, UBR
I don't know who to credit for this method. Nor can I really show a specific search that caused me to find it and decide it is about as simple and accurate as we have. Another benefit of it would be that you don't need to use PowerShell to take advantage of information it provides; e.g. just use regedit to drill down to the same registry values.
