Talk:Windows 10 version history/Archive 2

How should the article be split?
Earlier, I split the article into sections set for every 1-2 years. However, many people did not like how it was split and one of the users moved the article back into one single article, stating that before another split, we must come to a consensus as to how the article is to be split. If anyone has suggestions as to how to split this article, please leave a message on my talk page. Harshmoney (talk) 02:43, 17 June 2020 (UTC)
 * Indeed, it's just matter of how. A divider that will split the article into no more than two will do very well for me. A good example is the Firefox early version history which was part of Firefox version history, it got split into own article with good name, it's a divider we need. But because there were two major contents in same article named "Early versions" and "Rapid releases" in the past, the former got split easy. There's nothing like it here. However I've been looking into using codename as our divider. There's that Threshold and Redstone and the later ones don't seem to do it anymore. How does the Windows 10 Threshold and Redstone version history sound? It'll be holding all version history of Windows 10's Threshold and Redstone while we can continue adding new updates here.


 * I meant to ask you to build consensus because it's not the divider we want. Rukario -sama   ^ㅈ^ -(...)  10:03, 18 June 2020 (UTC)
 * I support the split you made in June and would encourage you to repeat it. Consensus isn't required for bold edits. Onetwothreeip (talk) 22:27, 22 July 2020 (UTC)

Page size
This page now has - depsite earlier atetmpts at splitting it up - 504,573 bytes of markup; it should be subdivided, into several sections. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 12:49, 21 September 2020 (UTC)

Build number suffixes for Dev Channel
It appears that Windows 10 build numbers in the Dev Channel have a ".1000" suffix (e.g. 10.0.20236.1000). Should this be included in the version history table for these preview builds? -- DL 6443  01:57, 16 October 2020 (UTC)
 * Yeah, I think it should be added. There was a time when the builds didn't have the suffix or it was simply ".0000", so it was omitted. At some point all the builds in the Fast Ring/Dev Channel started having ".1000" at the end, I don't remember at which point though, but surely it was before the new Fast Ring/Dev Channel strategy. Hayman30 (talk) 08:24, 16 October 2020 (UTC)
 * I can add the suffix for the builds in the new Dev Channel strategy (i.e. builds 19536 onwards) but someone will have to get the suffixes for earlier prerelease builds (I remember 20H1 preview 19008.1). -- DL 6443  04:14, 18 October 2020 (UTC)
 * Sounds good! Thanks for adding them. (By the way, just FYI, a ping only goes through if there's a new signature, so fixing the ping target without signing your message again doesn't work, hence I didn't get the notification.) Hayman30 (talk) 09:34, 18 October 2020 (UTC)

Changes throughout the years
Is it possible someone go through and add the "notable changes" in each version from 1607 through to 1809? Thanks -- DL 6443  23:59, 20 October 2020 (UTC)
 * I can help with that Herbfur (talk) 00:21, 21 October 2020 (UTC)
 * Thanks! Please add them ASAP -- DL 6443  23:56, 21 October 2020 (UTC)

PC version history
I like to suggest to add a note to detailed patch info at section "PC version history" If specific patch is only available for Education/Enterprise or LTSC (or special case like 1607 and Intel Clover Trail) and not for Home/Pro anymore.

Like it is already done for 1703 from Patch 10.0.15063.2172 with the note "This update is available for Surface Hub devices only." 213.61.152.30 (talk) 13:08, 24 June 2020 (UTC) I vote for this--2001:16B8:208:3400:7DBC:188B:C6E6:908B (talk) 10:24, 18 October 2020 (UTC) Done--2001:16B8:24C:EB00:85E7:FB1E:E0FB:700E (talk) 11:59, 23 October 2020 (UTC)

Dev Channel
Why was the list of Dev Channel builds removed? — Preceding unsigned comment added by 73.197.233.120 (talk) 04:15, 22 December 2020 (UTC)

21H2 will be
A.) have LTSC support,

B.) but only for 5 years

Source (German) https://www.heise.de/news/Windows-10-Enterprise-LTSC-Version-Ab-kommender-Version-nur-fuenf-Jahre-Support-5060596.html

-- 07:06, 22 February 2021 (UTC)  — Preceding unsigned comment added by LAZA74 (talk • contribs)

20H2 version?
Shouldn't the version for Win 10 20H2 be 2009, and not "20H2" ? (Don't have rights to edit the page.) — Preceding unsigned comment added by Ozskywalker (talk • contribs) 19:05, 17 March 2021 (UTC) No as the offical name by MS is "20H2" and not 2009 anymore. --87.123.175.50 (talk) 10:47, 15 May 2021 (UTC)

20H2 split
Now that 21H1 has been released, should we move 20H2 into its own article? -- DL 6443 (Talk/Contribs) 01:52, 20 May 2021 (UTC)

Split version bar when a version move to ent/edu or ltsc only support?
How about to change from

to something like

--87.123.175.50 (talk) 10:55, 15 May 2021 (UTC) Like! 89.247.13.202 (talk) 09:54, 26 June 2021 (UTC)

Semi-protected edit request on 1 July 2021
The support for Windows 10 Enterprise and Education version 20H1 ends 12/13/2022, NOT 2021.

https://docs.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-and-education Mbrahm06 (talk) 18:53, 1 July 2021 (UTC)
 * please look again. According to your source, the table in the article has the correct dates. Thank you for your input!  P.I. Ellsworth   ed.  put'r there 22:53, 1 July 2021 (UTC)

Do not mix up 20H1 (aka 2004) with 21H1 Version 2004 (20H1)	EOS = 12/14/2021 Version 21H1 EOS = 12/13/2022 H1 Versions generally have no longer support frame for ent/edu 2001:16B8:274:4300:A533:1183:2243:2ABC (talk) 11:22, 5 July 2021 (UTC)

Started discussion about split (again) and individual version histories
See Talk:Windows_10. Aasim (talk) 05:33, 22 October 2020 (UTC)
 * There's definitely a need to split this article up. I'm thinking maybe dividing by year or by version, and only have the current release and Dev Channel on this page. Pinging who also suggested a split above. Hayman30 (talk) 08:47, 22 October 2020 (UTC)
 * I agree. I propose splitting into an article containing 1507, 1511, and 1607, and articles for each year, with the latest year also having the Dev and Beta channels, somewhat like you proposed. Herbfur (talk) 15:45, 22 October 2020 (UTC)


 * I don't agree with your move from Windows 10 version history (version 1507) to Windows 10 version 1507, since it wasn't intended to be a separate article for version 1507, but rather an extension of Windows 10 version history. Naming the article "Windows 10 version 1507" would imply that it is an article about version 1507 (Windows 10), when in fact it's only the version history for that release, not a full article. Hayman30 (talk) 04:10, 24 October 2020 (UTC)
 * I hate to be a bother, but I don't really like the way we did the split. Splitting each version into its own article seems excessive to me. Could we maybe merge it to be 3-4 versions per page instead, so it's more convenient and notable? Herbfur (talk) 17:14, 24 October 2020 (UTC)
 * The issue is that for the past five years, Microsoft has been releasing incremental updates and builds for Windows 10 in the same manner that Apple and Google have for macOS, iOS, and Android. That means it would probably be best if the article was structured so that each individual version had its own article.  If we continue using the approach we have continued to use for the past 5 years, the size of that version history article will go out of control.  Each version also adds and removes its own features, and some versions are just incremental updates intended to patch bugs from the previous version.  And since it is unlikely that there will be a release of Windows 11 anytime soon, and since each build of Windows 10 adds its own features, I think it would be better to just briefly summarize each version in the section while liking to the article for version 1507, 1511, Anniversary, Creators, etc. Aasim (talk) 22:21, 24 October 2020 (UTC)
 * Even if we group three to four versions into one article, the list will too get excessively large at some point, so that's not really a solution either. Furthermore, how do we decide which versions should be grouped into one article? If we do it by year, that means every year when the H1 version gets archived from this article to the grouped article, we'll have to rename and move the page, since the current release will always stay on this page. For example, let's say Windows 10 versions from 2019 and 2020 are grouped together, and let's suppose version 2004 is the current release. 20H2 gets released and 2004 needs to be archived. Since the grouped article is located at "Windows 10 version history (2019)" (as only 2019 releases are included at that time), we'll have to rename it to "Windows 10 version history (2019–20)", and we need to do this every year. This is not a sustainable approach. And what happens when Microsoft decides it doesn't want to release two versions a year, are we gonna adapt to their release strategy and change our article grouping method? There really is no practical way to decide how to group the articles consistently and sustainably. By the way, Anniversary Update, Creators Update, October 2020 Update, etc. are marketing names intended to be used only for the consumer market. The official version name is "version MMYY", or "version YYHX" as it stands currently. That's how Microsoft refers to Windows 10 versions in official support documents and inside Windows 10 itself. I saw that you tried to move the splitted articles over those redirects, which would be incorrect. Hayman30 (talk) 09:22, 25 October 2020 (UTC)


 * I don't agree with the split. It helps to have the entirety of the Windows 10 version history on one page. -- DL 6443  00:53, 26 October 2020 (UTC)
 * Before the split, this article had a size of 518,871 bytes. Articles with more than 100,000 bytes "almost certainly should be divided" as per WP:SIZESPLIT. A split was long overdue, it was just a matter of how to do it. Hayman30 (talk) 11:46, 26 October 2020 (UTC)
 * If that's the case, then I propose that on the main article we have a brief description of the feature update and new features, but for each update we also have its own page (such as Windows 10 October 2020 Update) where we go into more detail about development issues and bugs (such as the file deletion bug for RS5) and have the build table. This goes for the new Dev Channel strategy as well. -- DL 6443  22:11, 26 October 2020 (UTC)
 * At the moment, the existing article and those of the most recent (i.e. supported) versions combined are still well within any sensible suggestion on maximum size. How about having this page have the main details (i.e. as much as is in their current 'couple of paragraphs and a list rather than the dropdown tables of preview builds and patches) for currently supported versions? The situation at the moment is frankly silly. Lovingboth (talk) 14:42, 16 April 2021 (UTC)
 * I can see why each major version was given its own page, given their total +500k size. But there was a lack of any text under all the sections as a result, which is silly indeed. Incidentally, the main Windows 10 article had a huge listing of every major update. I figured this would fit right in to this article as the "intro" to each update, so any other info can be kept in the individual version articles. TavianCLirette (talk) 05:09, 4 August 2021 (UTC)

Windows 11 version history
Due Windows 11 is very just a small update to Windows 10 and also could be named Windows 10 21Hx, I would like to suggest to keep also "Windows 11" in "Windows 10 version history" (wich maybe could be renamed to "Windows 10/11 version history") So not to create a new wiki entry for "version history". So e.g. forward https://en.wikipedia.org/wiki/Windows_11_version_history to https://en.wikipedia.org/wiki/Windows_10_version_history --2001:16B8:2DD:7F00:1C73:CA53:3AAA:8F0 (talk) 10:13, 20 June 2021 (UTC) I like this idea! 89.247.13.202 (talk) 09:53, 26 June 2021 (UTC)


 * As Windows 10 development and updating/upgrading is likely going to continue, you probably will get e real big confusion - to not say chaos - in this page. Mentioning it I think is ok, but fully integrating it, ... see may previous sentence. --Alien4 (talk) 11:30, 6 September 2021 (UTC)


 * Especially considering there are likely to be multiple concurrent 10 and 11 builds, and numerous 11 builds throughout its history. This page is already long enough. 11 needs a separate page. Jtrevor99 (talk) 16:11, 6 September 2021 (UTC)
 * Is windows 11 21H2? 109.252.90.174 (talk) 08:47, 6 October 2021 (UTC)

Semi-protected edit request on 13 March 2022
Preview builds of Windows 10 version 21H1 91.184.164.123 (talk) 10:17, 13 March 2022 (UTC)
 * Red question icon with gradient background.svg Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. casualdejekyll  15:21, 14 March 2022 (UTC)

Move Windows 11 builds to the Windows 11 version history
Currently, this page lists all of Windows 11's Insider Preview builds as if they are Windows 10 builds, which they're not. Microsoft's own version history refers to these builds as "Pre-Windows 11" builds, not Windows 10. Listing these versions as "Windows 10 preview builds" is inconsistent with how other versions are noted on this page; e.g.: we don't list the development builds for version 1703 as 1607 despite them identifying themselves as such. Further back, we don't list the Windows Developer Preview as something that isn't Windows 8 on that page either. It's common practice for branding to be resolved only late into development of Windows versions (or any software for that matter). This content must be restored to the correct page where it makes sense. --YannickFran (talk) 07:00, 14 June 2022 (UTC)

29.7.2022 - Windows 10 22H2 released
Update auf „22H2“: Microsoft veröffentlicht jetzt das „neueste“ Windows 10 29.7.2022 8:43 UhrSven Bauduin

https://www.computerbase.de/2022-07/windows-10-22h2-release/

-- LAZA74 (talk) 10:09, 29 July 2022 (UTC)

Semi-protected edit request on 27 September 2019
Version 1909 is 18363.387 for release preview insiders.

Semi-protected edit request on 07 May 2021
Windows 10 Insider Preview build 21376 was released on 6 May 2021.

Different colors for different release channels
The latest release should have four different colors for different release channels.

For example: Red - No longer supported Yellow - Older version, still supported Green - Latest public version Orange - Latest preview version (Release Preview) Purple - Latest preview version (Slow Ring) Pink - Latest preview version (Fast Ring) Blue - Future release

Where is Windows 10 Version 22H1 (May 2022 Update)?
We are in June 2022, but Microsoft only released Windows 10 21H2. Where is version 22H1 (May 2022 Update), which should have been released in May 2022? Why not already named 22H1 the updates since 10.0.19044.1706 [KB5013942] Release Preview Channel and public release May 10, 2022? This is correct, consistent and simple to do. Just give the name. Aainitio (talk) 22:27, 3 June 2022 (UTC)
 * Hi. Since November 2021, Microsoft stated in its blog post that there will no longer be updates released on May. Instead, they will be released in either October or November every year. Thanks.197.238.128.30 (talk) 20:19, 31 October 2022 (UTC)

Note about version 22H2
or anybody else in charge of updating the article, can anyone of you change title=October 28, 2022—KB5020953 (OS Builds 19042.2194, 19043.2194, and 19044.2194) Out-of-band to title=October 28, 2022—KB5020953 (OS Builds 19042.2194, 19043.2194, 19044.2194, and 19045.2194) Out-of-band? I recently noticed that Microsoft surreptitiously changed the headline without any notification.197.238.128.30 (talk) 20:19, 31 October 2022 (UTC)

Note about version 21H1
Hi. I've copied content from the article's Version 21H1 (May 2021 Update) to its own page, however two users reverted my edit. Therefore, I've restored it including the last update. Nevertheless, the source page (i.e this article) is protected. Can I stand by my edits? Please look into this issue.197.244.53.194 (talk) 19:00, 13 December 2022 (UTC)


 * You do not get to split an article into multiple articles just because a page is protected and you can't edit it. Hey man im josh (talk) 19:25, 13 December 2022 (UTC)
 * I have viewed your reply concerning about the consensus. Now what? Are we going to come up with another consensus? Recombine the split articles into one again? The main reason Y I had applied such edit is because it has ran out of support, as Microsoft announced, meaning that particular section will no longer be actively updated overtime. Therefore, it is useless to have that particular section displayed in the main page when there would no longer be news about that update/version.197.244.53.194 (talk) 20:09, 13 December 2022 (UTC)

Version 21H2 (November 2021 Update)
Change the tables to the below (source modifications):

Version 21H1 (May 2021 Update)
Add template. Delete both tables, Preview builds of Windows 10 version 21H1 and Public patches of Windows 10 version 21H1. Also delete the sentence which says:

No editorializing intended! Requested by:197.0.245.138 (talk) 22:11, 17 December 2022 (UTC)
 * Red information icon with gradient background.svg Not done for now: please establish a consensus for this alteration before using the template.  casualdejekyll  17:54, 19 December 2022 (UTC)
 * , a consensus had been reached before I made this request. They decided to divide the article into many, except for the latest version. Plz, double-check the archive talk pages which are above the table of contents.102.159.121.91 (talk) 04:19, 20 December 2022 (UTC)
 * Red information icon with gradient background.svg Not done for now: Per casualdejekyll comments above. And also see Articles for deletion/Windows 10 version 21H1.  — Paper9oll  (🔔 • 📝)  04:38, 23 December 2022 (UTC)

Move discussion in progress
There is a move discussion in progress on Talk:IOS version history which affects this page. Please participate on that page and not in this talk page section. Thank you. —RMCD bot 17:48, 23 December 2022 (UTC)

Revert vandalism by user WikiLive 01
The last edit done by user WikiLive 01 (Revision as of 02:19, 13 January 2023) is vandalism that hasn't been reverted 10 days later. Lumaras (talk) 01:33, 23 January 2023 (UTC)


 * I've undone the edit, as it appears to be unsourced speculation. Herbfur (Eric, He/Him) (talk) 04:00, 23 January 2023 (UTC)

Possible protection
I am requesting this page to be temporarily protected.197.244.102.196 (talk) 16:11, 6 May 2023 (UTC)

Another edit request
Please, do not use redirects. Use official pages. Change to  .197.238.82.68 (talk) 20:06, 6 May 2023 (UTC)
 * ✅ Callme mirela &#127809; 21:01, 6 May 2023 (UTC)

Mistaken URL
This website, https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-client-roadmap-update/ba-p/380522, links to an image. Replace title=https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-client-roadmap-update/ba-p/380522 with title=https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-client-roadmap-update/ba-p/3805227 by adding the number 7 at the end of the website.197.244.87.87 (talk) 18:39, 16 May 2023 (UTC)
 * ✅  Heart  (talk) 18:41, 16 May 2023 (UTC)

Condensation of several parameters
The reason for this request has something to do with the article's size. I C this being applied to similar pages including windows 11 version history. In any case, there won't be any visual changes, just for the sake of decreasing the size of the page. Here are the changes: tags, wherever appearing, with tags (removing spaces and slashes). Requested by 197.244.135.236 (talk) 01:30, 18 May 2023 (UTC) tags, before making modifications. Using tags has four bytes, whereas has six bytes. If my request for changes gets discarded again then the size of the page will continue to increase greatly over time with the excessive use of unwanted spaces and quotation marks.197.238.159.62 (talk) 06:30, 18 May 2023 (UTC) , being copied and pasted at one line after the other. If we have 2 six-byte tags added in one month then we have 12 bytes added. On the other hand, if we have 2 four-byte tags,, added in one month then we have 8 bytes added. Thus, preventing the article to grow darn quickly in the future. How hard is this to understand? They have nothing to do with such irrelevant and invalid info about how wikimedia's servers operate.197.238.159.62 (talk) tags and how those deleted spaces before or after double or triple equal signs got added back. What I also understand is that WP:VEing does not allow an editor to change the code of WP:TEMPLATEs, WP:TAGs, WP:WIKITABLEs and etc. the user wishes to add, which is one of the reasons I prefer source editing instead.197.238.245.211 (talk) 22:01, 20 May 2023 (UTC)
 * Replace and
 * Replace scope="col" parameters, wherever appearing, with scope=col (omitting quotation marks).
 * Delete spaces before or after double equal signs (==) or triple equal signs (===) wherever appearing.
 * Red information icon with gradient background.svg Not done for now: please establish a consensus for this alteration before using the template.  —  Paper9oll  (🔔 • 📝)  03:31, 18 May 2023 (UTC)
 * When I tested the changes in the WP:SANDBOX there were a total of 806 bytes removed (eight hundred and six). Moreover, when other users add patches to the end of tables, they would copy the last patch added above them, including the
 * Wikimedia hosts a lots of severs.... as you know. If such small spaces become huge burden, oh, their reports on finical should be carefully reviewed. -Lemonaka‎  12:06, 18 May 2023 (UTC)
 * Red information icon with gradient background.svg Not done for now: Explained. -Lemonaka‎  12:06, 18 May 2023 (UTC)
 * It seems that U users don't seem to understand my points. I had to explain in details. The page gets updated twice every month, with the six-byte tag,
 * Per H:BR, it doesn't matter which break line code is used. See Help:Table for your second request and Help:Section for your third request. Callme mirela &#127809; 16:45, 18 May 2023 (UTC)
 * , I clearly do understand that whichever method works. However, do U editors care about the size of this page? If U scroll to the top of this talk page U would realize the page was previously considered for deletion by back in June 2018 due to the rapid growth of the article, in which  and  suggested that the article be split, which eventually did happen.
 * The other problem is the amount of extra spaces and punctuations, which is the whole point of my doggone request, have been overused from time to time. A former editor,, was the only user who came up with solutions to decrease the page size. Here ®️ some of its contributions to the article:
 * special:diff/852745230
 * special:diff/852742080
 * special:diff/857741064
 * special:diff/852168347
 * The above changes cleared over two kilobytes that time without even making any single visual change.197.244.236.124 (talk)
 * Please stop removing spaces on the talk page. Consensus right now, from users engaging into the conversation, is based on MOS, spaces are naturally to be included. There is no valid reason or policy to obsess over the size of the article. Additionally, please read WP:CANVASS; it is not a method to get your way. Callme mirela &#127809; 19:59, 20 May 2023 (UTC)
 * Then please stop going against multiple consensus which have been reached multiple times. We cannot change the structure of the article secretly without starting another consensus. I understand that when a consensus is reached, those rules have to be observed indefinitely, unless there's another consensus which would attempt to reverse the previous consensus. Also, I am not WP:CANVASSing.197.244.236.124 (talk) 20:49, 20 May 2023 (UTC)
 * This diff says otherwise. Consensus with this thread is that the current MOS remains, per three editors. Structure is not being changed secretly; I have no idea what tangent you're on with this. The discussion is open to the public. Furthermore, consensus is not set in stone. Callme mirela &#127809; 21:30, 20 May 2023 (UTC)
 * Seriously? The U typed? If U ®️n't kidding me, then please explain how did those tags were restored back to the original
 * @197.238.159.62@197.238.245.211 or anyone in this range, please stop your filibusters. This Wp:ER was declined per Snowball clause and more debating is just a waste of time. Sorry for not so civil. -Lemonaka‎  23:30, 20 May 2023 (UTC)
 * Excuse me? Please go through and consider my relevant points before alleging the fact that I am editing with bad faith.197.238.245.211 (talk) 23:44, 20 May 2023 (UTC)

Blunders committed by
Can any other user fix that user's mistakes?

|-valign=top July 11, 2023 The user should have added what editions are eligible to receive that patch. In this case, it is more relevant to have the above lines changed to the below lines: |-valign=top Because, according to the website attached above, the Home edition and respective Pro editions of 21H2 are no longer supported after 13 of June, 2023. Beginning July 2023, patches are available for all other editions I mentioned inside the above quote.
 * 1) In this revision, the user added the below lines:
 * style=background:#fef8c6|10.0.19044.3208
 * KB5028166
 * Release Preview Channel and public release:
 * style=background:#fef8c6|10.0.19044.3208
 * KB5028166
 * Release Preview Channel and public release: July 11, 2023
 * This update is available for Education, Enterprise, IoT Enterprise, Enterprise LTSC and IoT Enterprise LTSC only.

|style=background:#d4f4b4|10.0.19044.3208
 * 1) Also, in this revision, the user added the below lines:

July 11, 2023 which have to be replaced with the below lines: because 22H2 does not have the 10.0.19044 build no., that's for 21H2 instead. Its build no. is actually 10.0.19045.
 * KB5028166
 * Release Preview Channel and public release:
 * style=background:#d4f4b4|10.0.19045.3208
 * KB5028166
 * Release Preview Channel and public release: July 11, 2023

Kindly fix those goof-ups.41.230.202.227 (talk) 16:22, 12 July 2023 (UTC)
 * Checking. -Lemonaka‎  01:43, 13 July 2023 (UTC)
 * ✅ -Lemonaka‎  01:47, 13 July 2023 (UTC)

22H2 last update for Win10
Per https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-client-roadmap-update/ba-p/3805227 22H2 will be the last Win10 release and it will only receive monthly security updates until the end of support on 10/14/2025. Colbyringeisen (talk) 16:35, 14 July 2023 (UTC)