Patches for Windows - Site version 3116

My October baselines have 2 fixlets where the source fixlet differs - this wasn’t the case when I went home last night.

I looked for a site content modification mail and then for an announcement in this forum, but I can’t find one.

Current site version is 3116, my last site content modification mail for Patches for Windows was for version 3114.

Microsoft’s pages were both last modified on 9th October, so I would guess that the relevant (rather than the patch payload) has changed, but I don’t like guessing and I need to know whether the testing and piloting is still valid - if the relevance has changed then I can sync the baseline, if the payload has changed I need to repeat testing to reduce the chances of killing off applications or computers.

I’m surprised you didn’t list those fixlets in your post. I’m not seeing any difference on my end. It has been rumored that KB4462923 was pulled but nothing official from M$.

Today we start our production Windows client patching and I plan to move forward.

I’m surprised I didn’t too.

Session relevance:

	(
		name of it , source release date of it , modification time of it 
	)
	of fixlets 
	whose
	(
		category of it = "Security Update" 
	and
		source release date of it > current date - 10 * day 
	and
		modification time of it > now - 12 * hour 
	)
	of all bes sites 
	whose
	(
		name of it = "Enterprise Security" 
	)

Results:

|MS18-OCT: Security update for Excel 2016 - Excel 2016 - KB4461448|Tue, 09 Oct 2018|Tue, 16 Oct 2018 01:17:14 +0100|
 |MS18-OCT: Security update for Word 2016 - Word 2016 - KB4461449|Tue, 09 Oct 2018|Tue, 16 Oct 2018 01:17:14 +0100|

I’m surprised there has been an update with no corresponding announcement.

Announcement mail has arrived.

A number of Office 2016 fixlets, including these two and stretching back to September 2017 have been updated to address some cases of false negative.