![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
@ ViperSnake151: I have no idea how to capitalize the title, but should you or someone with the knowledge do that? Does that require another move? The Professor123 ( talk) 02:21, 14 November 2015 (UTC)
What is a "major" update is an opinion; two articles are not needed for Windows 10 updates. That page should be merged into this one. 331dot ( talk) 14:37, 22 December 2015 (UTC)
Personally, I think at least mentioning the branch name for each release would work better (i.e. "rs1_release"). That's an actual piece of data used to designate each release series. ViperSnake151 Talk 13:58, 22 December 2015 (UTC)
So, what part of this article is the "close paraphrasing"-message actually for. I'm willing to take a look at it, but I can't find anything wrong... -- YannickFran ( talk) 21:53, 13 February 2016 (UTC)
Windows 10 is Divided by branches. After a branch reaches RTM, The major build number for that branch is fixed. Any further updates to Windows 10 on that particular branch typically includes little to no new feature; rather, they only include fixes, security updates, and quality improvements. An update to a Windows 10 branch that has reached RTM increments the OS's build's minor version number. For example:
Branch: Windows 10 Codename X Build 12345 Build 12346 build 12347 build 12348 (RTM) Build 12348.123 Build 12348.456 Build 12348.789 ... Build 12348.n
Given that adding these post RTM updates can end up causing the tables to be very long, and given that these updates do not include significant new features, do you think this article should cover the minor build versions (cumulative updates). Note that for branches that are supported by LTSB, such as TH1 branch, those branches will be supported for 10 years. This means, there will be 10 years of monthly cumulative updates. You can imagine how long the table will get with only cumulative updates.
Please discuss. — Preceding unsigned comment added by NazmusLabs ( talk • contribs) 06:07, 8 March 2016 (UTC)
We're currently keeping track of Windows 10 Mobile's version history in the Windows 10 Mobile article itself, and just like how we've split of Windows 10's version history from the Windows 10-page, I think it is reasonable to split Windows 10 Mobile's version history from that article. However, I would suggest it is being merged into this article as Mobile - theoretically - is just another edition of Windows 10 and put it under its own subsection, like "Version history: Mobile" and rename the current "Version history" to "Version history: desktop and tablet". -- YannickFran ( talk) 21:45, 13 February 2016 (UTC)
Anyone know how to make the table collapsable in the moble site? NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 04:58, 14 March 2016 (UTC)
According to the WP:NOTCHANGELOG set of rules we may only add new changes to a changelog if they can be backed up by secondary and tertiary sources due to both WP:NOTABILITY and WP:SOURCE and since my time is very little and very precious I can't search for the right sources for all entries, but I'll try to find as many as possible and I advise other editors to do so as well otherwise we'll end up with another Xbox One System Software on our hands where the entire version history/changelog was completely deleted due to only/exclusively Microsoft being used as a source. I am not saying that we should remove any references and links to the original Microsoft sources, only complementary links to other tech sites and newspapers that have also reported on these builds.
Sincerely, -- 86.81.201.94 ( talk) 22:32, 25 March 2016 (UTC)
@ Guy Harris: All other operating system version history articles already link to others.
Sincerely, -- 86.81.201.94 ( talk) 20:27, 15 April 2016 (UTC)
Correct me if I am wrong but isn't it Unix's bash or at very least Debain's bash? — Preceding unsigned comment added by DarkLight748 ( talk • contribs) 19:50, 11 April 2016 (UTC)
Here is the text from WP:NOTCHANGELOG "Exhaustive logs of software updates. Use reliable third-party (not self-published or official) sources in articles dealing with software updates to describe the versions listed or discussed in the article. Common sense must be applied with regard to the level of detail to be included." Bug fixes are a part of software updates, and the list above only prohibits bugs and excessive details, also copyright infringement.
Sincerely, -- 86.81.201.94 ( talk) 17:17, 22 April 2016 (UTC)
Each release brings significant changes that should be noted. These changes are more important than a small UI change or a new option in the settings menu. Such changes can be updates to the developer environment and APIs, major visual changes, new features and applications, and other things that Microsoft and the press highlights as new features of a release. The table of versions highlight every little changes, and, thus, the big changes get buried. Furthermore, different changes appear at different builds, making it hard to know what changes have been made for each new release.
Currently, it's hard to know what each new release brings without looking at every single builds in the table. This is why the major changes will be highlighted for each release to make it easier for readers to get an idea of each release at a glance.
I look forward to your contributions! -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 11:58, 20 April 2016 (UTC)
I propose the first one as I believe both the articles have/can have the same info; But this article, with proper modifications, can be better than the other one as this one has features organized in different branches. Chandradeep Dey ( talk) 16:45, 5 May 2016 (UTC)
Alright, I think this is getting way out of hand here. 2 sections up came the request if features should be added to every release. Kind of odd to ask when you go ahead right away, though. Anyway, not my point. I've removed all of this information for a number of reasons:
So, for the purpose these sections served, the info should be added to Features new to Windows 10, where this information belongs. -- YannickFran ( talk) 07:08, 7 May 2016 (UTC)
I've noticed the entire article goes outside the blue outlined border of Wikipedia. From the "Pre-release versions of Windows 10 codename "Threshold 2"" chart and below. I tried looking at the code to see what the problem was, and I was not able to fix it. This isn't really a major issue, but I thought I'd point it out so someone can figure out what happened. I'm on Windows 7, Google Chrome. And yes, I've cleared my cache/cookies, have the latest drivers, ran virus scans, CCleaner, re-installed everything, etc. I've also tried it on several other computers, with the same issue each time, so I know its not me. Might just be the site itself, but I haven't yet found the issue on any other article. The Professor123 ( talk) 19:45, 11 May 2016 (UTC)
When Microsoft lists "improved consistency/reliability/stability of X", should that be included under a new feature, or a bug fix? I've been including those as fixes, but someone has been moving them to features. The Professor123 ( talk) 07:54, 29 June 2016 (UTC)
This is ridiculous. The article now says itself that 10240 is not the RTM, yet it insists on calling it an RTM because some journos are calling it like that. So what, if people started calling Windows "Doors", we'll be renaming this article "Doors 10 version history"? The term "RTM" was dropped after Windows 8.1. Not to mention that you'll also find plenty of people calling 10586 a RTM and whatever the stable Anniversary Update will be is also called out as RTM. Because many people call it that, doesn't make it its official name. Additionally, this has NOTHING to do with a Neutral Point of View. Well... it has now, because you're putting in journos subjective PoV as a trueth. — Preceding unsigned comment added by YannickFran ( talk • contribs) 07:56, 23 June 2016 (UTC)
Shouldn't we better split up the table into "Threshold 1", "Threshold 2" and "Redstone 1". That way we have a clear place to add some information about every update as we do with iOS and Android's pages on this matter and we don't end up with a way to long table. -- YannickFran ( talk) 14:50, 2 January 2016 (UTC)
If a build is released to the Release Preview ring, but not released to outsiders, should they still be placed under the "public release" charts? I would think they wouldn't be, but previous builds under that description have been being added under the "public releases" graphs. The Professor123 ( talk) 02:35, 10 August 2016 (UTC)
See Windows 10 Latest Preview: Isn't the version supposed to be 1703? Why isn't the page updated? Can you update the page? 220.255.100.134 ( talk) 13:05, 16 October 2016 (UTC)
The cumulative updates for Windows 10 are blatant copy-paste of the KB articles' descriptions of these updates. They need to be rewritten in original manner and properly summarized. We do not need to list every single bug fixes. Just highlights for each cumulative updates is sufficient. Wikipedia is not meant to be a detailed log of software updates. It is designed to give readers a summery. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 06:39, 16 March 2016 (UTC)
Anyone know whats going on with this? Why does wiki think it's a copy right violation? — Preceding unsigned comment added by Gh0sti100 ( talk • contribs) 20:49, 3 November 2016 (UTC)
Prior content in this article duplicated one or more previously published sources. Copied or closely paraphrased material has been rewritten or removed and must not be restored, unless it is duly released under a compatible license. (For more information, please see "using copyrighted works from others" if you are not the copyright holder of this material, or "donating copyrighted materials" if you are.)
For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or published material; such additions will be deleted. Contributors may use copyrighted publications as a source of information, and, if allowed under fair use, may copy sentences and phrases, provided they are included in quotation marks and referenced properly. The material may also be rewritten, providing it does not infringe on the copyright of the original or plagiarize from that source. Therefore, such paraphrased portions must provide their source. Please see our guideline on non-free text for how to properly implement limited quotations of copyrighted text. Wikipedia takes copyright violations very seriously, and persistent violators will be blocked from editing. While we appreciate contributions, we must require all contributors to understand and comply with these policies. Thank you. — Diannaa 🍁 ( talk) 20:25, 4 November 2016 (UTC)
I would like to point out that other version histories do the exact same thing. Why is this one being singled out? In addition, development versions listed in this article are NOT taken directly from Microsoft blog posts, only cumulative updates to released versions are. For the infringing parts, surely re-wording and/or more thorough citations would solve the issue? I don't believe removing all of the tables on this page was in any way necessary. (Please do not delete this anonymous comment, this situation is infuriating me.) — Preceding unsigned comment added by 2601:19A:4101:DD42:35C9:BBAC:2E72:3B59 ( talk) 22:38, 5 November 2016 (UTC)
Let's clear up 2 things here: Why is "Version 1511, November Update" 'too long'? Every other OS is getting these kind of titles, take a look at MacOS version history and Ubuntu version history, they all include version and name in the titles that are often longer. Second, 1507 is an official version and Microsoft has been referencing to the first version of Windows 10 with 1507 ever since 1511 was released.
Since these version numbers are the only thing that actually resemble something you can put in chronological order, it makes no sense to leave the mout of the titles. -- YannickFran ( talk) 11:05, 13 November 2016 (UTC)
winver
) and didn't see 1507 there. I believe the "official" criteria is appearing in the software itself.![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The anniversary update came out for LTSB in 2016. 66.69.252.169 ( talk) 10:01, 2 December 2016 (UTC)
Thanks SO MUCH to the admin who deleted everything for the sake of the article! I am genuinely thankful. While it is a shame that a lot of the non-copyrighted work got deleted, the outcome has been better than the risk of the entire article getting deleted and stuck behind a autocracy of appeal for restoration.
I, and many others, have spent hours writing dozens and dozens of bullet points in completely original format, making sure to not violate copyright. And while it pains me to see all that work go to waste, I acknowledge that hundreds of other bullet points were, indeed, copy and pasted from Microsoft blog posts. And trying to find what was stolen work versus what was not was going to be a massive pain and a waste of time, with a huge risk of having the article deleted.
Aso, again, I think the admin who saved the article. :)
Now, here's what we are going to do. We don't give up. We are going to do this correctly. From now on, we are going to err on the side of caution. It is better to have less, but originally written, information, rather than full breadth of information but copy-pasted or too closely paraphrased information from another source.
So, here's the guideline: List the released builds on the tables, with citation from non-Microsoft sources (adding MS sources in addition, if desired), BUT DO NOT ADD NOTES unless you have the time to write them yourselves. It's better to leave the notes section blank than plagiarizing. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 20:06, 6 November 2016 (UTC)
Candid question: since recently I can no longer see the list of Version 1607 build numbers. Why is this? — Preceding unsigned comment added by Jacques.999 ( talk • contribs) 09:32, 30 November 2016 (UTC)
Why keeping 1607 update are copyright violation. I think micro. will become happy if we keep they're update history? why not? At Last ... ( talk) 17:13, 8 December 2016 (UTC)
More than a defense of copyright violations, it looks like a boycott on MS. This page used to be the best source to keep track of the improvements on Windows 10 Pc and Mobile. — Preceding unsigned comment added by Judiospi ( talk • contribs) 18:11, 12 January 2017 (UTC)
Is this correct?
Version 1607 (Anniversary Update)
Latest Version 10.0.14393 is marked as Old and not as Current stable version. -- MTimann ( talk) 13:46, 13 March 2017 (UTC)
It took me quite a lot of time to look for the right sources and references and regarding early cumulative updates are harder to attain and are often "hid" in articles about more than one update (often still including Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, and Microsoft Windows 8.1 updates in the same articles), anyhow I've tried to add as much as possible containing the changes mentioned in the changelog so as of now this article fully fits what's permitted within WP:NOTCHANGELOG (although the way it's written needs to fit a more encyclopedic style).
To any new additions to the changelog please add non-Microsoft sources complementary to the original source, on the day an update is released finding news articles relating to the update are relatively easy to find, but if you wait too long they'll drown in various blogs and fora discussing the update at hand, so please work swift, and work in accordance to WP:SOURCE.
Thank you for taking the time to read this, and thank you in advance for adding secondary and tertiary sources to your contributions to this page.
Sincerely, -- 86.81.201.94 ( talk) 15:33, 27 March 2016 (UTC)
@ 111.123.144.58: Could you please explain why you keep removing the Windows Central source? It is not an invalid source. Thank you. Hayman30 ( talk) 10:40, 17 April 2017 (UTC)
@ 88.196.91.6: You changed the slow ring date from March 29, 2017 to April 11, 2017, but that is wrong. Please see the original source, "UPDATE 3/29: We have released Windows 10 Insider Preview Build 15063.2 for Mobile to Windows Insiders in the Slow ring.", the build for mobile was released to insiders on March 29. Your source simply verifies that it will be rolling out to the public on April 11, but the tabel you are changing is Preview versions of Windows 10 Redstone 2, you made a mistake. Hayman30 ( talk) 11:05, 17 April 2017 (UTC)
The app updates included in the builds were actually bundled with the said builds and should be included. The fact that an update or an app is ported to an older release is not a reason to not include that update in the release of the build in which it originates. It's like saying Internet Explorer 7 should not be included with Windows Vista release notes because it was later brought to Windows XP. Same with IE8, IE10, and IE11. Furthermore, some app updates do not get ported back to older versions due to technology limitations (for instance the UWP skype app which is exclusive to RS1 and not TH2 release, Paint 3D which is exclusive to RS2, and updated Windows Store in RS1). So even if we did agree to remove app updates that eventually gets ported (which I wholeheartedly disagree with), you would have to find individual updates and see if they were ported or not.
The same is true for extensions. Some extensions, such as Turn off the Lights on Edge, is ONLY available in RS2 builds because the developer stated that it requires new technology in the browser not present in RS1 (which can be heard in The Sam's Report podcast).
This also applies to updates. Some updates, such as Windows Update Cleanup from Windows 8, are ported to older Windows Releases. That doesn't mean we don't include the update in the release notes of the build it originates from.
Thank you. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 17:45, 13 November 2016 (UTC)
Alright folks, version 1507 isn't EOL. It is no longer supported in the Semi Annual Pilot and Sime Annual Broad channels (the CB and CBB, for those on the old naming) but it is still supported on the Long-Term Support Channel for years to come. Support for version 1507 isn't expected to end until 2025. Another update for it will be released this tuesday... -- YannickFran ( talk) 14:15, 11 June 2017 (UTC)
So, now the argument has come up that LTSB "does not apply here" because "It's basically ended for consumers". Why? LTSB is a branch as much as any others are. Since when has Wikipedia ever made a difference between consumer-facing branches and non-consumer-facing branches? Not to mention that the Fast Ring, Slow Ring, Release Preview Ring and Semi Annual Broad Channel - branches that are all included in this page - aren't for consumers either. This is a wiki, not a consumers information guide. Nobody is removing information about Enterprise editions of Windows because they aren't for consumers either, this isn't any different. On June 13th, Microsoft will release another update for 10240 just like they've done every month. Are we now intentionally going to be incomplete and leave these builds out, ignoring about 8 years of version history for 1507 (and future LTSC releases like 1607)?-- YannickFran ( talk) 17:31, 11 June 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
111.123.159.25 ( talk) 11:57, 23 June 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Request to remove bad quality edits by @ Hayman30: that doesn't seem to help the article, primarily fails WP:SOURCE as these edits were heavily based on Microsoft's own websites and uses plagiarized content from Microsoft. 42.112.154.124 ( talk) 01:54, 14 July 2017 (UTC)
{{
edit semi-protected}}
template.
jd22292 (Jalen D. Folf) (
talk)
02:35, 14 July 2017 (UTC)117.135.235.17 ( talk) 08:01, 18 July 2017 (UTC)
User:Hayman30 I'm not sure what you are trying to achieve here. 1709 is not the current version of Windows 10, it is still in active development and there for the current preview release, just like the 1803 builds that are rolling out as well. 2 versions can be in development at the same time, that doesn't make the first one that is set to be released an "Old version, still supported", it's still the "Latest preview version" of Redstone 3. Having said that, stop complaining about "Taking it to talk", you're the one not doing that, this discussion is already going on Template_talk:Windows_10_versions, at this point, you're just trying to escalate this into an edit war. -- YannickFran ( talk) 14:45, 14 September 2017 (UTC)
It's odd to have two latest version. Also, Version 1709 is still in final development and still not yet released to Release Preview Ring. I think it should be categorized into latest preview version. Hakurei Phomu ( talk) 13:54, 21 September 2017 (UTC)
Windows 10 Fall Creators Update is actually Autumn Creators Update for the UK
https://www.windowscentral.com/microsoft-will-call-windows-10s-next-update-autumn-creators-update-uk
Microsoft will regionally adjust the name of the Windows 10 Fall Creators Update in the UK, calling it the "Autumn Creators Update" instead — Preceding unsigned comment added by Jonathan McEvoy ( talk • contribs) 13:51, 28 September 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
spelling "Creaters" -> "Creators"
Version 1709 (Fall Creators Update)
.... The Fall Creaters Update (Version 1709, 10.0.16299) was officially release on October 17, 2017.
Version 1709 (Fall Creators Update)
.... The Fall Creators Update (Version 1709, 10.0.16299) was officially release on October 17, 2017.
108.235.242.4 ( talk) 04:24, 18 October 2017 (UTC)
.... The Fall Creators Update on Mobile (Version 1709, 10.0.15254.1) was available to Release Preview, and probably official release on October 17, 2017. 1000mm ( talk) 23:43, 18 October 2017 (UTC)
Is this a reliable source for saying that the next update of Windows 10 is called the 2018 Update?? If not, please explain:
https://theleaker.com/windows-10-2018-update-preview-is-redstone-4/
Georgia guy ( talk) 20:03, 26 October 2017 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on Windows 10 version history. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 5 June 2024).
Cheers.— InternetArchiveBot ( Report bug) 01:11, 21 November 2017 (UTC)
Microsoft updated the final dates of support for the Windows 10 Semi-Annual Channel (SAC): https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet#update
This page is already properly footnoted. Simply requesting that the dates listed in the table are updated to match. Here are the specific changes to the final dates of support for SAC:
Hope I'm raising this properly, this is my first Wikipedia edit suggestion. Thanks.
-- Ericalanwhitney ( talk) 13:41, 2 February 2018 (UTC)
Table should get new column at "support until" isn't it ?
Suggestion:
Support until | ||
---|---|---|
SAC (Home/Pro) |
SAC (Ent/Edu) |
LTSC |
-- 83.135.150.160 ( talk) 12:21, 3 February 2018 (UTC)
Maybe also another Column for Mobile ?
-- 83.135.150.160 ( talk) 12:23, 3 February 2018 (UTC)
https://thewincentral.com/windows-10-redstone-4-spring-creators-update-version-1803/
Georgia guy ( talk) 19:38, 3 February 2018 (UTC)
Can we please add a feature for version 15254.248 that it breaks the ability to open pdf files in Edge (only default app possible) which results in any pdf from an app which doesn't give you the option to download being unopenable. 103.217.166.220 ( talk) 00:00, 2 March 2018 (UTC)
In the past, Windows Server was not included in the list becasue it wasn't updated as a continuous release as was Windows 10 & Windows 10 mobile.
There was only Windows Server 2016, and it was akin to Windows 7, Windows Vista, Server 2008 RT, etc. But now, it's different.
Server has now adopted the Software as a service model and has aligned itself with Windows 10 client. There's now RS3, RS4, and RS5 releases either public or scheduled.
There needs to be a consensus on whether server should be included.
There's mobile version history. Why not server.
Thoughts, please.
NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 23:56, 22 March 2018 (UTC)
I like the idea of creating a new article for Server Semi-Annual channel @ Warren suggested. That article can have a Version History heading that can list the builds for the server, using the tables following the template of this page. This will work like how Xbox OS version history, or iOS version history does.
Although these releases are essentially Windows 10 builds with the server stack added in on it and some client features removed, they are not labeled as Windows 10, and I have come around to the fact. Perhaps my idea initial idea of adding a server section to this article, although server is an edition of Windows 10 behind the scenes, might not be the best. Plus, adding server here will only substantially increase the length of this already long article, with new build releases only adding to the problem.
So, any objections? Ideas?
Current latest mobile version for public and insider ring is 10.0.15254.490 updated on 11 july 2018 Shubdragon ( talk) 13:04, 17 July 2018 (UTC)
windows 1809 has been recalled so currently has no release date the latest release candidate was 30th October ( https://support.microsoft.com/en-us/help/4464619)
On July 25, 2018, Microsoft officially released the first preview build of version 1903 (codename 19H1) to Insiders in the exclusive Skip Ahead ring (such as myself). The template for the Overview chart should be edited as such to reflect the changes, as well as updating the version 1809 build to 17723, as it has also been released to Insiders in the Fast ring. — Preceding unsigned comment added by TheTwoEyedMan ( talk • contribs) 23:24, 25 July 2018 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Under section Version 1809, please add version 10.0.17763 (Fast ring on September 18, 2018 at the bottom of the table. Here's the source:
[1]
86.22.8.235 (
talk)
17:37, 18 September 2018 (UTC)
Already done 86.22.8.235 ( talk) 18:39, 20 September 2018 (UTC)
Dear wiki-editors,
Why — after the
recent AfD proposal — the suggested splitting of this article has not yet been made?
It seems to be a very good solution. Current article needs to contain only summary information, such as the introductory part with a "overview table" (both already present).
Complementary and detailed data can effectively, without any prejudice, be directed to specific articles, created with an appropriate argument (year, edition / version, etc.).
Aainitio (
talk)
15:00, 18 June 2018 (UTC)
Any plan to add build history numbers to old versions (1607, 1703 1709...) This would be a great addition to keep everything in one place. Witkoskijp ( talk) 15:20, 20 August 2018 (UTC)
The opening sentence of this article currently reads " Windows 10 is an operating system developed by Microsoft." This obviously does not conform with the manual of style. The article title is "Windows 10 version history", not "Windows 10", so "Windows 10" should not be in bold. And even if it was correct for it to be in bold, it should not contain a link according to MOS:BOLDAVOID. It's depressing to note that the article has contained this error since it was created almost three years ago. 37.152.231.45 ( talk) 20:44, 9 October 2018 (UTC)
The Windows 10 rings is not really clear. They says build 1607 is still supported, but the consumer version isn't supported anymore. I think is is a idea to split the support in consumer and business. In "Latest build" seperate collums for consumer and business. Maybe it is possible to add the collors in the support dates instead of in "Latest build" The current design is really confusing. ( 195.35.231.195 ( talk) 10:45, 23 January 2019 (UTC)) — Preceding unsigned comment added by 195.35.231.195 ( talk) 10:42, 23 January 2019 (UTC)
Wikipedia has a clear policy on this category of articles, and whether is should be deleted. See Wikipedia:Articles for deletion/Google Chrome OS version history for an example of a past discussion. -- Kaledomo ( talk) 05:09, 13 March 2019 (UTC)
I'm request to split this page as a separate pages, because the page becoming heavier for every new information of new Windows versions. But probably we need choose between 2 ways.
1. New arcticle for every major update, like ..." Windows 10 Fall Creators Update", " Windows 10 April 2018 Update", " Windows 10 October 2018 Update", " Windows 10 19H1"...
2. New arcticle every 3 years (or less or more), like "Windows 10 version history (2015-2017)", "Windows 10 version history (2018-2020)", "Windows 10 version history (2021-2023)"... We already made simular of these as on Timeline of the Syrian Civil War or something like that.
So, what do you think? -- 81.200.16.229 ( talk) 11:52, 26 December 2018 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Windows 20H1 is now available for Fast Ring users
Source: https://twitter.com/windowsinsider/status/1116024531947147265 Selman N. Tabet AKA Chaos The Slayer 19:20, 10 April 2019 (UTC) — Preceding unsigned comment added by SelmanTabet97 ( talk • contribs) 20:20, 10 April 2019 (UTC)
Windows 10 has been dubbed as a service by Microsoft for almost five years now, with major updates building off of previous updates. Which is the reason why I am suggesting something that Mac articles have done: add articles about each Windows version, along with added features, removed features, reception, etc. Here are a few examples of what I am talking about: macOS Sierra, macOS High Sierra, macOS Mojave, OS X Mavericks.
Before Windows 10, the Windows OS only received paid upgrades, including Windows 8.1 to 10, Windows 7 to 8/8.1, Windows Vista to 7, and Windows XP to Vista. Windows 10 as a service removes the payments for these upgrades dubbed "feature updates". In fact, Windows 10 has significantly changed since the initial launch.
Given the information I provided, does Windows 10 deserve its own version articles? (Feel free to copy to WP:RFC or such) Awesome Aasim 03:31, 1 May 2019 (UTC)
Previously thought to be a 19H2 build, Microsoft surprised us by releasing a build for an update scheduled to launch in 2020. They claim that some features in the update need additional testing.
What are we going to do in this situation? Microsoft hasn’t even released a build of 1909 (19H2) yet. Any ideas? NotYourAbnormalJoe ( talk) 20:39, 14 February 2019 (UTC)
I saw a new at origo.hu, that there could be only 1 version in '19. Alfa-ketosav ( talk) 18:24, 5 May 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Error in KB number for: Version 1809 (October 2018 Update) / Public patches of Windows 10 version 1809 Currently reads: 10.0.17763.503 [619] / KB4495667 / Public release: May 14, 2019 Should read: 10.0.17763.503 [619] / KB4494441 / Public release: May 14, 2019 stu Bigstu2019 ( talk) 08:00, 15 May 2019 (UTC)
Shouldn't said template be moved from Windows 10 version history#Rings down to Windows 10 version history#PC version history since said template relates more to the latter than the former? -- Some-username-here1 ( talk) 20:00, 6 June 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Version 1903 (May 2019 Update) The Windows 10 May 2019 Update[651] (also known as version 1903[652] and codenamed "19H1"[606]) is the seventh major update to Windows 10 and the first to use a more descriptive codename (including the year and the order released) instead of the "Redstone"[653] or "Threshold" codename. The first preview was released to Insiders who opted in to the exclusive Skip Ahead ring on July 25, 2018. The update began rolling out on May 21, 2019.[654] Notable changes in the May 2019 Update include:[655][656]
The latest OS Build version is 18362.207 [June 27, 2019]
Edit request reason: The above paragraph is edited to add some more new features of Windows 10 1903 May 2019 update. Also the latest OS build version citing the sources. This is to keep Windows 10 users informed about a more vast set of changes made in the new version update. Palla Sridhar 16:06, 28 June 2019 (UTC) — Preceding unsigned comment added by Shreen2008 ( talk • contribs)
References
Not done The edit request has already been declined. Please do not change it back to "answered=no" until you have achieved consensus. --
kingboyk (
talk)
22:17, 20 July 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The latest current versions are 10.0.18362.356 and 10.0.18363.356 as of September 10, 2019. [2] ---- 194.207.146.167 ( talk) 07:08, 11 September 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Version 1903 is 18362.385 for release preview and version 1909 is 18363.385 for release preview. Harshmoney ( talk) 12:43, 24 September 2019 (UTC)
References
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Public patches of Windows 10 version 1809 10.0.17763.806[705] KB4519338 Public release: October 8, 2019 change to: 10.0.17763.805 192.33.238.48 ( talk) 14:09, 17 October 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
1909 preview (the one with 18362 builds) bar below section "PC version history" should be red (no support) instead of yellow, since 1909 is released, isn't it?-- 2001:16B8:201:4400:C54F:A300:E187:E9F2 ( talk) 08:44, 16 November 2019 (UTC)
As in the article also 20H1 is in there, is there any official source - i know, it's only a code name, nevertheless - what the H stands for ... "heat"? Thank you. --
Alien4 (
talk)
12:01, 13 November 2019 (UTC)
Q = Quarter of a year ( 1~4 ) and H = Half of year ( 1~2)
so in case of 20H1 = in 1st half of the year 2020. XX03 and XX09 was for the months March and September, but this often do not fit with released date.
--
2001:16B8:201:4400:C54F:A300:E187:E9F2 (
talk)
08:49, 16 November 2019 (UTC)
20H2 Codname: Manganese 19541 — Preceding unsigned comment added by 2A02:8108:8E80:3338:DC3C:4A0B:AD80:12E9 ( talk) 14:25, 13 January 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Adding 20H2 row with link to article in Rings head Nikhilpal2705 ( talk) 07:43, 23 January 2020 (UTC)
Recently this page has crossed the 2048000 "Post-expand include size" limit enforced by the web server's software. See Help:Template#Template_limits and Category:Pages where template include size is exceeded for details.
The result is that templates that are at the bottom of the page will not display correctly.
I recommend splitting off another page identical to this one to cover "PC version history" versions 1507 through 1703. Why those dates? Except for LTSC (formerly named LTSB), those versions are not supported at all. davidwr/( talk)/( contribs) 21:31, 9 March 2020 (UTC)
[ [3]] Please add -- 2A02:8071:8199:FC00:61E2:ACB6:3BB9:53C1 ( talk) 13:40, 15 April 2020 (UTC)
Hi
Is it possible to change the codename for 20H1 to 'Vibranium'? See https://www.thurrott.com/windows/windows-10/190138/windows-10s-next-major-updates-will-be-codenamed-vanadium-vibranium. Also, 19H1 & 19H2 were still named Redstone (possibly 6 & 7), they still had 'rs' in the build strings. Wagnerp16 ( talk) 15:59, 30 April 2020 (UTC)
People are looking for information on particular versions; they do not want the entire article to be loaded. They want to know how a particular version was received by the general public. They do not want very general information like that in
Windows 10 or here.
A
a
s
i
m
01:13, 7 May 2020 (UTC)
Possibly divide the article into 15xx, 16xx, 17xx, etc. e.g. in pairs of two versions rather than each version separately as that would kind of be too much articles as there is not particularly much to say/difference between each version.
LukaAndjelkovic (
talk)
21:21, 7 May 2020 (UTC)
I agree that the versions could be paired, especially with the new major-minor cadence that Microsoft is using. I don't think splitting the article would be wise, though. It's useful to have a single page with the whole release history.
Herbfur (
talk)
22:46, 7 May 2020 (UTC)
I would like to see the 'windows 10 versions' table kept intact
Choman2 (
talk)
22:46, 10 May 2020 (UTC)
I would also like to see the table kept intact. I use it as reference on a regular basis because it is succinct (and easily bookmarked) in a way that Microsoft's own documentation is not.--
Jasebaese (
talk)
13:30, 19 May 2020 (UTC)
Wiki-Friends,
I understand the concern with the size of the article
Windows 10 version history in its current form [2020.05.18].
The suggestion for partitioning subsets can be useful in this case.
However, I recommend that redirection from
Windows 10 version history is present in all sub-articles.
Even more: I recommend that the table contained in
Windows_10_version_history # Rings be present in all sub-articles.
For... Viewing THE WHOLE... can be very important and useful.
Wiki-Success!
Aainitio (
talk)
11:57, 18 May 2020 (UTC)
Currently, any machine using an older graphics card based on Nvidia Tesla architecture is compatibility locked out of installing 2004, and it is unclear whether that will ever change. The issue is Stop codes (BSODs) with drivers older than 358.00 due to an incompatibility, and Tesla architecture cannot install drivers newer than version 342.01. I'm just browsing this article for the first time so am wondering if this would be an appropriate add anywhere and if so, where. (This is the only potentially permanent lockout I see on the list, but there may be others I missed.) Jtrevor99 ( talk) 02:57, 2 June 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
2001:16B8:27B:C800:D500:746C:4AA3:7A1E ( talk) 11:22, 7 June 2020 (UTC)
I suggest to fwd to latest /info/en/?search=Windows_10_version_history_(2019%E2%80%932020) not to oldest-- 2001:16B8:27B:C800:D500:746C:4AA3:7A1E ( talk) 11:22, 7 June 2020 (UTC)
Currently, if you open /info/en/?search=Windows_10_version_history you will be forwarded to /info/en/?search=Windows_10_version_history_(2015%E2%80%932016)
IMHO the forward target should changed from /info/en/?search=Windows_10_version_history_(2015%E2%80%932016) to /info/en/?search=Windows_10_version_history_(2019%E2%80%932020)
Cause the older history should be less important so the latest should have the priority. -- 2001:16B8:27B:C800:F4CE:FC31:15AD:1 ( talk) 18:30, 7 June 2020 (UTC)
After a long discussion, I have taken action at last and split the article into three, one for updates released from 2015 to 2016, one for 2017 to 2018, and one for 2019 to 2020 (which also includes rolling Fast Ring builds). I have also updated the templates to reflect the split. The original link redirects to the 2015 to 2016 updates. Harshmoney ( talk • contribs) 17:05, 4 June 2020 (UTC)
As of 08:31, 18 June 2020 (UTC), there are 950 references in the article. This is rather long, so is it possible someone build a collapsible around the references section? Thanks -- SlitherioFan2016 ( Talk/ Contribs) 08:31, 18 June 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hi, i want to edit some typos in this page, there are too much typos there! Chris Ducker ( talk) 12:00, 21 June 2020 (UTC)
. Chris Ducker ( talk) 12:01, 21 June 2020 (UTC)
This is a very good and helpful article, but I'd like to have "build X = version Y" dependency in the chart; I think it would make nailing down disparate identifiers much easier than parsing the detailed writeups. — Preceding unsigned comment added by 96.91.22.118 ( talk) 17:48, 17 July 2020 (UTC)
ETA: NVM; I guess I was blind. — Preceding unsigned comment added by 96.91.22.118 ( talk) 17:50, 17 July 2020 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
@ ViperSnake151: I have no idea how to capitalize the title, but should you or someone with the knowledge do that? Does that require another move? The Professor123 ( talk) 02:21, 14 November 2015 (UTC)
What is a "major" update is an opinion; two articles are not needed for Windows 10 updates. That page should be merged into this one. 331dot ( talk) 14:37, 22 December 2015 (UTC)
Personally, I think at least mentioning the branch name for each release would work better (i.e. "rs1_release"). That's an actual piece of data used to designate each release series. ViperSnake151 Talk 13:58, 22 December 2015 (UTC)
So, what part of this article is the "close paraphrasing"-message actually for. I'm willing to take a look at it, but I can't find anything wrong... -- YannickFran ( talk) 21:53, 13 February 2016 (UTC)
Windows 10 is Divided by branches. After a branch reaches RTM, The major build number for that branch is fixed. Any further updates to Windows 10 on that particular branch typically includes little to no new feature; rather, they only include fixes, security updates, and quality improvements. An update to a Windows 10 branch that has reached RTM increments the OS's build's minor version number. For example:
Branch: Windows 10 Codename X Build 12345 Build 12346 build 12347 build 12348 (RTM) Build 12348.123 Build 12348.456 Build 12348.789 ... Build 12348.n
Given that adding these post RTM updates can end up causing the tables to be very long, and given that these updates do not include significant new features, do you think this article should cover the minor build versions (cumulative updates). Note that for branches that are supported by LTSB, such as TH1 branch, those branches will be supported for 10 years. This means, there will be 10 years of monthly cumulative updates. You can imagine how long the table will get with only cumulative updates.
Please discuss. — Preceding unsigned comment added by NazmusLabs ( talk • contribs) 06:07, 8 March 2016 (UTC)
We're currently keeping track of Windows 10 Mobile's version history in the Windows 10 Mobile article itself, and just like how we've split of Windows 10's version history from the Windows 10-page, I think it is reasonable to split Windows 10 Mobile's version history from that article. However, I would suggest it is being merged into this article as Mobile - theoretically - is just another edition of Windows 10 and put it under its own subsection, like "Version history: Mobile" and rename the current "Version history" to "Version history: desktop and tablet". -- YannickFran ( talk) 21:45, 13 February 2016 (UTC)
Anyone know how to make the table collapsable in the moble site? NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 04:58, 14 March 2016 (UTC)
According to the WP:NOTCHANGELOG set of rules we may only add new changes to a changelog if they can be backed up by secondary and tertiary sources due to both WP:NOTABILITY and WP:SOURCE and since my time is very little and very precious I can't search for the right sources for all entries, but I'll try to find as many as possible and I advise other editors to do so as well otherwise we'll end up with another Xbox One System Software on our hands where the entire version history/changelog was completely deleted due to only/exclusively Microsoft being used as a source. I am not saying that we should remove any references and links to the original Microsoft sources, only complementary links to other tech sites and newspapers that have also reported on these builds.
Sincerely, -- 86.81.201.94 ( talk) 22:32, 25 March 2016 (UTC)
@ Guy Harris: All other operating system version history articles already link to others.
Sincerely, -- 86.81.201.94 ( talk) 20:27, 15 April 2016 (UTC)
Correct me if I am wrong but isn't it Unix's bash or at very least Debain's bash? — Preceding unsigned comment added by DarkLight748 ( talk • contribs) 19:50, 11 April 2016 (UTC)
Here is the text from WP:NOTCHANGELOG "Exhaustive logs of software updates. Use reliable third-party (not self-published or official) sources in articles dealing with software updates to describe the versions listed or discussed in the article. Common sense must be applied with regard to the level of detail to be included." Bug fixes are a part of software updates, and the list above only prohibits bugs and excessive details, also copyright infringement.
Sincerely, -- 86.81.201.94 ( talk) 17:17, 22 April 2016 (UTC)
Each release brings significant changes that should be noted. These changes are more important than a small UI change or a new option in the settings menu. Such changes can be updates to the developer environment and APIs, major visual changes, new features and applications, and other things that Microsoft and the press highlights as new features of a release. The table of versions highlight every little changes, and, thus, the big changes get buried. Furthermore, different changes appear at different builds, making it hard to know what changes have been made for each new release.
Currently, it's hard to know what each new release brings without looking at every single builds in the table. This is why the major changes will be highlighted for each release to make it easier for readers to get an idea of each release at a glance.
I look forward to your contributions! -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 11:58, 20 April 2016 (UTC)
I propose the first one as I believe both the articles have/can have the same info; But this article, with proper modifications, can be better than the other one as this one has features organized in different branches. Chandradeep Dey ( talk) 16:45, 5 May 2016 (UTC)
Alright, I think this is getting way out of hand here. 2 sections up came the request if features should be added to every release. Kind of odd to ask when you go ahead right away, though. Anyway, not my point. I've removed all of this information for a number of reasons:
So, for the purpose these sections served, the info should be added to Features new to Windows 10, where this information belongs. -- YannickFran ( talk) 07:08, 7 May 2016 (UTC)
I've noticed the entire article goes outside the blue outlined border of Wikipedia. From the "Pre-release versions of Windows 10 codename "Threshold 2"" chart and below. I tried looking at the code to see what the problem was, and I was not able to fix it. This isn't really a major issue, but I thought I'd point it out so someone can figure out what happened. I'm on Windows 7, Google Chrome. And yes, I've cleared my cache/cookies, have the latest drivers, ran virus scans, CCleaner, re-installed everything, etc. I've also tried it on several other computers, with the same issue each time, so I know its not me. Might just be the site itself, but I haven't yet found the issue on any other article. The Professor123 ( talk) 19:45, 11 May 2016 (UTC)
When Microsoft lists "improved consistency/reliability/stability of X", should that be included under a new feature, or a bug fix? I've been including those as fixes, but someone has been moving them to features. The Professor123 ( talk) 07:54, 29 June 2016 (UTC)
This is ridiculous. The article now says itself that 10240 is not the RTM, yet it insists on calling it an RTM because some journos are calling it like that. So what, if people started calling Windows "Doors", we'll be renaming this article "Doors 10 version history"? The term "RTM" was dropped after Windows 8.1. Not to mention that you'll also find plenty of people calling 10586 a RTM and whatever the stable Anniversary Update will be is also called out as RTM. Because many people call it that, doesn't make it its official name. Additionally, this has NOTHING to do with a Neutral Point of View. Well... it has now, because you're putting in journos subjective PoV as a trueth. — Preceding unsigned comment added by YannickFran ( talk • contribs) 07:56, 23 June 2016 (UTC)
Shouldn't we better split up the table into "Threshold 1", "Threshold 2" and "Redstone 1". That way we have a clear place to add some information about every update as we do with iOS and Android's pages on this matter and we don't end up with a way to long table. -- YannickFran ( talk) 14:50, 2 January 2016 (UTC)
If a build is released to the Release Preview ring, but not released to outsiders, should they still be placed under the "public release" charts? I would think they wouldn't be, but previous builds under that description have been being added under the "public releases" graphs. The Professor123 ( talk) 02:35, 10 August 2016 (UTC)
See Windows 10 Latest Preview: Isn't the version supposed to be 1703? Why isn't the page updated? Can you update the page? 220.255.100.134 ( talk) 13:05, 16 October 2016 (UTC)
The cumulative updates for Windows 10 are blatant copy-paste of the KB articles' descriptions of these updates. They need to be rewritten in original manner and properly summarized. We do not need to list every single bug fixes. Just highlights for each cumulative updates is sufficient. Wikipedia is not meant to be a detailed log of software updates. It is designed to give readers a summery. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 06:39, 16 March 2016 (UTC)
Anyone know whats going on with this? Why does wiki think it's a copy right violation? — Preceding unsigned comment added by Gh0sti100 ( talk • contribs) 20:49, 3 November 2016 (UTC)
Prior content in this article duplicated one or more previously published sources. Copied or closely paraphrased material has been rewritten or removed and must not be restored, unless it is duly released under a compatible license. (For more information, please see "using copyrighted works from others" if you are not the copyright holder of this material, or "donating copyrighted materials" if you are.)
For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or published material; such additions will be deleted. Contributors may use copyrighted publications as a source of information, and, if allowed under fair use, may copy sentences and phrases, provided they are included in quotation marks and referenced properly. The material may also be rewritten, providing it does not infringe on the copyright of the original or plagiarize from that source. Therefore, such paraphrased portions must provide their source. Please see our guideline on non-free text for how to properly implement limited quotations of copyrighted text. Wikipedia takes copyright violations very seriously, and persistent violators will be blocked from editing. While we appreciate contributions, we must require all contributors to understand and comply with these policies. Thank you. — Diannaa 🍁 ( talk) 20:25, 4 November 2016 (UTC)
I would like to point out that other version histories do the exact same thing. Why is this one being singled out? In addition, development versions listed in this article are NOT taken directly from Microsoft blog posts, only cumulative updates to released versions are. For the infringing parts, surely re-wording and/or more thorough citations would solve the issue? I don't believe removing all of the tables on this page was in any way necessary. (Please do not delete this anonymous comment, this situation is infuriating me.) — Preceding unsigned comment added by 2601:19A:4101:DD42:35C9:BBAC:2E72:3B59 ( talk) 22:38, 5 November 2016 (UTC)
Let's clear up 2 things here: Why is "Version 1511, November Update" 'too long'? Every other OS is getting these kind of titles, take a look at MacOS version history and Ubuntu version history, they all include version and name in the titles that are often longer. Second, 1507 is an official version and Microsoft has been referencing to the first version of Windows 10 with 1507 ever since 1511 was released.
Since these version numbers are the only thing that actually resemble something you can put in chronological order, it makes no sense to leave the mout of the titles. -- YannickFran ( talk) 11:05, 13 November 2016 (UTC)
winver
) and didn't see 1507 there. I believe the "official" criteria is appearing in the software itself.![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The anniversary update came out for LTSB in 2016. 66.69.252.169 ( talk) 10:01, 2 December 2016 (UTC)
Thanks SO MUCH to the admin who deleted everything for the sake of the article! I am genuinely thankful. While it is a shame that a lot of the non-copyrighted work got deleted, the outcome has been better than the risk of the entire article getting deleted and stuck behind a autocracy of appeal for restoration.
I, and many others, have spent hours writing dozens and dozens of bullet points in completely original format, making sure to not violate copyright. And while it pains me to see all that work go to waste, I acknowledge that hundreds of other bullet points were, indeed, copy and pasted from Microsoft blog posts. And trying to find what was stolen work versus what was not was going to be a massive pain and a waste of time, with a huge risk of having the article deleted.
Aso, again, I think the admin who saved the article. :)
Now, here's what we are going to do. We don't give up. We are going to do this correctly. From now on, we are going to err on the side of caution. It is better to have less, but originally written, information, rather than full breadth of information but copy-pasted or too closely paraphrased information from another source.
So, here's the guideline: List the released builds on the tables, with citation from non-Microsoft sources (adding MS sources in addition, if desired), BUT DO NOT ADD NOTES unless you have the time to write them yourselves. It's better to leave the notes section blank than plagiarizing. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 20:06, 6 November 2016 (UTC)
Candid question: since recently I can no longer see the list of Version 1607 build numbers. Why is this? — Preceding unsigned comment added by Jacques.999 ( talk • contribs) 09:32, 30 November 2016 (UTC)
Why keeping 1607 update are copyright violation. I think micro. will become happy if we keep they're update history? why not? At Last ... ( talk) 17:13, 8 December 2016 (UTC)
More than a defense of copyright violations, it looks like a boycott on MS. This page used to be the best source to keep track of the improvements on Windows 10 Pc and Mobile. — Preceding unsigned comment added by Judiospi ( talk • contribs) 18:11, 12 January 2017 (UTC)
Is this correct?
Version 1607 (Anniversary Update)
Latest Version 10.0.14393 is marked as Old and not as Current stable version. -- MTimann ( talk) 13:46, 13 March 2017 (UTC)
It took me quite a lot of time to look for the right sources and references and regarding early cumulative updates are harder to attain and are often "hid" in articles about more than one update (often still including Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, and Microsoft Windows 8.1 updates in the same articles), anyhow I've tried to add as much as possible containing the changes mentioned in the changelog so as of now this article fully fits what's permitted within WP:NOTCHANGELOG (although the way it's written needs to fit a more encyclopedic style).
To any new additions to the changelog please add non-Microsoft sources complementary to the original source, on the day an update is released finding news articles relating to the update are relatively easy to find, but if you wait too long they'll drown in various blogs and fora discussing the update at hand, so please work swift, and work in accordance to WP:SOURCE.
Thank you for taking the time to read this, and thank you in advance for adding secondary and tertiary sources to your contributions to this page.
Sincerely, -- 86.81.201.94 ( talk) 15:33, 27 March 2016 (UTC)
@ 111.123.144.58: Could you please explain why you keep removing the Windows Central source? It is not an invalid source. Thank you. Hayman30 ( talk) 10:40, 17 April 2017 (UTC)
@ 88.196.91.6: You changed the slow ring date from March 29, 2017 to April 11, 2017, but that is wrong. Please see the original source, "UPDATE 3/29: We have released Windows 10 Insider Preview Build 15063.2 for Mobile to Windows Insiders in the Slow ring.", the build for mobile was released to insiders on March 29. Your source simply verifies that it will be rolling out to the public on April 11, but the tabel you are changing is Preview versions of Windows 10 Redstone 2, you made a mistake. Hayman30 ( talk) 11:05, 17 April 2017 (UTC)
The app updates included in the builds were actually bundled with the said builds and should be included. The fact that an update or an app is ported to an older release is not a reason to not include that update in the release of the build in which it originates. It's like saying Internet Explorer 7 should not be included with Windows Vista release notes because it was later brought to Windows XP. Same with IE8, IE10, and IE11. Furthermore, some app updates do not get ported back to older versions due to technology limitations (for instance the UWP skype app which is exclusive to RS1 and not TH2 release, Paint 3D which is exclusive to RS2, and updated Windows Store in RS1). So even if we did agree to remove app updates that eventually gets ported (which I wholeheartedly disagree with), you would have to find individual updates and see if they were ported or not.
The same is true for extensions. Some extensions, such as Turn off the Lights on Edge, is ONLY available in RS2 builds because the developer stated that it requires new technology in the browser not present in RS1 (which can be heard in The Sam's Report podcast).
This also applies to updates. Some updates, such as Windows Update Cleanup from Windows 8, are ported to older Windows Releases. That doesn't mean we don't include the update in the release notes of the build it originates from.
Thank you. -- NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 17:45, 13 November 2016 (UTC)
Alright folks, version 1507 isn't EOL. It is no longer supported in the Semi Annual Pilot and Sime Annual Broad channels (the CB and CBB, for those on the old naming) but it is still supported on the Long-Term Support Channel for years to come. Support for version 1507 isn't expected to end until 2025. Another update for it will be released this tuesday... -- YannickFran ( talk) 14:15, 11 June 2017 (UTC)
So, now the argument has come up that LTSB "does not apply here" because "It's basically ended for consumers". Why? LTSB is a branch as much as any others are. Since when has Wikipedia ever made a difference between consumer-facing branches and non-consumer-facing branches? Not to mention that the Fast Ring, Slow Ring, Release Preview Ring and Semi Annual Broad Channel - branches that are all included in this page - aren't for consumers either. This is a wiki, not a consumers information guide. Nobody is removing information about Enterprise editions of Windows because they aren't for consumers either, this isn't any different. On June 13th, Microsoft will release another update for 10240 just like they've done every month. Are we now intentionally going to be incomplete and leave these builds out, ignoring about 8 years of version history for 1507 (and future LTSC releases like 1607)?-- YannickFran ( talk) 17:31, 11 June 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
111.123.159.25 ( talk) 11:57, 23 June 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Request to remove bad quality edits by @ Hayman30: that doesn't seem to help the article, primarily fails WP:SOURCE as these edits were heavily based on Microsoft's own websites and uses plagiarized content from Microsoft. 42.112.154.124 ( talk) 01:54, 14 July 2017 (UTC)
{{
edit semi-protected}}
template.
jd22292 (Jalen D. Folf) (
talk)
02:35, 14 July 2017 (UTC)117.135.235.17 ( talk) 08:01, 18 July 2017 (UTC)
User:Hayman30 I'm not sure what you are trying to achieve here. 1709 is not the current version of Windows 10, it is still in active development and there for the current preview release, just like the 1803 builds that are rolling out as well. 2 versions can be in development at the same time, that doesn't make the first one that is set to be released an "Old version, still supported", it's still the "Latest preview version" of Redstone 3. Having said that, stop complaining about "Taking it to talk", you're the one not doing that, this discussion is already going on Template_talk:Windows_10_versions, at this point, you're just trying to escalate this into an edit war. -- YannickFran ( talk) 14:45, 14 September 2017 (UTC)
It's odd to have two latest version. Also, Version 1709 is still in final development and still not yet released to Release Preview Ring. I think it should be categorized into latest preview version. Hakurei Phomu ( talk) 13:54, 21 September 2017 (UTC)
Windows 10 Fall Creators Update is actually Autumn Creators Update for the UK
https://www.windowscentral.com/microsoft-will-call-windows-10s-next-update-autumn-creators-update-uk
Microsoft will regionally adjust the name of the Windows 10 Fall Creators Update in the UK, calling it the "Autumn Creators Update" instead — Preceding unsigned comment added by Jonathan McEvoy ( talk • contribs) 13:51, 28 September 2017 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
spelling "Creaters" -> "Creators"
Version 1709 (Fall Creators Update)
.... The Fall Creaters Update (Version 1709, 10.0.16299) was officially release on October 17, 2017.
Version 1709 (Fall Creators Update)
.... The Fall Creators Update (Version 1709, 10.0.16299) was officially release on October 17, 2017.
108.235.242.4 ( talk) 04:24, 18 October 2017 (UTC)
.... The Fall Creators Update on Mobile (Version 1709, 10.0.15254.1) was available to Release Preview, and probably official release on October 17, 2017. 1000mm ( talk) 23:43, 18 October 2017 (UTC)
Is this a reliable source for saying that the next update of Windows 10 is called the 2018 Update?? If not, please explain:
https://theleaker.com/windows-10-2018-update-preview-is-redstone-4/
Georgia guy ( talk) 20:03, 26 October 2017 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on Windows 10 version history. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 5 June 2024).
Cheers.— InternetArchiveBot ( Report bug) 01:11, 21 November 2017 (UTC)
Microsoft updated the final dates of support for the Windows 10 Semi-Annual Channel (SAC): https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet#update
This page is already properly footnoted. Simply requesting that the dates listed in the table are updated to match. Here are the specific changes to the final dates of support for SAC:
Hope I'm raising this properly, this is my first Wikipedia edit suggestion. Thanks.
-- Ericalanwhitney ( talk) 13:41, 2 February 2018 (UTC)
Table should get new column at "support until" isn't it ?
Suggestion:
Support until | ||
---|---|---|
SAC (Home/Pro) |
SAC (Ent/Edu) |
LTSC |
-- 83.135.150.160 ( talk) 12:21, 3 February 2018 (UTC)
Maybe also another Column for Mobile ?
-- 83.135.150.160 ( talk) 12:23, 3 February 2018 (UTC)
https://thewincentral.com/windows-10-redstone-4-spring-creators-update-version-1803/
Georgia guy ( talk) 19:38, 3 February 2018 (UTC)
Can we please add a feature for version 15254.248 that it breaks the ability to open pdf files in Edge (only default app possible) which results in any pdf from an app which doesn't give you the option to download being unopenable. 103.217.166.220 ( talk) 00:00, 2 March 2018 (UTC)
In the past, Windows Server was not included in the list becasue it wasn't updated as a continuous release as was Windows 10 & Windows 10 mobile.
There was only Windows Server 2016, and it was akin to Windows 7, Windows Vista, Server 2008 RT, etc. But now, it's different.
Server has now adopted the Software as a service model and has aligned itself with Windows 10 client. There's now RS3, RS4, and RS5 releases either public or scheduled.
There needs to be a consensus on whether server should be included.
There's mobile version history. Why not server.
Thoughts, please.
NazmusLabs (A small part of a bigger movement to better the world!) ( talk) 23:56, 22 March 2018 (UTC)
I like the idea of creating a new article for Server Semi-Annual channel @ Warren suggested. That article can have a Version History heading that can list the builds for the server, using the tables following the template of this page. This will work like how Xbox OS version history, or iOS version history does.
Although these releases are essentially Windows 10 builds with the server stack added in on it and some client features removed, they are not labeled as Windows 10, and I have come around to the fact. Perhaps my idea initial idea of adding a server section to this article, although server is an edition of Windows 10 behind the scenes, might not be the best. Plus, adding server here will only substantially increase the length of this already long article, with new build releases only adding to the problem.
So, any objections? Ideas?
Current latest mobile version for public and insider ring is 10.0.15254.490 updated on 11 july 2018 Shubdragon ( talk) 13:04, 17 July 2018 (UTC)
windows 1809 has been recalled so currently has no release date the latest release candidate was 30th October ( https://support.microsoft.com/en-us/help/4464619)
On July 25, 2018, Microsoft officially released the first preview build of version 1903 (codename 19H1) to Insiders in the exclusive Skip Ahead ring (such as myself). The template for the Overview chart should be edited as such to reflect the changes, as well as updating the version 1809 build to 17723, as it has also been released to Insiders in the Fast ring. — Preceding unsigned comment added by TheTwoEyedMan ( talk • contribs) 23:24, 25 July 2018 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Under section Version 1809, please add version 10.0.17763 (Fast ring on September 18, 2018 at the bottom of the table. Here's the source:
[1]
86.22.8.235 (
talk)
17:37, 18 September 2018 (UTC)
Already done 86.22.8.235 ( talk) 18:39, 20 September 2018 (UTC)
Dear wiki-editors,
Why — after the
recent AfD proposal — the suggested splitting of this article has not yet been made?
It seems to be a very good solution. Current article needs to contain only summary information, such as the introductory part with a "overview table" (both already present).
Complementary and detailed data can effectively, without any prejudice, be directed to specific articles, created with an appropriate argument (year, edition / version, etc.).
Aainitio (
talk)
15:00, 18 June 2018 (UTC)
Any plan to add build history numbers to old versions (1607, 1703 1709...) This would be a great addition to keep everything in one place. Witkoskijp ( talk) 15:20, 20 August 2018 (UTC)
The opening sentence of this article currently reads " Windows 10 is an operating system developed by Microsoft." This obviously does not conform with the manual of style. The article title is "Windows 10 version history", not "Windows 10", so "Windows 10" should not be in bold. And even if it was correct for it to be in bold, it should not contain a link according to MOS:BOLDAVOID. It's depressing to note that the article has contained this error since it was created almost three years ago. 37.152.231.45 ( talk) 20:44, 9 October 2018 (UTC)
The Windows 10 rings is not really clear. They says build 1607 is still supported, but the consumer version isn't supported anymore. I think is is a idea to split the support in consumer and business. In "Latest build" seperate collums for consumer and business. Maybe it is possible to add the collors in the support dates instead of in "Latest build" The current design is really confusing. ( 195.35.231.195 ( talk) 10:45, 23 January 2019 (UTC)) — Preceding unsigned comment added by 195.35.231.195 ( talk) 10:42, 23 January 2019 (UTC)
Wikipedia has a clear policy on this category of articles, and whether is should be deleted. See Wikipedia:Articles for deletion/Google Chrome OS version history for an example of a past discussion. -- Kaledomo ( talk) 05:09, 13 March 2019 (UTC)
I'm request to split this page as a separate pages, because the page becoming heavier for every new information of new Windows versions. But probably we need choose between 2 ways.
1. New arcticle for every major update, like ..." Windows 10 Fall Creators Update", " Windows 10 April 2018 Update", " Windows 10 October 2018 Update", " Windows 10 19H1"...
2. New arcticle every 3 years (or less or more), like "Windows 10 version history (2015-2017)", "Windows 10 version history (2018-2020)", "Windows 10 version history (2021-2023)"... We already made simular of these as on Timeline of the Syrian Civil War or something like that.
So, what do you think? -- 81.200.16.229 ( talk) 11:52, 26 December 2018 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Windows 20H1 is now available for Fast Ring users
Source: https://twitter.com/windowsinsider/status/1116024531947147265 Selman N. Tabet AKA Chaos The Slayer 19:20, 10 April 2019 (UTC) — Preceding unsigned comment added by SelmanTabet97 ( talk • contribs) 20:20, 10 April 2019 (UTC)
Windows 10 has been dubbed as a service by Microsoft for almost five years now, with major updates building off of previous updates. Which is the reason why I am suggesting something that Mac articles have done: add articles about each Windows version, along with added features, removed features, reception, etc. Here are a few examples of what I am talking about: macOS Sierra, macOS High Sierra, macOS Mojave, OS X Mavericks.
Before Windows 10, the Windows OS only received paid upgrades, including Windows 8.1 to 10, Windows 7 to 8/8.1, Windows Vista to 7, and Windows XP to Vista. Windows 10 as a service removes the payments for these upgrades dubbed "feature updates". In fact, Windows 10 has significantly changed since the initial launch.
Given the information I provided, does Windows 10 deserve its own version articles? (Feel free to copy to WP:RFC or such) Awesome Aasim 03:31, 1 May 2019 (UTC)
Previously thought to be a 19H2 build, Microsoft surprised us by releasing a build for an update scheduled to launch in 2020. They claim that some features in the update need additional testing.
What are we going to do in this situation? Microsoft hasn’t even released a build of 1909 (19H2) yet. Any ideas? NotYourAbnormalJoe ( talk) 20:39, 14 February 2019 (UTC)
I saw a new at origo.hu, that there could be only 1 version in '19. Alfa-ketosav ( talk) 18:24, 5 May 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Error in KB number for: Version 1809 (October 2018 Update) / Public patches of Windows 10 version 1809 Currently reads: 10.0.17763.503 [619] / KB4495667 / Public release: May 14, 2019 Should read: 10.0.17763.503 [619] / KB4494441 / Public release: May 14, 2019 stu Bigstu2019 ( talk) 08:00, 15 May 2019 (UTC)
Shouldn't said template be moved from Windows 10 version history#Rings down to Windows 10 version history#PC version history since said template relates more to the latter than the former? -- Some-username-here1 ( talk) 20:00, 6 June 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Version 1903 (May 2019 Update) The Windows 10 May 2019 Update[651] (also known as version 1903[652] and codenamed "19H1"[606]) is the seventh major update to Windows 10 and the first to use a more descriptive codename (including the year and the order released) instead of the "Redstone"[653] or "Threshold" codename. The first preview was released to Insiders who opted in to the exclusive Skip Ahead ring on July 25, 2018. The update began rolling out on May 21, 2019.[654] Notable changes in the May 2019 Update include:[655][656]
The latest OS Build version is 18362.207 [June 27, 2019]
Edit request reason: The above paragraph is edited to add some more new features of Windows 10 1903 May 2019 update. Also the latest OS build version citing the sources. This is to keep Windows 10 users informed about a more vast set of changes made in the new version update. Palla Sridhar 16:06, 28 June 2019 (UTC) — Preceding unsigned comment added by Shreen2008 ( talk • contribs)
References
Not done The edit request has already been declined. Please do not change it back to "answered=no" until you have achieved consensus. --
kingboyk (
talk)
22:17, 20 July 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The latest current versions are 10.0.18362.356 and 10.0.18363.356 as of September 10, 2019. [2] ---- 194.207.146.167 ( talk) 07:08, 11 September 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Version 1903 is 18362.385 for release preview and version 1909 is 18363.385 for release preview. Harshmoney ( talk) 12:43, 24 September 2019 (UTC)
References
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Public patches of Windows 10 version 1809 10.0.17763.806[705] KB4519338 Public release: October 8, 2019 change to: 10.0.17763.805 192.33.238.48 ( talk) 14:09, 17 October 2019 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
1909 preview (the one with 18362 builds) bar below section "PC version history" should be red (no support) instead of yellow, since 1909 is released, isn't it?-- 2001:16B8:201:4400:C54F:A300:E187:E9F2 ( talk) 08:44, 16 November 2019 (UTC)
As in the article also 20H1 is in there, is there any official source - i know, it's only a code name, nevertheless - what the H stands for ... "heat"? Thank you. --
Alien4 (
talk)
12:01, 13 November 2019 (UTC)
Q = Quarter of a year ( 1~4 ) and H = Half of year ( 1~2)
so in case of 20H1 = in 1st half of the year 2020. XX03 and XX09 was for the months March and September, but this often do not fit with released date.
--
2001:16B8:201:4400:C54F:A300:E187:E9F2 (
talk)
08:49, 16 November 2019 (UTC)
20H2 Codname: Manganese 19541 — Preceding unsigned comment added by 2A02:8108:8E80:3338:DC3C:4A0B:AD80:12E9 ( talk) 14:25, 13 January 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Adding 20H2 row with link to article in Rings head Nikhilpal2705 ( talk) 07:43, 23 January 2020 (UTC)
Recently this page has crossed the 2048000 "Post-expand include size" limit enforced by the web server's software. See Help:Template#Template_limits and Category:Pages where template include size is exceeded for details.
The result is that templates that are at the bottom of the page will not display correctly.
I recommend splitting off another page identical to this one to cover "PC version history" versions 1507 through 1703. Why those dates? Except for LTSC (formerly named LTSB), those versions are not supported at all. davidwr/( talk)/( contribs) 21:31, 9 March 2020 (UTC)
[ [3]] Please add -- 2A02:8071:8199:FC00:61E2:ACB6:3BB9:53C1 ( talk) 13:40, 15 April 2020 (UTC)
Hi
Is it possible to change the codename for 20H1 to 'Vibranium'? See https://www.thurrott.com/windows/windows-10/190138/windows-10s-next-major-updates-will-be-codenamed-vanadium-vibranium. Also, 19H1 & 19H2 were still named Redstone (possibly 6 & 7), they still had 'rs' in the build strings. Wagnerp16 ( talk) 15:59, 30 April 2020 (UTC)
People are looking for information on particular versions; they do not want the entire article to be loaded. They want to know how a particular version was received by the general public. They do not want very general information like that in
Windows 10 or here.
A
a
s
i
m
01:13, 7 May 2020 (UTC)
Possibly divide the article into 15xx, 16xx, 17xx, etc. e.g. in pairs of two versions rather than each version separately as that would kind of be too much articles as there is not particularly much to say/difference between each version.
LukaAndjelkovic (
talk)
21:21, 7 May 2020 (UTC)
I agree that the versions could be paired, especially with the new major-minor cadence that Microsoft is using. I don't think splitting the article would be wise, though. It's useful to have a single page with the whole release history.
Herbfur (
talk)
22:46, 7 May 2020 (UTC)
I would like to see the 'windows 10 versions' table kept intact
Choman2 (
talk)
22:46, 10 May 2020 (UTC)
I would also like to see the table kept intact. I use it as reference on a regular basis because it is succinct (and easily bookmarked) in a way that Microsoft's own documentation is not.--
Jasebaese (
talk)
13:30, 19 May 2020 (UTC)
Wiki-Friends,
I understand the concern with the size of the article
Windows 10 version history in its current form [2020.05.18].
The suggestion for partitioning subsets can be useful in this case.
However, I recommend that redirection from
Windows 10 version history is present in all sub-articles.
Even more: I recommend that the table contained in
Windows_10_version_history # Rings be present in all sub-articles.
For... Viewing THE WHOLE... can be very important and useful.
Wiki-Success!
Aainitio (
talk)
11:57, 18 May 2020 (UTC)
Currently, any machine using an older graphics card based on Nvidia Tesla architecture is compatibility locked out of installing 2004, and it is unclear whether that will ever change. The issue is Stop codes (BSODs) with drivers older than 358.00 due to an incompatibility, and Tesla architecture cannot install drivers newer than version 342.01. I'm just browsing this article for the first time so am wondering if this would be an appropriate add anywhere and if so, where. (This is the only potentially permanent lockout I see on the list, but there may be others I missed.) Jtrevor99 ( talk) 02:57, 2 June 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
2001:16B8:27B:C800:D500:746C:4AA3:7A1E ( talk) 11:22, 7 June 2020 (UTC)
I suggest to fwd to latest /info/en/?search=Windows_10_version_history_(2019%E2%80%932020) not to oldest-- 2001:16B8:27B:C800:D500:746C:4AA3:7A1E ( talk) 11:22, 7 June 2020 (UTC)
Currently, if you open /info/en/?search=Windows_10_version_history you will be forwarded to /info/en/?search=Windows_10_version_history_(2015%E2%80%932016)
IMHO the forward target should changed from /info/en/?search=Windows_10_version_history_(2015%E2%80%932016) to /info/en/?search=Windows_10_version_history_(2019%E2%80%932020)
Cause the older history should be less important so the latest should have the priority. -- 2001:16B8:27B:C800:F4CE:FC31:15AD:1 ( talk) 18:30, 7 June 2020 (UTC)
After a long discussion, I have taken action at last and split the article into three, one for updates released from 2015 to 2016, one for 2017 to 2018, and one for 2019 to 2020 (which also includes rolling Fast Ring builds). I have also updated the templates to reflect the split. The original link redirects to the 2015 to 2016 updates. Harshmoney ( talk • contribs) 17:05, 4 June 2020 (UTC)
As of 08:31, 18 June 2020 (UTC), there are 950 references in the article. This is rather long, so is it possible someone build a collapsible around the references section? Thanks -- SlitherioFan2016 ( Talk/ Contribs) 08:31, 18 June 2020 (UTC)
![]() | This
edit request to
Windows 10 version history has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hi, i want to edit some typos in this page, there are too much typos there! Chris Ducker ( talk) 12:00, 21 June 2020 (UTC)
. Chris Ducker ( talk) 12:01, 21 June 2020 (UTC)
This is a very good and helpful article, but I'd like to have "build X = version Y" dependency in the chart; I think it would make nailing down disparate identifiers much easier than parsing the detailed writeups. — Preceding unsigned comment added by 96.91.22.118 ( talk) 17:48, 17 July 2020 (UTC)
ETA: NVM; I guess I was blind. — Preceding unsigned comment added by 96.91.22.118 ( talk) 17:50, 17 July 2020 (UTC)