Microsoft apparently reinstates Meltdown/Spectre patches for some AMD processors

[woodyDa Boss]

Of course, predictably, nobody’s saying which ones are now back on the patch list. Post coming in Computerworld. Thx @mrbrian
[See the full post at: Microsoft apparently reinstates Meltdown/Spectre patches for some AMD processors]

6 users thanked author for this post.

Elly,

JDeC,

HiFlyer,

AJNorth,

Tiernan,

MrBrian

[radosuafAskWoody Lounger]

Anybody got this?

MSI H110 PC MATE * Intel Core i5-6402P * 2 x 8 GB Corsair Vengeance LPX DDR4 2133 MHz * Aorus Radeon RX 570 4GB * Samsung 840 EVO 250GB SSD * Western Digital Blue 1TB HDD * Seagate Barracuda 1TB HDD * DVD RW Lite-ON iHAS 124 * Creative X-Fi XtremeGamer PCI * Windows 10 Pro 1809 64-bit

1 user thanked author for this post.

BobbyB

[woodyDa Boss]

Oh no. Not another one….

Wait. Is that the October 3 driver? Something’s fishy.

[radosuafAskWoody Lounger]

Description in WU says: “Yesterday”. Catalog says Oct 3rd, 2016…

MSI H110 PC MATE * Intel Core i5-6402P * 2 x 8 GB Corsair Vengeance LPX DDR4 2133 MHz * Aorus Radeon RX 570 4GB * Samsung 840 EVO 250GB SSD * Western Digital Blue 1TB HDD * Seagate Barracuda 1TB HDD * DVD RW Lite-ON iHAS 124 * Creative X-Fi XtremeGamer PCI * Windows 10 Pro 1809 64-bit

[FakeNinjaAskWoody Lounger]

What do you mean by “another one”? What are these strange intel updates? I also have a few of these in my Windows Update.

[anonymous]

Yep I got it yesterday and hid it.

[BobbyBAskWoody Lounger]

Not yet, and not hidden either; Just did a check, got about 588.1Mb’s (inc Office 2010) of updates all dated this year alas 🙁

[radosuafAskWoody Lounger]

I got 7 updates for my Office 2007 yesterday :).

MSI H110 PC MATE * Intel Core i5-6402P * 2 x 8 GB Corsair Vengeance LPX DDR4 2133 MHz * Aorus Radeon RX 570 4GB * Samsung 840 EVO 250GB SSD * Western Digital Blue 1TB HDD * Seagate Barracuda 1TB HDD * DVD RW Lite-ON iHAS 124 * Creative X-Fi XtremeGamer PCI * Windows 10 Pro 1809 64-bit

[KarlstonAskWoody Plus]

Yep, here too.

It’s a driver offered by Windows Update so it gets the usual treatment… unchecked and hidden.

Grunble time… here in Australia (and probably lots of other countries) that date is interpreted as 10th of March (dd/mm/yyyy), not October 3rd (mm/dd/yyyy).  And they want us to use Windows 10 S to educate our children… spleen vented… 🙂

Hanlon's Razor: Never attribute to malice that which can be adequately explained by stupidity.

1 user thanked author for this post.

AJNorth

[bhenAskWoody Lounger]

As someone who had to deal with that update popping up on a W10 recently… I dislike that ‘update’ immensely. The people on 7/8.1 probably have an easier time dealing with that than people on 10.

I probably made a mistake or two in the process, but I eventually just fresh started the computer and haven’t had it pop up in the weeks since then. I’m still sorta left to wonder why that update arrived for me a year after it really got attention on here and other places.

It’s not like getting error 0x80070643 on KB4054517 causes it to start fetching that computer-wrecking junk out of confusion? It was something else in the process, I’m sure.

[SeffAskWoody Plus]

I’m being offered KB4056894 again on my AMD Phenom II machine, this time it’s checked.

[anonymous]

Me too on my AMD FX. I installed it (after creating a restore point to prevent havoc) and everything is ok (as fas as now)

[bytemeAskWoody Plus]

I’m being offered KB4056894 (checked) on my Dell desktop with an Intel processor and an AMD Radeon HD 7570 video card.

[SeffAskWoody Plus]

I’m also being offered that update on my Intel machine with an AMD Radeon graphics card, but then I always have been – it was never withdrawn unlike on my AMD Phenom II machine.

[PKCanoDa Boss]

On 1/10/2018 Microsoft released Security-only update KB4073576 for:

Unbootable state for AMD devices in Windows 8.1 and Windows Server 2012 R2

Summary

An update is available to fix the following issue that occurs after you install January 3, 2018—KB4056898 (Security-only update) or January 8, 2018—KB4056895 (Monthly Rollup):

AMD devices fall into an unbootable state.

See The Microsoft Support page.

This update has been added to the Group B Knowledge Base AKB2000003.

2 users thanked author for this post.

AJNorth,

amraybt

[anonymous]

I have an Intel CPU and AMD video card on Windows 7. Still haven’t received any security patches for January via Windows Update. Just checked again now, nothing shows up.

[anonymous]

Installed the recent update (KB4056894) on an old AMD C-50 and it booted up fine. I wasn’t too concerned about any performance issues as it’s not the quickest CPU but I was surprised the machine didn’t throw up upon reboot.

[anonymous]

Dell desktop with Win 7 Intel i7 processor and AMD Radeon HD 7770 video card … I’m being offered KB4056894 (checked) when I run windows update.

Not running the update yet, but I’m confused as to why a GPU would be affected by the patch?  CPU could make sense as well a combined APU, but the GPU?

[anonymous]

Just read the following, as AMD looks to be releasing some CPU patches:

https://www.theverge.com/2018/1/11/16880922/amd-spectre-firmware-updates-ryzen-epyc

AMD is also revealing that its Radeon GPU architecture isn’t impacted by Meltdown or Spectre, simply because those GPUs “do not use speculative execution and thus are not susceptible to these threats.”

2 users thanked author for this post.

The Surfing Pensioner,

MrBrian

[anonymous]

Windows Updates didn’t show up anything but the Flash player update on the Intel boxes here. Looks like they called off Patch Tuesday for smart folks… Don’t touch the button, don’t touch nuttin’, right?

[PKCanoDa Boss]

If your anti-virus program has not set the ALLOW Regkey to indicate it is compatible with the updates, the Rollup and the .NET patches will not show up in Windows Update.

January Rollups are causing BSODs in computers with certain AMD processors. Microsoft has blocked the Rollups for those computers.

[anonymous]

It’s all Microsoft, no third-party stuff… The story is that folks better don’t touch the check-for-updates button and let Microsoft decide when it’s time to deploy those patches. Manually checking for updates triggers the update system to deliver each and everything, and the kitchen sink…

[GeoAskWoody Plus]

This time 894 was checked.  Didn`t update yet.  Sempron 145.

[MrBrianAskWoody_MVP]

From AMD’s statement (my bolding) “Microsoft is distributing patches for the majority of AMD systems now. We are working closely with them to correct an issue that paused the distribution of patches for some older AMD processors (AMD Opteron, Athlon and AMD Turion X2 Ultra families) earlier this week. We expect this issue to be corrected shortly and Microsoft should resume updates for these older processors by next week.”

1 user thanked author for this post.

Jan K.

[anonymous]

I just got 894 again.  Win 7X64, Sempron 145, I use Microsoft Security essentials.  Didn`t  update, waiting for MS- defcon to change before updating.

[anonymous]

What is (Windows 10 1607) KB4049411 a Creator’s/Feature update related patch and not the Spectre patch for AMD systems?

[PKCanoDa Boss]

KB4049011 is the servicing stack for 1607

[anonymous]

Is there something wrong with the registration on this site? I registered two days ago but I have yet to receive a confirmation email along with a password. Any help would be appreciated.

[KirstyDa Boss]

No specific fault with registration that we know of; however, occasional problems can occur with emails (such as spam filters). As you did not mention your user name, I suggest you email Woody, who should be able to set/reset your password, to get you going.

If you choose to reply with your username, we can check if the account is showing, as a first step (and it shouldn’t need to be published here!). Hopefully you’re on board without too much delay 🙂

[anonymous]

My username was Hopper15. Sorry I forgot to include it.

[PKCanoDa Boss]

Your user name is on the system. Woody has been notified and should send a password to your registered email address before too long.

1 user thanked author for this post.

woody

[anonymous]

Just when you thought it was safe to go back in the water –

https://www.reuters.com/article/us-cyber-security-intel/intel-says-patches-can-cause-reboot-problems-in-old-chips-idUSKBN1F101X

 

3 users thanked author for this post.

Elly,

HiFlyer,

woody

[woodyDa Boss]

Just posted this on Computerworld.

https://www.computerworld.com/article/3247788/computer-hardware/intel-says-new-firmware-patches-trigger-reboots-in-haswell-and-broadwell-systems.html

I really feel bad for the folks who bought Surface Pro 2 machines.

1 user thanked author for this post.

Elly

[PKCanoDa Boss]

I feel truly sorry for “Joe User” out there (and there are millions), who has no idea about Registry keys or microcode updates or how to recover from a BSOD except by paying his local computer shop big bucks, and who probably has Windows Update on Automatic.

And my latest processor is a 2013 Haswell….

5 users thanked author for this post.

Elly,

HiFlyer,

woody,

Jan K.,

grayslady

[SailorAskWoody Lounger]

I got update KB4023057 for my Windows 10 1703.

[anonymous]

I tried replying to @radosuaf but got “Error establishing a database connection”.

These Intel patches in Windows Update seem endless even when blocked. I had one marked “important” last month that I ignored on advice from the folks here and one optional called “Ports” recently. I unchecked both and they disappeared eventually. I usually hide them but they just come back.

It makes me wonder how many people get stuck with these random patches due to having WU set to automatic.

[anonymous]

My dad’s (AMD processor) computer has tanked after the recent update this week.  Has anyone seen a solution for those machines?  Thanks!

[PKCanoDa Boss]

You may be able to boot from your Rescue Disk, go to System Restore, and restore to a point before the update.

[MrBrianAskWoody_MVP]

Windows 7 has a fixed update available.

5 users thanked author for this post.

Elly,

woody,

Woody posting as an MVP,

DrBonzo,

abbodi86

[PKCanoDa Boss]

On 1/12/2018 Microsoft released Security-only update KB4073578 for:

Unbootable state for AMD devices in Windows 7 SP1 and Windows Server 2008 R2 SP1

Summary

An update is available to fix the following issue that occurs after you install January 3, 2018—KB4056897 (Security-only update) or January 4, 2018—KB4056894 (Monthly Rollup):

AMD devices fall into an unbootable state.

See Microsoft Support page

This update has been added to the Group B Knowledge Base AKB2000003.

2 users thanked author for this post.

HiFlyer,

DrBonzo

[DrBonzoAskWoody Lounger]

Is this – KB4078578 – an additional security only update or a replacement for KB4056897?

I don’t believe I have any AMD chips in my computer, but there have been a couple reports of BSOD on Intel machines, so I’m wondering if I should install this new patch even though it’s strongly implied by MS that it’s for AMD chips.

1 user thanked author for this post.

HiFlyer

[anonymous]

Sorry for be being dense here, but how do you apply a patch to a computer that’s in an unbootable state?

1 user thanked author for this post.

woody

[MrBrianAskWoody_MVP]

I think Microsoft’s intention is that affected users remove the bad update via methods already discussed, and then install the new update.

[anonymous]

Microsoft released two updates to fix the bug with older AMD CPUs, KB4073578 for Windows 7 and KB4073576 for Windows 8.1, but… nothing for Windows 10!

So the bug is still present in Windows 10, and for the bad… Windows Update started to offering the Windows 10 cumulative update again in the affected AMD machines, and after reboot Windows stuck in Windows logo again! :S

4 users thanked author for this post.

satrow,

HiFlyer,

woody,

Woody posting as an MVP

[bjmAskWoody Lounger]

anonymous wrote:

What is (Windows 10 1607) KB4049411 a Creator’s/Feature update related patch and not the Spectre patch for AMD systems?

same question:  What is KB4049411 on W10 1607

[PKCanoDa Boss]

You have a typo in the number
KB4049011 is the servicing stack.

[anonymous]

I’m an the quoted anonymous person. Having rechecked wushowhide it does indeed list Update for Windows 10 Version 1607 for x64-based systems (KB4049411).

The update number you for which have provided a correction is a November 2017 update described on the Windows update catalog site. Unfortunately there is no KB4049411 for download available on the update catalog site, therefore it does looks like another suspicious attempt at Microsoft ‘s shenanigans.

[PKCanoDa Boss]

You are so right about 4049411 not being listed in the Catalog or on the Software Update Services page. For some reason I had 4049011 (servicing stack) listed in my notes. ???

[anonymous]

I do apologize if that was gruff in tone, it looks as if somebody might have to install the thing or figure out how to separately download this package.

According to more KB4049411 search results perhaps it is another way to get users to fumble and upgrade to the Version 1709 (Green Screen of Death Edition). Most of the results show that package to be related to installation failure error messages starting last November.

1 user thanked author for this post.

PKCano

[Hopper15AskWoody Lounger]

anonymous wrote:

Microsoft released two updates to fix the bug with older AMD CPUs, KB4073578 for Windows 7 and KB4073576 for Windows 8.1, but… nothing for Windows 10! So the bug is still present in Windows 10, and for the bad… Windows Update started to offering the Windows 10 cumulative update again in the affected AMD machines, and after reboot Windows stuck in Windows logo again! :S

I wonder if that’s going to be offered this Tuesday via WU.

[anonymous]

Does anyone know if bsod is happening with AMD e-350 cpus? I have Win 7 Home Premium

[Author]

Posts