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.
I was hoping the Hide/Show troubleshooter WUHIDESHOW.DIAGCAB tool downloaded at: https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window
would help, but when I run it it unfortunately shows no updates to hide or show.
So for now, I guess I will have to leave my Windows Update Service stopped & disabled and hope for a fix.
I suspect that the Hide/Show tool relies on the service you have stopped.
I was hoping the Hide/Show troubleshooter WUHIDESHOW.DIAGCAB tool downloaded at: https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window
would help, but when I run it it unfortunately shows no updates to hide or show.
So for now, I guess I will have to leave my Windows Update Service stopped & disabled and hope for a fix.
I suspect that the Hide/Show tool relies on the service you have stopped.
Good thought--thanks-maybe that is the cause (?windows update service being disabled?) why hide/show tool doesn't see the update?! But not sure how to properly "time" re-enabling my Windows Update service since Windows will then immediately start installing the update, after which I will be unable to do a restart or boot the computer. A "Catch 22 situation." I don't know, but I "assume" (never assume) that the hide/show tool has to be used to hide the update BEFORE the update is installed.
I "assume" (never assume) that the hide/show tool has to be used to hide the update BEFORE the update is installed.
Yes, BEFORE the update is installed!
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.
I did not ask this question. This is nothing to do with me.
