After installation of KB4056892 boot failure, after roll-back error 0x800f0845

Question

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?

Answer 1

I have to do some more digging but on a hunch, maybe secure boot could be causing some errors. I noticed while getting it to boot CSM keys where being unloaded. 

I could be wrong but at least its something to take a peak at.

Answer 2

I have the same issue with an Intel i7 in a Gigabyte motherboard. After the update and the machine boots it constantly throws an error. I can get to the command prompt but everything is locked. I bought a new hard drive and re-installed Windows 10 on it. When Windows Update installed the latest updates (15th Feb 2018) it all started again. So it's definitely the updates. If I re-install and block updates the problem is not present.

Answer 3

I am have encountered the same error, I installed the link for troubleshooting but it can't seem to fix it. I also followed this - any idea how to fix it

If you receive Windows Update error 0x80073712 or 80073712, it means that a file needed by Windows Update is damaged or missing. Windows has troubleshooting tools that can help you address this problem. Follow the steps below to use these tools.

Method 1: Run the Windows Update troubleshooter

1. Open the Windows Update troubleshooter by swiping in from the right edge of the screen, tapping Search (or if you're using a mouse, pointing to the upper-right corner of the screen, moving the mouse pointer down, and then clicking Search), entering Troubleshooting in the search box, tapping or clicking Settings, and then tapping or clicking Troubleshooting. UnderSystem and Security, tap or click Fix problems with Windows Update.
2. Run the troubleshooter, then open Windows Update and try to install the update again.

Method 2: Run the DISM tool

1. Swipe in from the right edge of the screen, and then tap Search.

(If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.) 2. Enter command prompt in the search box. 3. In the list of results, swipe down on or right-click Command Prompt, and then tap or click Run as administrator. 4. In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:

*DISM.exe /Online /Cleanup-image /Scanhealth*

*DISM.exe /Online /Cleanup-image /Restorehealth*

5. To close the Administrator: Command prompt window, type Exit, and then press Enter.
6. Run Windows Update again.

Method 3: Refresh your PC

• For information about how to do this, go to How to restore, refresh, or reset your PC.

~

80070003

Click Start (Press “Windows Key + Q” to open Charms Bar.)

Type: cmd

Right click on cmd in start menu and select 'Run as Administrator'

Type: net stop wuauserv

Hit Enter

Type: ren c:\windows\SoftwareDistribution softwaredistribution.old

Hit Enter

Type: net start wuauserv

Hit Enter

Type: exit

Hit Enter

Restart once it's finished running and see if the return code still appears when checking for updates.

Attempt to download updates

Answer 4

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.