Yesterday, the third Tuesday of the month, Microsoft dumped another big bucket of patches:<\/span><\/p>\n\n
![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/09\/windows_patch_security12-100734741-large.3x2.jpg\"\/)
<\/p>\n<\/p>\n
Credit to Author: Woody Leonhard| Date: Wed, 18 Apr 2018 06:32:00 -0700<\/strong><\/p>\n Yesterday, the third Tuesday of the month, Microsoft dumped another big bucket of patches:<\/span><\/p>\n There are lots of oddities in this motley collection.<\/span><\/p>\n The <\/span>Monthly Rollup Preview for Win7<\/span><\/a> says:<\/span><\/p>\n Addresses a stop error that occurred when the previous month\u2019s update was applied to 32-bit (x86) computers with Physical Address Extension (PAE) mode disabled.<\/span><\/p>\n If you thought we\u2019d already been through that hassle, you\u2019re right. The March Win7 <\/span>Monthly Rollup<\/span><\/a> and <\/span>Security-only patch<\/span><\/a> say the problems are fixed by the April patches we got a week ago, KB 4093118 and KB 4093108. (Thx, MrBrian.) Why does the Preview list them as solved, when they were listed as solved last week?<\/span><\/p>\n Abbodi86 <\/span>has an answer<\/span><\/a>:<\/span><\/p>\n The same fix is in both the April Monthly Rollup and in the Preview. I guess they ran out of something extra to list in the page \ud83d\ude42<\/span><\/p>\n KB4093113 (the Monthly Rollup Preview) literally has nothing new over KB4093118 (the Monthly Rollup) except two things:<\/span><\/p>\n I wonder why they didn\u2019t document what’s fixed\/improved in the Windows Update Agent. Both the Win7 and 8.1 Monthly Rollup Previews released yesterday have the changes.<\/span><\/p>\n The KB 4099950 patch-of-a-patch-of-a-buggy-patch <\/span>continues to confuse<\/span><\/a>. It\u2019s supposed to be <\/span>a precursor <\/span><\/a>to installing the Win7 March Monthly Rollup, KB 4088875, or the Security-only patch, KB 4088878, and it\u2019s designed to bypass the bug in those two March patches that mess up NIC settings and\/or static IP addresses. <\/span><\/p>\n It appears as if the metadata in KB 4099950 changed yesterday, but the files themselves have not.<\/span><\/p>\n According to the <\/span>Knowledge Base article<\/span><\/a>:<\/span><\/p>\n If you have previously installed KB4099950 prior to April 17, 2018 please uninstall the older version of KB4099950 and reinstall to assure you have the most recent version.<\/span><\/p>\n Alpha128 posed <\/span>a great question<\/span><\/a>, unanswered by the official docs:<\/span><\/p>\n So those of us who installed KB4099950 before March Rollup KB4088875, but prior to April 17, 2018, have to uninstall the older version of KB4099950 and reinstall to be sure we have the most recent version?<\/span><\/p>\n Are we supposed to do that <\/span>before<\/span><\/i> or <\/span>after<\/span><\/i> installing April Rollup KB4093118?<\/span><\/p>\n At this point, I don\u2019t have a definitive answer to the question, although there\u2019s a detailed discussion of the bugs in the earlier version of KB 4099950 <\/span>starting here<\/span><\/a>.<\/span><\/p>\n Twbartender <\/span>goes on to ask<\/span><\/a>:<\/span><\/p>\n The problem is when you click on the download tab in the catalog, there are 2 separate files being offered for download. One is an .exe file and the other is .msu file.<\/span><\/p>\n pciclearstalecache_1c944f48bfb21d88a2054683abcd02327ecf6b37.exe<\/span><\/p>\n windows6.1-kb4099950-x64_245d5aaf7d50587297825f9176be166c47ad10f7.msu<\/span><\/p>\n Are both of these files required to be installed in order for KB4099950 to function properly?<\/span><\/p>\n It would be nice of Microsoft if they would give a little more information on how to apply this new update.<\/span><\/p>\n According to <\/span>abbodi86<\/span><\/a>, you only need the .msu file update.<\/span><\/p>\n All of this would be rather funny, in a gallows-humor sort of way, if it weren\u2019t for the fact that plenty of Win7 and Server 2008R2 machines are dropping off their networks because of bugs in last month\u2019s security patches. Microsoft has provided extremely poor, frequently conflicting, documentation of the best way to proceed.<\/span><\/p>\n Of course, I continue to recommend that you hold off on this month\u2019s patches.<\/span><\/p>\n Join us for the usual Wednesday-morning quarterbacking on the<\/span><\/i> AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Wed, 18 Apr 2018 06:32:00 -0700<\/strong><\/p>\n Yesterday, the third Tuesday of the month, Microsoft dumped another big bucket of patches:<\/span><\/p>\n<\/p>\n\n