This article possibly contains original research. (July 2014) (Learn how and when to remove this template message)
Patch Tuesday (also known as Update 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. Microsoft formalized Patch Tuesday in October 2003.
Patch Tuesday occurs on the second, and sometimes fourth, Tuesday of each month in North America. As far as the integrated Windows Update (WU) function is concerned, Patch Tuesday begins at 18:00 or 17:00 UTC (10:00 PST (UTC−8) or 10:00 PDT (UTC−7)). The updates show up in Download Center before they are added to WU, and the KB articles and the Technet bulletin are unlocked later.
Microsoft has a pattern of releasing a larger number of updates in even-numbered months, and fewer in odd-numbered months. Minor updates are also released outside Patch Tuesday. Daily updates consist of malware database refreshes for Windows Defender and Microsoft Security Essentials. Sometimes there is an extraordinary Patch Tuesday, two weeks after the regular Patch Tuesday. Some updates could be released at any time.
Starting with Windows 98, Microsoft included Windows Update that once installed and executed, would check for patches to Windows and its components, which Microsoft would release intermittently. With the release of Microsoft Update, this system also checks for updates for other Microsoft products, such as Microsoft Office, Visual Studio and SQL Server.
Earlier versions of Windows Update suffered from two problems:
- Less-experienced users often remained unaware of Windows Update and did not install it. Microsoft countered this issue, in Windows ME with the Automatic Updates component, which displayed availability of updates, with the option of automatic installation.
- Customers with multiple copies of Windows, such as corporate users, not only had to update every Windows deployment in the company but also to uninstall patches issued by Microsoft that broke existing functionality.
Microsoft introduced "Patch Tuesday" in October 2003 to reduce the cost of distributing patches. This system accumulates security patches over a month, and dispatches them all on the second Tuesday of each month, an event for which system administrators may prepare. The following day, informally known as "Exploit Wednesday", marks the time when exploits may appear in the wild which take advantage on unpatched machines of the newly announced vulnerabilities.
Tuesday was chosen as the optimal day of the week to distribute software patches. This is done to maximize the amount of time available before the upcoming weekend to correct any issues that might arise with those patches, while leaving Monday free to address other unanticipated issues that might have arisen over the preceding weekend.
An obvious security implication is that security problems that have a solution are withheld from the public for up to a month. This policy is adequate when the vulnerability is not widely known or is extremely obscure, but that is not always the case.
There have been cases where vulnerability information became public or actual worms were circulating prior to the next scheduled Patch Tuesday. In critical cases Microsoft issues corresponding patches as they become ready, alleviating the risk if updates are checked for and installed frequently.
At the Ignite 2015 event, Microsoft revealed a change in distributing security patches. They release security updates to home PCs, tablets and phones as soon as they are ready, while enterprise customers will stay on the monthly update cycle, which was reworked as Windows Update for Business.
Many exploitation events are seen shortly after the release of a patch; analysis of the patch helps exploitation developers to immediately exploit the previously unknown underlying vulnerability, which will remain in unpatched systems. Therefore, the term "Exploit Wednesday" was coined.
Discontinued Windows versions
Microsoft warned users that it discontinued support for Windows XP starting on April 8, 2014 - users running Windows XP afterwards would be at the risk of attacks. As security patches of newer Windows versions can reveal similar (or same) vulnerabilities present in both newer and older Windows versions, this can allow attacks on devices with unsupported Windows versions (c.f. "zero-day attacks"). However Microsoft stopped fixing such (and other) vulnerabilities in unsupported Windows versions, regardless how widely known such vulnerabilities became, leaving these vulnerabilities unfixed and devices running these Windows versions vulnerable to attacks. Microsoft made a singular exception during the rapid spread of the WannaCry ransomware and released patches in May 2017 for the by then unsupported Windows XP, Windows 8, and Windows Server 2003 (in addition to then supported Windows versions).
For Windows 7 (with Service Pack 1) support will end January 14, 2020, and on January 10, 2023 for Windows 8.1; this will cause the same "unfixed vulnerabilities" issue for users of these operation systems. Support for Windows 8 already ended January 12, 2016 (with users having to install Windows 8.1 or Windows 10 to continue to get support), and support for Windows 7 without SP1 was ended April 9, 2013 (with the ability to install SP1 to continue to get support until 2020, or having to install Windows 8.1 or Windows 10 to receive support after 2020).
One major change with the introduction of Windows 10 was that Microsoft started to release a new version of Windows 10 twice per year, and with Microsoft's "modern lifecycle policy" a newly released Windows 10 version starts a "grace period" for the previous version with regards to support - unlike previous Windows products which received only infrequent updates via service packs, and supported was governed by the "fixed lifecycle policy". With this new policy Home and Pro version of Windows 10 will be provided with security and feature updates (so called "mainstream support") for up to 18 months after release, "enterprise" and education versions with 24 months. To give an example: support for Windows 10 Home/Pro version 1703 (which was released in April 2017) will be stopped by Microsoft in October 2018, and support for versions 1507 and 1511 (released in 2015) officially ended in 2017. Microsoft announced to give "extended support" (security but not feature updates) for at least one "semi-annual channel" (SAC) Windows 10 version until October 14, 2025.
According to Microsoft a "device needs to install the latest version (feature update) before [the] current version reaches end of service to help keep your device secure and have it remain supported by Microsoft". Same as with previous Windows operating systems, any device running such an unsupported version of Windows (which no longer receives security patches) is potentially affected by the "unfixed vulnerabilities" issue beginning with the "end of support" date. To counter this Microsoft has designed the update system for the Home and Pro editions of Windows 10 so that in most cases if technically possible the latest Windows version is downloaded and installed automatically - this has however drawn criticism due to other problems such forced upgrades can introduce.
|Version||Codename||Marketing name||Release date||Support until||Latest build|
|Threshold 1||N/A||July 29, 2015||May 9, 2017||May 9, 2017||October 14, 2025||N/A||Older version, yet still supported: 10240||N/A|
|Threshold 2||November Update||November 10, 2015||October 10, 2017||October 10, 2017||N/A||January 9, 2018||Old version, no longer supported: 10586||Old version, no longer supported: 10586|
|Redstone 1||Anniversary Update||August 2, 2016||April 10, 2018||April 9, 2019||October 13, 2026||October 9, 2018||Older version, yet still supported: 14393||Old version, no longer supported: 14393|
|Redstone 2||Creators Update||April 5, 2017||October 9, 2018||October 8, 2019||N/A||July 11, 2019||Older version, yet still supported: 15063||Older version, yet still supported: 15063|
|Redstone 3||Fall Creators Update||October 17, 2017||April 9, 2019||April 14, 2020||N/A||December 10, 2019||Older version, yet still supported: 16299||Current stable version: 15254|
|Redstone 4||April 2018 Update||April 30, 2018||November 12, 2019||November 10, 2020||N/A||N/A||Older version, yet still supported: 17134||N/A|
|Redstone 5||October 2018 Update||November 13, 2018||May 12, 2020||May 11, 2021||January 9, 2029||N/A||Current stable version: 17763||N/A|
|19H1||TBA||TBA||+18 Months||+18 Months||TBA||N/A||Latest preview version of a future release: 18282||N/A|
In addition to the commonly used editions like Home and Pro, Microsoft offers specialized "Long-Term Servicing Branch" (LTSB) or "Long-Term Servicing Channel" (LTSC) versions of Windows 10 with longer support timelines, governed by Microsoft's "fixed lifecycle policy" - e.g. "Windows 10 Enterprise 2016 LTSB" will receive extended support until October 13, 2026.
Adoption by other companies
SAP's "Security Patch Day", when the company advises users to install security updates, was chosen to coincide with Patch Tuesdays. Adobe Systems' update schedule for Flash Player since November 2012 also coincides with Patch Tuesday. One of the reasons for this is that Flash Player comes as part of Windows starting with Windows 8 and Flash Player updates for the built-in and the plugin based version both need to be published at the same time in order to prevent reverse-engineering threats.
Windows Update uses the Background Intelligent Transfer Service (BITS) to download the updates, using idle network bandwidth. However BITS will use the speed as reported by the network interface (NIC) to calculate bandwidth. This can lead to bandwidth calculation errors, for example when a fast network adapter (e.g. 10 Mbit/s) is connected to the network via a slow link (e.g. 56 kbit/s) - according to Microsoft "BITS will compete for the full bandwidth [of the NIC] ... BITS has no visibility of the network traffic beyond the client."
Furthermore the Windows Update servers of Microsoft do not honor the TCP's slow-start congestion control strategy. As a result, other users on the same network may experience significantly slower connections from machines actively retrieving updates. This can be particularly noticeable in environments where many machines individually retrieve updates over a shared, bandwidth-constrained link such as those found in many multi-PC homes and small to medium-sized businesses. Bandwidth demands of patching large numbers of computers can be reduced significantly by deploying Windows Server Update Services (WSUS) to distribute the updates locally.
In addition to updates being downloaded from Microsoft servers, Windows 10 devices can "share" updates in a peer-to-peer fashion with other Windows 10 devices on the local network, or even with Windows 10 devices on the internet. This can potentially distribute updates faster while reducing usage for networks with a metered connection.
- "August updates for Windows 8.1 and Windows Server 2012 R2". Windows Experience Blog. Retrieved 25 November 2015.
- "Microsoft Patch Tuesday to target Windows, IE". CNet. October 10, 2011. Retrieved November 9, 2011.
- ".NET Framework 1.1 Servicing Releases on Windows Update for 64-bit Systems". Microsoft. March 28, 2006. Archived from the original on March 27, 2012. Retrieved November 8, 2011.
- "Understanding Windows automatic updating". Microsoft — Understanding Windows — Get Help. Retrieved July 3, 2014.
- Budd, Christopher. "Ten Years of Patch Tuesdays: Why It's Time to Move On". GeekWire. Retrieved 28 July 2015.
- Trent, Rod (2004). The Administrator Shortcut Guide to Patch Management. p. 51. ISBN 9781931491365.
- Gregg Keizer (9 June 2011). "Microsoft slates hefty Patch Tuesday, to fix 34 flaws next week". Computerworld. Retrieved 25 November 2015.
- "Microsoft Ready To Patch 34 Security Vulnerabilities". ITProPortal. Retrieved 25 November 2015.
- Gregg Keizer. "Microsoft to patch critical Windows Server vulnerability". Techworld. Retrieved 25 November 2015.
- "Patch Tuesday: WM 6.1 SMTP fix released!". Microsoft — Outlook Mobile Team Blog. November 11, 2008. Retrieved November 9, 2011.
- "Microsoft details new security plan". News.cnet.com. Retrieved 2013-02-12.
- Paul Oliveria (Trend Micro Technical Communications) (4 October 2006). "Patch Tuesday… Exploit Wednesday". Blog.trendmicro.com. Retrieved 9 February 2016.
- "Windows 10 bombshell: Microsoft to KILL OFF Patch Tuesday". theregister.co.uk. Retrieved 25 November 2015.
- "Exploit Wednesday". afterdawn.com. Retrieved 25 November 2015.
- Kurtz, George (2010-01-14). "Operation "Aurora" Hit Google, Others". mcafee.com. Archived from the original on 2012-01-17. Retrieved 2014-08-12.
- Leffall, Jabulani (2007-10-12). "Are Patches Leading to Exploits?". Redmond Magazine. Retrieved 2009-02-25.
- "Customer Guidance for WannaCrypt attacks". MSRC. Retrieved 2017-11-23.
- "Windows lifecycle fact sheet". Microsoft. 2015-08-31. Retrieved 2015-08-31.
- Windows 10 v1507 End of Servicing for CB and CBB - Microsoft.com
- Search product life cycle - Windows 10 - Microsoft.com
- von Etizen, Chris (2010-09-15). "SAP introduces a patch day". The H Security. Archived from the original on 11 August 2011. Retrieved 2013-01-07.
- McAllister, Neil (2012-11-08). "Adobe switches Flash fix schedule to Patch Tuesdays". The Register. Retrieved 2013-01-07.
- "About BITS". MSDN. Microsoft. Retrieved 26 March 2016.
- MSDN BITS Network Bandwidth
- Strong, Ben (2010-11-25). "Google and Microsoft Cheat on Slow Start". benstrong.com. Archived from the original (blog) on December 7, 2013.
- Warren, Tom (15 March 2015). "Microsoft to deliver Windows 10 updates using peer-to-peer technology". The Verge. Vox Media.
- Chacos, Brad (3 August 2015). "How to stop Windows 10 from using your PC's bandwidth to update strangers' systems". PC World. IDG.
- Evers, Joris (2005-09-09). "Microsoft pulls 'critical' Windows update". CNET News.com. Retrieved 2006-12-12.
- Schneier, Bruce (17 July 2006). "Zero-Day Microsoft PowerPoint Vulnerability". Schneier on Security. Example of report about vulnerability found in the wild with timing seemingly coordinated with "Patch Tuesday"
- Schneier, Bruce (7 September 2006). "Microsoft and FairUse4WM". Schneier on Security. Example of a quick patch response, not due to a security issue but for DRM-related reasons.