New
#10
The fix by MS to block the update for older AMD CPUs didn't work for me yesterday - see KB4056892 Still Received and Bricked an Old AMD PC
Windows OS security update block for some AMD based devices
-
-
New #11
I've just checked and that update successfully installed on the 10th, only just got this machine and it's the first AMD I've had my other machines have been Intel.
It's an HP Envy x360 Convertible. Mind you I've done a check and it seems there are updates from HP for it 3 are recommended but I'm a bit nervous of doing them as one is a BIOS one and there's one for UEFI for AMD, I think I've got those letters right you lot probably know better than me.
The check said there were 6 updates 3 recommended and 3 optional.
-
New #12
Performance impact of spectre and meltdown:
Understanding the performance impact of Spectre and Meltdown mitigations on Windows Systems Microsoft Secure
-
-
New #14
-
New #15
Not sure where MS is at with that kb, but I’m quite sure they would not release it again unless it was able to install. I noticed you two use 3rd party AV. Do you know about the fact that an AV has to be compatible for that kb? It needs to be able to change certain Registry keys in order for the kb to install successfully. More about that in this thread:
Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192 - Windows 10 Forums
Also, the term “bricked” means to render a device absolutely useless. e.g. A BIOS flash or a firmware update gone bad, therefore not able to install anything thereafter rendering it useless. Attempting to install the kb may have borked or broke your system, but not bricked it. My thoughts is that it frightens people when they see that term is all.
-
New #16
-
New #17
@Tony K
My PC isn't bricked - it just refuses to boot after KB4056892 is installed.
Updating Windows Defender applies the necessary Registry fix, by the way, paving the way for KB4056892 to install,
Restored it to an earlier build (16299.19)) via Macrium and it worked perfectly until I allowed KB4056892 to install, when the whole cycle starts again. So, the version of KB4056892 that's currently available still stops some AMD PCs from booting.
I did allow some updates through, so presently the PC is at OS Build 16299.125. I've made another image of that and have set
Set Feature update delay 365 days
Quality update delay 30 days
Network METERED
That'll stop it!
-
New #18
That should work - else use the method in this Tutorial which I've used to block the single offending update Hide or Show Windows Updates in Windows 10@Tony K
My PC isn't bricked - it just refuses to boot after KB4056892 is installed. Restored it to an earlier build (16299.19)) via Macrium and it worked perfectly until I allowed KB4056892 to install, when the whole cycle starts again. So, the version of KB4056892 that's currently available still stops some AMD PCs from booting.
I did allow some updates through, so presently the PC is at OS Build 16299.125. I've made another image of that and have set
Set Feature update delay 365 days
Quality update delay 30 days
Network METERED
That'll stop it!
-
-
New #19
Understandably tension are high, especially with this CPU fiasco going on. Then updating fiascos. Believe me, I'm only attempting to be helpful by pointing out some possibilities is all. If the kb doesn't install on some AMDs, that's the first I've heard of it. Happy that you pointed that out.@Tony K
My PC isn't bricked - it just refuses to boot after KB4056892 is installed.
Updating Windows Defender applies the necessary Registry fix, by the way, paving the way for KB4056892 to install,
Restored it to an earlier build (16299.19)) via Macrium and it worked perfectly until I allowed KB4056892 to install, when the whole cycle starts again. So, the version of KB4056892 that's currently available still stops some AMD PCs from booting.
I did allow some updates through, so presently the PC is at OS Build 16299.125. I've made another image of that and have set
Set Feature update delay 365 days
Quality update delay 30 days
Network METERED
That'll stop it!
Also, I've heard that Macrium Reflect was having issues as well. Don't use it so can't help there.
So far as the term brick; It actually was introduced by means of unlocking cell phones with firmware, for here in the U.S. our phones were locked. When a firmware hack went bad it rendered the phone useless, so therefore called a brick. So the term is rather scary here.
Quote
Related Discussions
