Microsoft halts the distribution of the Meltdown patch.

[whoololon]

Source.

It seems that the main affected have been users of AMD processors (I assume AM3 and AM3+ platforms) after installing the patch against the Meltdown vulnerability launched indiscriminately by Microsoft through Windows Update, which has left their computers unusable after applying said file.
This has led Microsoft to stop "offering" said update via Windows Update (although it can still be downloaded manually from the repository, as we will see later).

The Redmond-based company, for its part, blames AMD for the documentation provided that has caused such an incident, something that I assume AMD will deny.

Not long ago, I commented that said patch did not come out among the critical updates, it was thanks to Cobito linking it that I could apply it; which leads me to assume (given that nowhere is anything concrete specified) that it was W10 that was responsible as it is more prone to force the installation of patches and updates.
In fact, the article links to documentation of the patch KB4054022, which is for Windows 10, and which, as can be seen, has not been withdrawn.

I continue with my particular (and according to some, stupid) crusade against W10, but if one does not have a KabyLake or is not a user of AM4, W10 should stay far away.

[cobito]

I'm also not a fan of Windows 10 precisely because it updates itself.

The truth is that the big American tech companies are showing off with their statements on this matter. First Intel puts its marketing team to work to give a ridiculous and shameful explanation for the failure (nothing less than saying that it is actually a software failure) and now Microsoft is dodging the issue with AMD whose micros, by the way, do not have speculative memory prediction and are therefore free of guilt.

Without being a fan of AMD (or Intel or any) I have to say that they are treating the company shamefully in this matter: in Linux the patch is applied to their processors by default (I don't know if in the last hours it has changed) harming the performance in the appropriate tasks (it does affect virtualization). And now they are defenestrating an entire platform, because in the end the user sees that their PC doesn't work, not because they use Windows, but because they use AMD while the one next to them who uses Intel, does work.