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

Anonymous

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.

0 comments

494 answers

Anonymous

2018-01-10T17:26:22+00:00

I followed the instructions here to disable the KB update

http://www.thewindowsclub.com/block-unwanted-windows-updates-in-windows-10
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-10T16:32:26+00:00

This seems to have happened to me on Saturday, unable to boot or restore. Runs Ubuntu Live disc so I was able to confirm all parts seem to be working. Saved my files to my 2nd drive using Ubuntu. I have a newer(not new, but not as old) AMD processor, I believe it is AMD A10-7800 Quad-core 3.5GHz (3.9GHz Turbo) Processor with AMD R7 graphics or very near that. I noticed a thumb drive was not recognized on Saturday and rebooted only to get stuck on OEM(ASUS) auto-repair screens. System restore point was from 1pm that day and does not fix the issue so I assume the patch was auto-installed before then. I'd say this chipset is about 5 or a little more years old as I bought it less than 3 years ago. Made a System Repair Disc off of an Intel 64 machine, but it doesn't seem to boot properly. I will attempt a fresh Win 10 install tonight, hopefully that does the trick. I wanted to post because most of the machines I have heard about had much older chipsets than mine. Is this affecting more machines than earlier reported?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-10T16:14:58+00:00

It doesn't brick it but counting on Home or Pro version comes slightly different work around.

Windows stops dead on logo with no animation. After 2 or 3 reboots Windows start repair. Counting on options it may roll back or say it must repair. Repair will replace old window install. But if you go to advanced and check for a restore point you can restore back.

After that step you must stop the update. Counting on Windows home or Pro you have different options

Home does not have option to delay or hide but you can disable Windows update in the services. This must be done before Windows attempts to upgrade again. If windows does a repair then it will turn the service back on so check it again.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-10T15:43:29+00:00

This happened to me last night and as you said i couldnt system restore but I did manage to reinstall windows 10 without losing personal info
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-10T15:18:43+00:00

It appears my component store is corrupted

But getting a source for dism to use for the repair seem out of my reach

Can you connect to internet from repair mode command prompt ??
Was this answer helpful?

0 comments No comments