![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security14-100734743-large.3x2.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Tue, 16 Jan 2018 07:33:00 -0800<\/strong><\/p>\n I\u2019ve seen a lot of bizarre Microsoft patches-of-patches, but the new patches for AMD processors are in a world of their own. The security-only, manually downloadable patches appear to be Meltdown\/Spectre patches for machines that were bricked by other bad patches, earlier this month, but they\u2019ve arrived with no instructions \u2014 and a strange circular logic.<\/span><\/p>\n Last week, Microsoft released two patches, with these official titles:<\/span><\/p>\n The Win7 KB article says:<\/span><\/p>\n An update is available to fix the following issue that occurs after you install <\/span>January 3, 2018\u2014KB4056897 (Security-only update)<\/span><\/a> or <\/span>January 4, 2018\u2014KB4056894 (Monthly Rollup)<\/span><\/a>:<\/span><\/p>\n AMD devices fall into an unbootable state\u2026<\/span><\/p>\n This update does not replace a previously released update.<\/span><\/p>\n The Win8.1 article says the same thing, with reference to the analogous patches <\/span>KB 4056898<\/span><\/a> and <\/span>4056895<\/span><\/a>.<\/span><\/p>\n \u2026 and that\u2019s all of the description on offer. You can find lots of posts about the two patches and how they fix the \u201cunbootable state\u201d (what most of us would call a BSOD or blue screen), but there\u2019s exactly zero advice on how to use the patches, or what fixes they include. And that part about \u201cdoes not replace a previously released update\u201d has my head whirling.<\/span><\/p>\n Just for starters, if you installed one of this month\u2019s buggy Meltdown\/Spectre Windows patches on a machine with an older AMD processor (Athlon, Sempron, Turion, Opteron, Phenom and some Ryzen computers), you probably <\/span>hit a blue screen<\/span><\/a>. Microsoft <\/span>pulled the patches<\/span><\/a>\u00a0a few days later, but a whole lot of people had to boot to a recovery environment or re-install Windows, just to get going again.<\/span><\/p>\n Now we have patches for Win7 and 8.1 that appear to be the Meltdown\/Spectre patches specifically for AMD machines. There\u2019s something karmic about a patch that is designed to install on a machine that can\u2019t boot, thus can\u2019t install any patches. But let’s move beyond the Kafkaesque dilemma.<\/span><\/p>\n Here are just a few of the many, many questions swirling around over the weekend:<\/span><\/p>\n Which AMD machines are targeted? I don\u2019t know. Microsoft isn\u2019t saying. Apparently these patches are meant for machines that threw BSODs with the earlier patches \u2014 but do you need to install the original patch and wait to see if you hit a BSOD, before installing these patches?<\/span><\/p>\n If installing a patch just to see if it bricks your machine doesn\u2019t sound like a fun way to spend a snowy day, can you put these new patches on any AMD machine? If so, what happens? Who knows? <\/span><\/p>\n Are these patches replacements for the originals \u2014 do they cover the same ground \u2014 or are they somehow different? Poster <\/span>@MrBrian on AskWoody<\/span><\/a> says:<\/span><\/p>\n On Windows 7 x64, I compared what KB4056897 installs vs. what KB4073578 installs. Considering just executable files, KB4073578 installs a newer version of some executable files. \u2026 Of the changed executable files between the two Windows 7 x64 updates (inspected with CBS Package Inspector), the only executable file that changed in size is hvax64.exe.<\/span><\/p>\n So if the old and new versions of this month\u2019s Windows\/Spectre patches install different files, should you install the new patch on an AMD machine that somehow installed the old one? <\/span><\/p>\n For that matter, can you install this newer version on an Intel machine and get away with it? @MrBrian in an intrepid moment tried that. <\/span>His conclusion<\/span><\/a>:<\/span><\/p>\n As a test, I installed<\/span> KB4073578<\/span><\/a> on two computers with two different Intel CPU models. I then rebooted and logged into a user account on each computer. There were no apparent problems. <\/span><\/p>\n To recap, we have patches for Win7 and 8.1 AMD computers that officially only apply to bricked AMD computers, but still install on Intel computers, and come up with a newer hvax64.exe file. And the patches are only for Win7 and 8.1, not Win10.<\/span><\/p>\n Care to chase this down the January patch rabbit hole? <\/span><\/p>\n For example, as @PKCano notes, the Win8.1 Monthly Rollup appeared after the Win7 Monthly Rollup. Does the Win8.1 Monthly Rollup include the new security files or the old ones? <\/span><\/p>\n What happens if you install the old patches and the new patches, in any time sequence combination of Security-only, Monthly Rollup, old and new? <\/span><\/p>\n Let\u2019s not forget that Microsoft started <\/span>pushing the Meltdown\/Spectre patches <\/span><\/a>for some AMD processors, but are they old ones or new ones, and for which processors?<\/span><\/p>\n Most of all, what happened to Windows 10? Microsoft <\/span>yanked a half-dozen<\/span><\/a> January Win10 cumulative updates because they were bricking AMD processors. At least some of those cumulative updates are going out again. Do they include the new files or the old ones? Since Microsoft doesn\u2019t release Security-only patches for Win10, are we stuck with the old cumulative updates until the February Patch Tuesday cycle kicks in? What about those who have AMD machines that choke on the cumulative updates?<\/span><\/p>\n I feel an Excedrin headache coming on. Join me on the <\/span><\/i>AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n