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.
My HP Pavilion Slimline desktop PC with AMD Athlon processor gets into an unbootable state following the KB4056892 update Windows 10. I did a system restore and disabled windows updates. Microsoft claims that the update would be paused for my computer, but after I resumed windows updates, KB4056892 was pushed to my computer with the same unbootable results. I had to system restore and disabled updates again. Will I ever be able to resume windows updates?
![](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(137.6, 51%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
DISM is pretty quick, if it gave problems, it's probably good you went to a clean install (I prefer a clean installed OS). If you continue to have issues, consider looking at a hardware issue.
CTRL-C or closing the command prompt window, would have probably ended the command, There is no reason (I can think of) to wait an hour for a proper 'dism' command to complete.
Edit: Please post back and start a new question in MC, if KB4056892 (or the ability to hide it) comes back, as you recently clean installed.... BTW what kind of processor are you running (Pls answer in new question, if necessary)...
Good you got that to work. When I tried dism, I just got an endless moving bar. After an hour or two, I shut it off and moved on to a clean install. With the clean install they don't try to install the .192 build. Getting everything back together took me some time. But well worth it.
I fixed mine by disabling Windows Update. Services.msc, stop the windows update services, set it to disabled and set the auto recovery to none. After that, it rebooted and didn't download the failed update again.
I had same problem. Once the update has been downloaded, it seems nothing will stop W10 from attempting the update. There may be a way, but I never got any of the suggestions to work. In end, I downloaded a clean Win 10 iso from MS and did a clean install. THis got us back working withing 8 hrs after 3 weeks of broken Windows 10. Really hard to believe that MS could screw up so badly.
