Talk:Patch Tuesday

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on Patch Tuesday. Please take a moment to review my edit. You may add {{cbignore}} after the link to keep me from modifying it, if I keep adding bad data, but formatting bugs should be reported instead. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether, but should be used as a last resort. I made the following changes:

• Attempted to fix sourcing for http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 13:21, 31 March 2016 (UTC)

"fixed the wrong way around"?

You reverted my edit, but I don't quite understand what you mean by "fixed the wrong way around". Windows 10 most definitly does not become unsupported at that date. Rather, the version released in 2015, aka "1507" (if I am not mistaken) – e.g. "10 Enterprise 2015 LTSB" – becomes unsupported by 2025. I think you are wrong (e.g. "Windows 10 Enterprise 2016 LTSB" is supported until 2026), and I kindly ask you to investigate the facts, and then correct the article accordingly. Kindest regards, Tony Mach (talk) 11:18, 24 February 2018 (UTC)

Hello, Tony Mach

Everything you said here is completely correct. But that's not sufficient.

The statement we want to verify is 'The "zero day" issue for [...] Windows 10 [will occur] starting October 14, 2025."

My source confirms that until October 14, 2025, Microsoft will keep all editions of Windows 10 updated to such extent that no zero day issue would occur for them. Since that date, however, most editions or Windows 10 (Home, Pro, Enterprise, Enterprise LTSB 2015, Mobile, Pro Workstation, Eduction) will see zero day issues.

Best regards,
Codename Lisa (talk) 11:53, 24 February 2018 (UTC)

Please supply a reference for this assertion:

"Since that date, however, most editions or Windows 10 (Home, Pro, Enterprise, Enterprise LTSB 2015, Mobile, Pro Workstation, Eduction) will see zero day issues."

Until then, I will remove the problematic content from wikipedia. Tony Mach (talk) 12:00, 24 February 2018 (UTC)

PS: "most editions" does NOT mean Windows 10 in its entirety.

Er ... care to explain? —Codename Lisa (talk) 12:09, 24 February 2018 (UTC)

This is the sentence as it was:

The "zero day" issue for Windows 7 will occur starting January 14, 2020, for Windows 8.1 starting January 10, 2023, and for Windows 10 starting October 14, 2025.

These will be the dates that Windows 7 (in its entirety), Windows 8.1 (in its entirety) but Windows 10 not in its entirety, will be no longer supported by Microsoft (only the LTSB Version 1507 will have the zero day problem!). But the sentence makes the impression that "Windows 10" will no longer be supported after 2025, which is wrong. As long as a person updates their computer (which Microsoft is doing rather forcefully, if I may remark), they will most definitely receive updates after 2025.

BTW: A "regular" person will have received updates for Windows 10 "1507" only until 2017, so that person would already have a zero day issues. So now you go and write better sentences, and I will revert them if I don't like them. Tony Mach (talk) 12:21, 24 February 2018 (UTC)

Again, the first part of your message is completely true, but not sufficient. It is a coincidence that Windows 7 and 8.1 don't have disparate support policies across their editions. Windows 10 does. Now, we must judge whether we mention a date when the first Windows 10 edition is exposed to zero day or the last Windows 10 edition. Since we are talking about danger, the first date (in which most editions are inflicted with zero day problem) is more appropriate. It is like huricane preparation: The news sets preparation deadline for when the hurricane reaches the first town, not last.

As for the second part of your message, you should read the fineprint in the source I have given:

Microsoft will continue to support at least one Windows 10 Semi-Annual Channel until the extended support date of October 14, 2025.

So, the question is: What happens to the other Windows 10 Semi-Annual Channels? The answer could be found in Windows lifecycle fact sheet which is: They expire long before that date.

"Please supply a reference for this assertion: [...]" I did! Check the diff to which you yourself have linked.

Best regards,
Codename Lisa (talk) 12:32, 24 February 2018 (UTC)

"Windows 7 and 8.1 don't have disparate support policies across their editions."

Not true, Microsoft makes a difference between Windows 7 and Windows 7 Service Pack 1. Tony Mach (talk) 15:41, 24 February 2018 (UTC)

I said "across editions". "Service Pack 1" is not an edition. —Codename Lisa (talk) 19:04, 24 February 2018 (UTC)

Too much queasy genuflect in the use of the word "official"

Patch Tuesday is an unofficial term used to refer to when Microsoft regularly releases security patches for its software products. It is widely referred to in this way by the industry.

I get why this is written this way, but there comes a point where a word is simply stretched too far, and we are verging on the rupture point here concerning the word "official".

Patch Tuesday is more properly thought of as a de facto industry-wide expression concerning a Microsoft policy that sends shock waves through the industry on the scale of an elephant—let's call her Mommy Matilda—taking a scheduled dump on an Antz hill (as viewed from the perspective of Woody Allen).

I've been reading Slashdot for nearly twenty years, and I can't recall seeing any other term in all that time, since early days in its inception. (Cleaning up all the crass language directed by the lower echelons at Microsoft's scheduled shit show would make even Hercules blanch, and maybe take a mulligan on his job-jar labour of the day.)

As for Microsoft's endorsement of this de facto terminology on the ground, who cares? They aren't ANSI. They aren't IANA. They aren't W3C. They aren't NIST. They aren't the DOD. They aren't even Websters.

Proposal:

Patch Tuesday is an industry-wide de facto term used to refer to when Microsoft regularly releases security patches for its software products, although the term has never been formally recognized by Microsoft.

Ah, but this is Wikipedia, so we can't write that the dog didn't bark in the night (that would ineluctably remain "citation needed" for ever and a day).

You know, if there's a thing about Wikipedia worse than it's inability to point to the thundering thud of the absence of evidence, I don't what that would possibly be.

Oh, but some pundit could write "isn't it weird how Microsoft has never officially endorsed the term 'Patch Tuesday' " (hey, we could cite that). Yes, we could, if the pundit wanted to talk to her audience like children who can't even count an elephant's four legs (while standing under the elephant [added by edit] as the two hind legs buckle ominously at the knees)—and in so doing conspicuously displaying no great desire to remain a pundit much longer.

However, despite the glaring CLM loophole, the rest of the logic here is absolutely watertight so far as Wikipedia's internal culture is concerned (and well it should be, because there's going to be a great associated flood, too).

Nevertheless, I thought I'd drop by and point out that the use of the word "official" in this context is officiously ridiculous. — MaxEnt 18:26, 17 May 2019 (UTC)

Other Tuesdays

This is still WP:OR, but updates for Microsoft Office also occur on the fourth and sometimes the first Tuesday of the month. tgeorgescu (talk) 20:17, 10 March 2022 (UTC)