That's a real shame that the patch didn't create a Restore Point !
That's bad, really bad, Microsoft folks.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
That's a real shame that the patch didn't create a Restore Point !
That's bad, really bad, Microsoft folks.
I have a A10 and a A8 processor the system loads but you cant do anything I uninstalled this update now everything works again... hid update for 30 days ..why would you put out a update that wasnt needed for AMD ! Amd has stated these attacks cannot be done on there CPUS
Are Microsoft accepting any feedback for Windows 7 Pro systems? I have an Athlon 64 X2 6000+ CPU in an HP workstation, got BSOD after patching with KB4056894 (auto-restart disabled); booted into System Restore, reverted to state immediately prior to patch installation, then went into Windows Updates settings and hid the update. System Event log shows update failure error 0x800f0816. I'm ecstatic I didn't install WX on this (reliable) dinosaur.
This computer wasn't slated for replacement until 2020- in fact, I was about to upgrade the SSD to a larger faster one, but now I'm wondering if this patch wasn't a gambit to drive up flagging sales in the desktop world, and I'll be swimming upstream.
I'd be happy to post the technical details (sans commentary) wherever it's most useful to Microsoft, just point me.
Thanks for your time
Kirk
I also have this issue issue...
16299.125 works fine but once I update to 16299.192, while it installs fine it's once you reboot the PC it gets to the Windows 10 loading screen and simply freezes and I have to hard power off and back on and it does the same thing but on the third boot it goes into automatic repair mode and returns Windows 10 back to 16299.125 and things work again but not long after it wants to install 16299.192 again which obviously won't work and will repeat the same process.
my fix... I installed Mint Linux (v18.3 Cinnamon x64) for the time being and I might consider staying with Mint Linux. but at least it's nice to know that Windows 10 will likely be fixed in case I never need to go back to it. but one thing I like about Mint Linux is that the touchpad on the laptop actually works with scrolling web pages etc (like on the right side of the touchpad) which does not work in Windows 10. but outside of that Windows 10 runs great outside of this major issue. but thankfully I have a CloneZilla image of 16299.125 which I can simply restore if I want to go back to Windows 10 once they sort this issue out and then update and that should be that.
side note: even clean installing Windows 10 16299.15 and then using the 600MB update file to bring it to build 16299.192 has this exact same freezing issue at the Windows 10 loading screen.
p.s. the above info is for a HP DV5-1002nr Laptop (10 years old) which has a AMD CPU (i.e. AMD Turion 64 X2 RM-70 @ 2Ghz). my main computer works fine with the 16299.192 update which has Intel i3-2120 CPU.
Thanks, it seems I was able to log-in to the feedback hub with my liveid, but unfortunately the feedback app just shows working animation and nothing more. I will try later, but it doesn't seem like robust feedback platform to me :)