Microsoft Pauses Rollout of Spectre and Meltdown Patches To AMD Systems (betanews.com)

← Back to Stories (view on slashdot.org)

Microsoft Pauses Rollout of Spectre and Meltdown Patches To AMD Systems (betanews.com)

Posted by msmash on Tuesday January 9, 2018 @02:44AM from the hold-on dept.

Microsoft is suspending patches to guard against Meltdown and Spectre security threats for computers running AMD chipsets after complaints by AMD customers that the software updates froze their machines. From a report: The company is blaming AMD's failure to comply with "the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown." There's no word on when the patches will be fixed, but Microsoft says that it is working with AMD to address the problem.

100 comments

Min score:

Reason:

Sort:

Maybe they should test on real hardware by HalAtWork · 2018-01-09 02:50 · Score: 4, Insightful

It seems like MS could have some sort of lab with various configurations of relatively recent hardware where they can test updates they deem ready for production.

--
Twinstiq, game news
1. Re:Maybe they should test on real hardware by mwvdlee · 2018-01-09 02:58 · Score: 1
  
  It seems like a company such as MS would benefit greatly from having a unique hardware configuration for each employee.
  It might be a PITA for their deployment systems but then again, they're selling those too!
  
  --
  Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
2. Re:Maybe they should test on real hardware by HalAtWork · 2018-01-09 03:00 · Score: 1
  
  Speaking to users with multiple configs I'm surprised the insiders did not help catch this either
  
  --
  Twinstiq, game news
3. Re:Maybe they should test on real hardware by thegarbz · 2018-01-09 03:40 · Score: 4, Funny
  
  It seems like MS could have some sort of lab with various configurations of relatively recent hardware where they can test updates they deem ready for production.
  They did. Today. Their beta testers found a bug and the rollout stopped. Just because their lab is the size of a planet doesn't change the fact that they are testing their high quality software releases.
4. Re:Maybe they should test on real hardware by HalAtWork · 2018-01-09 04:07 · Score: 1
  
  I was under the impression KB4056892 was a finalized patch that was officially issued?
  
  --
  Twinstiq, game news
5. Re:Maybe they should test on real hardware by Anonymous Coward · 2018-01-09 04:34 · Score: 0
  
  That wooshing noise wasn't the space x satellite passing by, it was the joke you missed.
6. Re:Maybe they should test on real hardware by HalAtWork · 2018-01-09 04:54 · Score: 1
  
  OIC, good one.
  
  --
  Twinstiq, game news
7. Re:Maybe they should test on real hardware by Aighearach · 2018-01-09 06:47 · Score: 0
  
  Or at least, the whooshing sound you were standing there making while insisting that something was funny.
8. Re:Maybe they should test on real hardware by Anonymous Coward · 2018-01-09 08:27 · Score: 0
  
  The only sound I hear right now is the full throttle fans from my ex. workmates( unknown beta tester) windows 7 AMD computer, witch i'm trying to restore after the update has destroyed it. Hi has already bought a new laptop so wintel +1
9. Re:Maybe they should test on real hardware by Anonymous Coward · 2018-01-09 08:41 · Score: 0
  
  Must be some good blue Kool-Aid
10. Re:Maybe they should test on real hardware by Anonymous Coward · 2018-01-09 15:43 · Score: 0
  
  OOOOH! BUURRNN!
11. Re: Maybe they should test on real hardware by Anonymous Coward · 2018-01-10 05:28 · Score: 0
  
  Especially since it is not AMD at fault, it is Intel.
Why Meldown? by 110010001000 · 2018-01-09 02:51 · Score: 2, Insightful

The only commercially available chips susceptible to Meltdown are Intel chips. Why is a Meltdown patch being pused to AMD systems? They aren't affected.
1. Re:Why Meldown? by Scarred+Intellect · 2018-01-09 02:56 · Score: 2
  
  The only commercially available chips susceptible to Meltdown are Intel chips. Why is a Meltdown patch being pused to AMD systems? They aren't affected.
  Incompetence.
2. Re:Why Meldown? by 110010001000 · 2018-01-09 02:58 · Score: 1
  
  Ah makes sense, seems to be contagious! Microsoft and Intel. What a team.
3. Re:Why Meldown? by Anonymous Coward · 2018-01-09 02:58 · Score: 0
  
  The only commercially available chips susceptible to Meltdown are Intel chips. Why is a Meltdown patch being pused to AMD systems? They aren't affected.
  Yeah, well they are now pal!
  Should have bought an Intel system to begin with, then we wouldn't have to rough you up like this!
4. Re:Why Meldown? by Anonymous Coward · 2018-01-09 02:58 · Score: 0
  
  Incompetence
  Funny, I was going to say "sucking Intels cock"
5. Re: Why Meldown? by Anonymous Coward · 2018-01-09 02:59 · Score: 3, Interesting
  
  On the Linux side, didn't Intel supply much of the Meltdown mitigation, pushing it on all CPUs? And then AMD had to add a patch to exempt their processors?
  Wouldn't be surprised if Intel did a lot of the behind-the-scenes work for Microsoft here, and they just sort of accepted it without sufficient testing.
6. Re:Why Meldown? by Anonymous Coward · 2018-01-09 02:59 · Score: 0
  
  You are essentially proposing having separate versions of Windows for AMD and Intel systems. That is not really a feasible option.
7. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:01 · Score: 0
  
  If only it had been a patch for both Spectre and Meltdown, then it would have made sense.
  Microsoft Pauses Rollout of Spectre and Meltdown Patches To AMD Systems
  Oh.
8. Re:Why Meldown? by 110010001000 · 2018-01-09 03:03 · Score: 2, Informative
  
  I don't get it. Do you think AMD and Intel Windows builds are 100% equivalent? Adorable!
9. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:04 · Score: 0
  
  It's an x86 OS, you expect it to run on any x86, Intel or not.
10. Re:Why Meldown? by 110010001000 · 2018-01-09 03:04 · Score: 1
  
  Yes. The "s" at the end of "patches" indicates there are multiple patches. So why push a fix for Meltdown when AMD chips aren't affected? Very confusing.
11. Re:Why Meldown? by 110010001000 · 2018-01-09 03:05 · Score: 2
  
  Why would an AMD system need to suffer the 30% slowdown, when it is Intel that messed up their architecture? That seems odd.
12. Re: Why Meldown? by 110010001000 · 2018-01-09 03:07 · Score: 1
  
  It really is. So please explain why a fix for Meltdown is needed for AMD systems? They aren't affected by Meltdown.
13. Re:Why Meldown? by TeknoHog · 2018-01-09 03:07 · Score: 4, Informative
  
  In the latest Linux releases, the Meltdown fix has a runtime detection of AMD CPUs, in which case the fix is not activated. I'm sure MS could do something similar if they wanted.
  
  --
  Escher was the first MC and Giger invented the HR department.
14. Re:Why Meldown? by AvitarX · 2018-01-09 03:09 · Score: 1
  
  Because MS keeps only one current version of Windows for x86, so if computers with AMD processors are to be kept current the patch will need to be applied.
  
  --
  Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
15. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:12 · Score: 1
  
  AFAIK, the patch is intended to also partially mitigate Spectre, which does affect AMD processors.
  In any case, stop feeding that troll 110010001000.
16. Re:Why Meldown? by 110010001000 · 2018-01-09 03:15 · Score: 1
  
  What? That doesn't make sense. Are you suggesting the Windows builds for AMD and Intel are binary equivalent?
17. Re:Why Meldown? by hairyfeet · 2018-01-09 03:17 · Score: 4, Interesting
  
  Because its not called "Wintel" for nothing? Remember this is the same company that royally fucked their own flagship OS just to allow good buddy Intel to sell a bunch of garbage 945 chipsets with the "Vista Capable" fiasco, I seriously would not be surprised if Intel picked up the phone and said "You damned well better fuck AMD with this patch as much as we are getting fucked".
  Never let it be said that old Hairy don't give credit where credit is due and in this case the Linux guys have it better as no less than Torvalds himself said that Linux shouldn't treat all CPUs (meaning ARM and AMD) as crap so I seriously doubt Linux users with AMD have a thing to worry about when it comes to the meltdown patches, it'll be us Windows users that will be going to forums and looking for .bat files or reg keys that will kill the meltdown patch on our AMD systems.
  Oh and on a personal note as someone who stuck with AMD FX while everyone was singing the praises of Intel (and still quite happy with my FX-8320e as even my games run buttery smooth at an average of 90 FPS+ while recording gameplay footage) I would be lying if I said it didn't give me a bit of a smile to see Intel getting bit right in the backside after their years of cripple compilers and bribing OEMs, the only thing that could make it more delicious would be if it turns out that Intel chips get a performance hit equal to what the cripple compiler did to AMD systems. Man would that not be some delectable irony?
  
  --
  ACs don't waste your time replying, your posts are never seen by me.
18. Re:Why Meldown? by 110010001000 · 2018-01-09 03:18 · Score: 1
  
  So why didn't they do something similar?
19. Re: Why Meldown? by Anonymous Coward · 2018-01-09 03:21 · Score: 0
  
  My guess is the fix replaces parts or all of the windows kernel. There isn't a specific kernel for intel systems and a separate kernel for AMD systems. They both use the same kernel and likely have code specific for minor differences/issues with each vendors platform. Something in the fix code for intel's issues probably isn't playing well with AMD platforms.
20. Re:Why Meldown? by Onymous+Hero · 2018-01-09 03:25 · Score: 1
  
  After all, what Intel giveth Microsoft taketh away...
21. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:26 · Score: 0
  
  This is likely the case. the fix is likely replacement of all or parts of the windows kernel. There is only one x86 and one x86-64 kernel for windows. AMD needs to work with MS to get the fix code in the kernel deactivated on their platforms just like the fix the pushed to the linux kernel to have that fix code deactivated on AMD platforms.
22. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:27 · Score: 0
  
  Then Intel would pay them less.
23. Re: Why Meldown? by 110010001000 · 2018-01-09 03:29 · Score: 1
  
  "There isn't a specific kernel for intel systems and a separate kernel for AMD systems. They both use the same kernel"
  
  Oh, wow. Really? Binary equivalent kernel for two different processors? Wow!
24. Re:Why Meldown? by 110010001000 · 2018-01-09 03:31 · Score: 1
  
  "There is only one x86 and one x86-64 kernel for windows. AMD needs to work with MS to get the fix code in the kernel deactivated"
  
  Wait, why wasn't this done? They knew about it 6 months ago. Were the engineers too busy? Were they on vacation? Missed their calls from Microsoft?
25. Re:Why Meldown? by haruchai · 2018-01-09 03:32 · Score: 1
  
  "a bunch of garbage 945 chipsets with the "Vista Capable" fiasco"
  It was even worse than that. It was the entry-level 915 which couldn't paint a postage stamp in alternating black & white stripes to save its life.
  
  --
  Pain is merely failure leaving the body
26. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:34 · Score: 0
  
  Yes. The "s" at the end of "patches" indicates there are multiple patches. So why push a fix for Meltdown when AMD chips aren't affected? Very confusing.
  It may just be one "patche" after all.
27. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:47 · Score: 0
  
  The only commercially available chips susceptible to Meltdown are Intel chips. Why is a Meltdown patch being pused to AMD systems? They aren't affected.
  It's a Microsoft-Intel conspiracy.
  AMD stock price down 4% on news Microsoft is pausing rollout of Meltdown fix when AMD chips aren't affected by it.
28. Re:Why Meldown? by Anonymous Coward · 2018-01-09 03:56 · Score: 0
  
  Because Microsoft and Intel have a long and deep monopolistic alliance.
29. Re:Why Meldown? by Antique+Geekmeister · 2018-01-09 04:10 · Score: 1
  
  Maintaining multiple kernels would confuse and potentially invalidate entire suites of compatibility tests. Picking and choosing which kernel to install at update is a risk, as would be testing other software for security, performance, and bugs with distinct runtime kernels running on distinct hardware. The list of issues grows the more you examine software validation for such a critical component as a kernel.
30. Re: Why Meldown? by Anonymous Coward · 2018-01-09 04:11 · Score: 0
  
  They didnâ(TM)t want to.
31. Re:Why Meldown? by Anonymous Coward · 2018-01-09 04:18 · Score: 0
  
  Maybe they know something you don't? I mean it seems likely, as you're a useless twat...
32. Re:Why Meldown? by MachineShedFred · 2018-01-09 04:25 · Score: 1
  
  Really what it comes down to, is that someone will be inconvenienced. Microsoft chose you, instead of themselves - they don't want to maintain two kernels for the same architecture and double all their QA test plans for basically forever.
  So the question you should ask yourself, is why you chose Microsoft.
  
  --
  Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
33. Re:Why Meldown? by danomac · 2018-01-09 04:28 · Score: 1
  
  Intel probably submitted the fix to Microsoft, and Microsoft's wonderful QA/QC team tested this (not likely) and got it ready for distribution.
  If you think about it, wouldn't Intel want all CPUs to have a significant performance penalty and not just their chips?
34. Re: Why Meldown? by Anonymous Coward · 2018-01-09 05:01 · Score: 1
  
  There doesn't have to be, and shouldn't be two different kernels. Intel and AMD both x86 or x86-64 compatible. You get into separate kernels when you are talking different architectures. a separate architecture is the differences between x86, x86-64, and ARM.
  And it is why AMD pushed a fix into the Linux kernel to disable this fix on their processors. The exact same Linux kernel runs on both Intel and AMD CPUs. You dont get a different kernel till you try and run Linux on ARM or some other CPU architecture
35. Re: Why Meldown? by Anonymous Coward · 2018-01-09 05:11 · Score: 0
  
  Probably should also call x86-64 what it truly is. AMD64. AMD invented x86-64. Intel obviously botched their implementation of it.
  Back in the day rather than extending x86 to 64bits, Intel decided to come out with the Itanium processor, a completely new architecture that was 64bit and in no way backwards compatible with x86. While Intel tried to push this processor which ultimately flopped and got nicknamed the Itanic. AMD continued work with x86 and extended it to 64bit. Intel had to swallow their pride and use AMD's implementation in all the processors that we have today.
36. Re: Why Meldown? by Anonymous Coward · 2018-01-09 05:26 · Score: 0
  
  Had Intel had their way, we probably wouldn't have had 64bit on the desktop as soon as we did. Intel's likely plan was to push Itanium in the server market for a few years, then implement it in desktop chips a few years later once the chips became cheaper to make. Instead while Intel was just getting Itanium out in the server market, AMD caught Intel with it's pants down when it released their AMD64 chip to the desktop market and was the 1st to 64bit on the desktop. Intel had no choice but to implement AMD64 on their desktop chips which is what we call x86-64 today.
37. Re: Why Meldown? by Anonymous Coward · 2018-01-09 05:30 · Score: 0
  
  https://en.wikipedia.org/wiki/X86-64#AMD64
38. Re:Why Meldown? by Scarred+Intellect · 2018-01-09 05:48 · Score: 1
  
  That's mostly how I understand it; it's just not practical yet to pick and choose. Better to cover all cases now and figure it out when we have time.
  From my understanding, it's not even incompetence that brought this about in the first place. Lack of foresight more than anything else. No one imagined trying an exploit like these until recently. Unless they have, but have been keeping it quiet, much like the Allies kept the cracking of Enigma quiet...
39. Re: Why Meldown? by Hal_Porter · 2018-01-09 06:00 · Score: 1
  
  It will be a binary equivalent kernel. Different drivers and HALs would get loaded. Actually last time I looked at Windows kernel mode they were moving to a single HAL for all x86 systems.
  If you look at the Linux code it's shared between AMD and Intel though it does check whether CPU features are present, so different code paths run.
  https://github.com/torvalds/li...
  
  --
  echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
40. Re:Why Meldown? by _merlin · 2018-01-09 06:08 · Score: 1
  
  The GMA950 was pretty bad. As well the performance being abysmal (sucking up RAM bandwidth from the already-starved CPU), it would cause kernel panics on and iBook running OSX when an external monitor was connected. They were terrible GPUs.
41. Re:Why Meldown? by Anonymous Coward · 2018-01-09 06:24 · Score: 0
  
  They've been caught doing exactly that in the past. Maybe you should shut the fuck on subjects about which you are demonstrably clueless?
42. Re:Why Meldown? by AvitarX · 2018-01-09 06:25 · Score: 1
  
  Yes, I assume that like Linux Distros, the official kernel is not CPU specific.
  I also assume this because I am running an Intel CPU on this computer, and my ntoskernl.exe comes from the folder "amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.15063.850_none_013717dd1a7ed72f", I assume that if they kept different binaries, they wouldn't use AMD branding for the Intel binary, and just call it Intel x86-64 or some such.
  Do you have any reason to think otherwise?
  
  --
  Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
43. Re:Why Meldown? by WaffleMonster · 2018-01-09 06:43 · Score: 2
  
  From my understanding, it's not even incompetence that brought this about in the first place. Lack of foresight more than anything else. No one imagined trying an exploit like these until recently. Unless they have, but have been
  keeping it quiet, much like the Allies kept the cracking of Enigma quiet...
  People did more than imagine. They wrote research papers on this very topic over a decade ago about the very thing the spectre ghost is holding in its hand.
  https://eprint.iacr.org/2006/2...
44. Re:Why Meldown? by Antique+Geekmeister · 2018-01-09 06:44 · Score: 2
  
  > No one imagined trying an exploit like these until recently.
  I'm afraid that this is not true. I'm following an intriguing discussion of similar side-channel attacks on Multics systems on GE hardware in roughly 1970. It's not a new problem. I've been trying to explain repeatedly to some colleagues while reviewing these attacks that doing "speculative compilation" is very appealing at first glance, but the work involved in doing it is not free. Security risks and maintenance of the resources are critical and related costs of such optimization.
45. Re:Why Meldown? by Anonymous Coward · 2018-01-09 08:07 · Score: 0
  
  Incompetence and weak coders at M$.
46. Re:Why Meldown? by Anonymous Coward · 2018-01-09 08:14 · Score: 0
  
  To level the playing field of course
47. Re: Why Meldown? by Megol · 2018-01-09 08:25 · Score: 1
  
  With exception of some optimization why would there be two kernels for a group of binary compatible processors? AMD and Intel are binary compatible unless one goes into some dusty corners and some setup specific things.
48. Re:Why Meldown? by Megol · 2018-01-09 08:29 · Score: 1
  
  Which is why Microsoft "forced" Intel to use AMD64 (renamed though) instead of their own emergency hack? There are other cases where MS forced Intel to behave.
49. Re:Why Meldown? by Anonymous Coward · 2018-01-09 08:29 · Score: 0
  
  I repeat what I said above: The only sound I hear right now is the full throttle fans from my ex. workmates( unknown beta tester) windows 7 AMD computer, witch I'm trying to restore after the update has destroyed it. Hi has already bought a new laptop so wintel +1
50. Re: Why Meldown? by ElizabethGreene · 2018-01-09 08:59 · Score: 1
  
  AMD chips are, according to AMD, vulnerable to a bounds check bypass related to speculative execution. In the details, they say "Resolved by software / OS updates to be made available by system vendors and manufacturers."
  They do NOT say they are immune to the branch target injection vulnerability either. The say the following which is much less reassuring: "Differences in AMD architecture mean there is a near zero risk of exploitation of this variant."
  http://www.amd.com/en/corporat...
51. Re:Why Meldown? by jwhyche · 2018-01-09 09:05 · Score: 2
  
  So the question you should ask yourself, is why you chose Microsoft.
  Because all the games and most of the software I want to run is Windows only. An none of the games have linux counterparts.
  Any other questions?
  
  --
  I read at +2. If your post doesn't reach that level I will not see or respond to it.
52. Re:Why Meldown? by ElizabethGreene · 2018-01-09 09:06 · Score: 1
  
  According to AMD, AMD is vulnerable to one variant of the attack, and possibly vulnerable to a second variant.
  http://www.amd.com/en/corporat...
53. Re:Why Meldown? by Anonymous Coward · 2018-01-09 12:08 · Score: 0
  
  This. Who would work for Microsoft, Google or Oracle these days when there are more ethical jobs everywhere. Inept ignorant assholes, that's who.
54. Re: Why Meldown? by Khyber · 2018-01-09 12:43 · Score: 1
  
  If you bothered to look more into AMD's statements, they have a much lower risk of exploitation because AMD encrypts everything in RAM with practically zero performance overhead. Even if exploited, you get encrypted data, which isn't the case with intel.
  
  --
  Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
55. Re: Why Meldown? by ElizabethGreene · 2018-01-09 13:48 · Score: 1
  
  Do you have a source for that? The linked page is all I can find on it.
56. Re:Why Meldown? by mcswell · 2018-01-09 15:14 · Score: 1
  
  One reason for binary equivalency would be that if I buy a new motherboard or new computer, I should be able to take the hard drive from my old PC and drop it into my new one. Now that's not to say that there might not be driver diffs, but they would presumably be self-contained modules, loadable at boot time.
57. Re: Why Meldown? by Anonymous Coward · 2018-01-09 20:14 · Score: 0
  
  There shouldn't be. There can be optimizations or fixes in the same kernel where it detects the exact model or manufacturer of the CPU to apply those optimizations or fixes. Appears MS took the lazy way out and applied the fix to all CPUs rather than detecting if an affected Intel CPU was present
58. Re: Why Meldown? by Khyber · 2018-01-10 02:46 · Score: 1
  
  Source? AMD's own webpage where they talk about SEV and SME. Of course, this isn't new technology; we've had encrypted RAM for at least 15 years.
  
  --
  Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
59. Re: Why Meldown? by ElizabethGreene · 2018-01-10 05:36 · Score: 1
  
  Encrypted ram protects you from physical attacks, i.e. cold boot or freeze the ram, power off, move the ram to another machine, and read the data out.
  That wouldn't seem to apply here, as the CPU executing the instructions has the decryption key.
  SEV would apply, and would keep a malicious hypervisor from reaching into a guest VMs memory space and digging around. That isn't what this class of vulnerabilities is though, and I don't see anything that indicates that SEV is used to separate kernel-mode and user-mode code within a machine.
  Do you have any links from AMD that indicate these technologies are mitigations for this class of attack?
60. Re:Why Meldown? by Agripa · 2018-01-10 07:52 · Score: 1
  
  Intel probably submitted the fix to Microsoft, and Microsoft's wonderful QA/QC team tested this (not likely) and got it ready for distribution.
  If you think about it, wouldn't Intel want all CPUs to have a significant performance penalty and not just their chips?
  It is not Intel's responsibility to not issue patches which break AMD's processors.
61. Re:Why Meldown? by hairyfeet · 2018-01-11 16:30 · Score: 1
  
  My Bad, I avoided all of the Intel chipsets like an STD, they were so much garbage that we shop guys knew to stay the hell away from anything Intel when it came to chipsets. Back then you wanted Nvidia or ATI, Intel was the crap you got stuck with if you didn't watch what you were buying.
  The only positive I can say about Intel chipsets is I made a killing on entry level PCI and PCIe cards when Win 7 came out, all these folks would say "I want Win 7!" and I'd take one look and go "not with that board you don't, not unless you upgrade from those crap graphics".
  
  --
  ACs don't waste your time replying, your posts are never seen by me.
AMD? by Anonymous Coward · 2018-01-09 02:58 · Score: 5, Interesting

So, the problem is that AMD failed to comply with the documentation for the Intel bug? Perhaps "failed to comply" is just MS-speak for "failed to implement the bug"...
1. Re:AMD? by Anonymous Coward · 2018-01-09 03:26 · Score: 0
  
  I know this is /., but read the article. It's pretty clear that MS is saying that AMD's processors did not conform to the documentation that they (AMD) sent to MS.
2. Re:AMD? by Entrope · 2018-01-09 03:33 · Score: 4, Insightful
  
  No, it's really not clear. Maybe that is the implication that Microsoft wants people to draw, but they don't directly say who provided the documentation in question.
3. Re:AMD? by mOzone · 2018-01-09 05:19 · Score: 1
  
  other then newest cpu's ...AMD cpus didn't change realy for 4+ years fx4300s-FX95XX not a huge secret to Microsoft ..AM3 motherboards and configs have to be known to them for 4+ years also ..Microsoft screwed up
4. Re:AMD? by Anonymous Coward · 2018-01-09 08:16 · Score: 0
  
  It was intentional sabotage to AMD. Otherwise it is easy for the patch to just check with
  if (CPUID == AMD) exit;
5. Re:AMD? by jrumney · 2018-01-09 14:12 · Score: 1
  
  It's pretty clear that AMD did not make any change to their processors between 2 Jan and now.
6. Re:AMD? by jrumney · 2018-01-09 14:15 · Score: 1
  
  if (CPUID == AMD) exit;
  I think Anonymous Microsoft Engineer just revealed the bug.
pay for by intel the same one who pay to may 1p ep by Joe_Dragon · 2018-01-09 03:05 · Score: 1

pay for by intel the same one who pay to may 1p epyc board be MIA. as well killing ryzen pro boards with IPMI.
Fuck off Microsoft, you're just trying to kill AMD by Anonymous Coward · 2018-01-09 03:06 · Score: 1

Wintel at work.
with linux it's just an boot flag to turn off the by Joe_Dragon · 2018-01-09 03:24 · Score: 1

with linux it's just an boot flag to turn off the slowdown
Re:Fuck off Microsoft, you're just trying to kill by Anonymous Coward · 2018-01-09 03:35 · Score: 0

AMD fanboys just can't get a break.
Intel paid Microsoft to slow down AMD by Anonymous Coward · 2018-01-09 03:47 · Score: 0

... only problem was it slowed some configs down too much and they got caught.
I was starting to see this issue by Anonymous Coward · 2018-01-09 03:48 · Score: 0

Once I got the affected machine (Phenom X2 B57) to boot (using F8 during startup), I re-ran WU. Once it got to the point where it wanted to restart to finish the process, I turned off AV (other than Defender), and restarted. The update then worked, and I'm running again.. possible fix?
Re:with linux it's just an boot flag to turn off t by MightyMartian · 2018-01-09 05:04 · Score: 1

Yes, I'm not clear why MS can't just check the CPU ID and decide functionality based on that. There must be other oddities of X86/64 architecture between different processor families that require MS to turn features on or off, or even alter the nature of functionality.

--
The world's burning. Moped Jesus spotted on I50. Details at 11.
Yeah by Anonymous Coward · 2018-01-09 05:36 · Score: 0

"Microsoft says that it is working with AMD to address the problem"
Perhaps they should have worked with AMD before they released an untested patch.
Collusion investigation of wintel in 3...2.......? by WaffleMonster · 2018-01-09 06:14 · Score: 2

Amazing the company that does it right and is not vulnerable to "Meltdown" in the first place is being actively punished for that fact.
Re:with linux it's just an boot flag to turn off t by Aighearach · 2018-01-09 06:51 · Score: 1

an boot
First time I found a person who pronounces boot with a silent B! lol
Re:Collusion investigation of wintel in 3...2..... by Anonymous Coward · 2018-01-09 07:27 · Score: 0

I'd like to know if this affects home PCs only, or servers (if MS supports AMDs in servers). If it hits servers as well I'd take it as a genuine mistake; if home only then it stinks.
Paused but still pushed by Anonymous Coward · 2018-01-09 07:55 · Score: 0

I just uninstalled the KB4056892 before it rebooted to install it completely.
About 5 minutes later Windows notified me that a new update was available...KB4056892.
Code does not work that way by Anonymous Coward · 2018-01-09 12:03 · Score: 0

There is code for Spectre and there is code for Meltodown. They are not same code.
Look closely now. Intel is doing everything Intel can to control the PR disaster, including pulling every possible competitor down with them. Inner circles hard at work, causing closely affiliated 'information outlets' spew whatever suits Intel best in this situation.
This is capitalism at its worst. Shit hits the fan and multiple separate companies voice out in unison: "It's nothing!"
Re:Why Meltdown? by Anonymous Coward · 2018-01-09 12:22 · Score: 0

Really? I'd love to read about this. Got a source?
I thought it was because both AMD and Intel have a cross-licensing agreement on the x86 instruction set. That's why MMX and SSE made its way to AMD processors.
So M$oft didn't make them behave, they recognised their position in the market when AMD came out with x86-64 and realised they were outmaneuvered. No one would adopt IA-64 now. There was no 'forcing' by anyone except the market. x86-64 was there for them to adopt, and they adapted.
Re: pay for by intel the same one who pay to may 1 by Brockmire · 2018-01-09 12:27 · Score: 1

You are approaching apk levels of annoying with this Ryzen plus IPMI spam. Just stop. Thanks.