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.
KB4056892 patch has failed to install twice on my desktop Dell Inspiron 531. (AMD Athlon 64 X2 Dual Core Processor 5000+ 2.60 GHz) It hangs on Windows Logo at reboot. No drive activity, no keyboard or mouse input. I have to do system restore to get the PC running again.
I have run Windows Show/Hide tool in attempt to pause installation of this update. Yet to be seen if it actually worked. http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab
Same problem on an older Athlon X2.
On startup I pressed f8 while booting and it would automatically roll back the update.... then promptly try to reinstall the update and back to square one.
Only temporary fix to this is to either disable or defer the updates. I haven't tried disabling virtualization as I actually need that for virtualbox. I guess I could always reverse my usage. Put linux on this machine, and put Windows 10 in a virtual machine :P.
I have the same problem with my old Athlon X2 4850e, Windows 10 pro, used as a file server. I went through the install the update, no boot, failed to install, remove the process and start over again numerous times. I have paused updates to be able to use the computer. I wanted to post here just to add my name to the list of people having this issue with this update. My 3 Intel computers updated without issue.
Tested now on a Windows 10 Home Fall Creators Update:
while the KB4056892 was downloading in Windows Update, I managed with the Hide/Show troubleshooter to hide the update, then restarted the pc.
Now the KB4056892 is not installed and is ignored by Windows Update!
I was finally successful in hiding/blocking KB4056892 using Hide/Show Troubleshooter. The key, as you pointed out, seems to have been restarting the PC after hiding it. I have Windows Update Service enabled again and (so far) it hasn’t tried to sneak it back onboard!
Gianni-you were correct in that the WUHIDESHOW.DIAGCAB Hide Show tool requires the Windows Update Service to be running (an internet connection) in order to show the updates on the list.
But unfortunately, even though I successfully "hid" the 2018 Cumulative Update KB4056892", and it showed up in the hide/show tool as being hidden, Windows Update just charged ahead anyhow and began downloading, got to 100% download, and then began installing this update on my system until I quickly disabled windows update service again. Maybe your results are different. Or maybe (just guessing, I don't know) it's because this update is considered an "emergency" update and Win10 forces it to download and install.
So for now, I think my only recourse is to keep windows update service disabled and hope for a fix from MS.
