![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||
|
![]() | The contents of the Windows 10 Cloud page were merged into Windows 10 editions. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
If this is true,
Microsoft has announced that upgrades made through July 29, 2016 will be free. This does not include upgrades for Windows Enterprise editions.[2]
Then why is Windows 7 Enterprise listed under Windows 10 Enterprise in that checkered table? -- 86.27.232.103 ( talk) 21:01, 3 June 2015 (UTC)
One of the only reasons I ever acquired Win 7 Ultimate editions was in order to be able to use multiple monitors with Remote Desktop.
Does anyone know and/or would it be useful to include information about whether/which editions of Win 10 support multi-monitor Remote Desktop? — Preceding unsigned comment added by Stokely ( talk • contribs) 13:36, 7 April 2016 (UTC)
Ugh, I'm horrible at editing...sorry this got inserted in the middle instead of at the bottom. — Preceding unsigned comment added by Stokely ( talk • contribs) 13:39, 7 April 2016 (UTC)
Originally on the Microsoft Windows 10 article the below wikitable was removed without any justification, while this article uses a completely different wikitable, personally I find the one below easier to read and would think that it would be more objective as it includes a more organised upgrade path and shows which versions and ineligible.
Windows version and edition | Eligible Windows 10 upgrade edition |
---|---|
Windows 7 Starter | Windows 10 Home |
Windows 7 Home Basic | |
Windows 7 Home Premium | |
Windows 8.1 with Bing | |
Windows 8.1 | |
Windows 7 Professional | Windows 10 Pro |
Windows 7 Ultimate | |
Windows 8.1 Pro | |
Windows 7 Enterprise | Not eligible |
Windows 8 Enterprise | |
Windows 8.1 Enterprise | |
Windows RT |
As the user hasn't given a reason for its removal I will ask if this model is better before inserting it and getting reverted. Sincerely, -- 86.81.201.94 ( talk) 07:19, 9 June 2015 (UTC)
Suggest that the data in this article be incorporated in main Windows 10 article. At the moment the sections on 'editions' are not consistent. CPES ( talk) 12:57, 29 June 2015 (UTC)
It has already been confirmed that these aren't Windows 10 editions, Wikipedia needs to be more consistent. Sincerely, -- 86.81.201.94 ( talk) 20:33, 9 October 2015 (UTC)
Locke411, your change does not include a reliable source. Your edits here and here (and now here, as you've reverted your changes yet again) - is not supported by a reliable source. If your change is correct and performing an in-place upgrade from the same Operating System to the exact same Operating System is not possible, then you need to provide a source that says that it isn't possible. Can you please discuss your concerns here instead of reverting? In the meantime, I am restoring the page back to its original state, as sources state that you can do this (it is essentially a system repair when you do so). See this source, as it is one of many sites that state that you can do this. ~Oshwah~ (talk) (contribs) 20:20, 22 March 2016 (UTC)
Please correct and improve my edit. Is it low-cost or free? Is it known what the maximum specs are? PizzaMan ( ♨♨) 11:41, 23 April 2016 (UTC)
Hi.
I recently reverted the following contribution in the article:
Windows 7 Ultimate's upgrade to Windows 10 Pro, is a functional downgrade, (W7U == W7 Enterprise, licenced for individual's use).
Apart from the fact that it is original research, it is wrong; i.e. upgrading Windows 7 Ultimate to Windows 10 Pro is not a functional downgrade. Windows 7 Ultimate had two set of extra features over Windows 7 Professional.
Here is feature set 1:
Although these features were available to owners of the Ultimate edition, only enterprises with appropriate software, licenses and a Windows Domain could use them. These features are not available in Windows 10 Pro.
Here is feature set 2:
These features can be used by the individuals at home. They are all available in Windows 10 Pro except SUA, which is deprecated in favor of Windows Subsystem for Linux. (Yes, Windows 10 Pro supports BitLocker too.)
So, as you can see, upgrading from Windows 7 Ultimate to Windows 10 Pro is not a functional downgrade.
Best regards,
Codename Lisa (
talk) 08:39, 10 June 2016 (UTC)
Hey. An IP editor has twice so far tried to add a "device-independent security updates" to the table, once without a source and once with a fake source. It is reverted once by Codename Lisa and once by your truly. If anyone has a source for this, please come forward. FleetCommand ( Speak your mind!) 07:23, 19 July 2016 (UTC)
What exactly is meant by this? There are many devices with hardware encryption around and they usually work independent from the OS. Thanks! 200.102.88.60 ( talk)
Re "Windows 10 Enterprise Long Term Servicing Branch (LTSB) ... is the most stripped down edition of Windows 10 available", I believe that Windows 10 Enterprise N LTSB is the most stripped down edition of Windows 10 available. -- Guy Macon ( talk) 18:36, 8 August 2016 (UTC)
I don't use Windows 10 so I can't verify or edit this myself, but in the comparison chart of Windows 10 editions, I would have expected the Remote Desktop feature in the Home edition of Windows 10 to be "host only", not "client only" - ie. someone can connect to you, but you can't connect to other people. That's how it's been with every other version of Windows that includes these features. -- TheSophera ( talk) 13:50, 13 August 2016 (UTC)
Hi.
Can this be proven by sources?
Best regards,
Codename Lisa (
talk) 15:03, 11 September 2016 (UTC)
I am trying to pull together a list of exactly what gets removed for N and KN editions. Here is my rough draft, mostly original research (random blogs, Korean and German sites using Google translate) WARNING: SOME OF THE FOLLOWING MAY BE INCORRECT.
"Due to a ruling for anti-competitive practices by the European Commission in 2004, Windows N editions have Media Player, Groove Music, Video Player, Voice Recorder, digital rights management, Windows Camera and Skype removed and are missing Audio and Video codecs (MPEG, WMA, AAC, FLAC, ALAC, AMR, Dolby Digital, VC-1, MPEG-4, H.264, H.265 and H.263)."
"Due to a ruling and fine by the Korea Trade Fair Commission in 2005, Windows KN editions have Media Player and Messenger removed and come pre-installed with links to competing instant messaging and media player software. KN Editions only support Korean and English."
(I think the K edition was XP only, but am not sure)
What I need to do to turn the above into something we can use are some reliable sources that detail exactly what was and was not removed so I can fact-check the above, add citations, and possibly add it to the article. Can anyone find sources on this? -- Guy Macon ( talk) 14:28, 12 September 2016 (UTC)
Hello
Today, WikIan made a host of good edits (resulting in 778448220), but I disagree with one of them. (As such I expressed by disagreement through BRD; I reverted to a last known good version, then restored all edits with which I had no problem.)
The problem is categorization of editions into "Main" and non-main variants. What is more questionable is that the editions designated as "Main" are actually the consumer editions: Home and Pro! Microsoft is a company whose motto should be: "Dear consumers, we couldn't care less about you." Its majority of income comes from the Enterprise sector and has not added a major consumers-only feature to Windows since Windows XP. How on earth these two editions are "Main"!?
Best regards,
Codename Lisa (
talk) 06:15, 3 May 2017 (UTC)
Right now Windows 10 S is listed as "device-specific", but isn't tied to any particular device type. It ships with the high-end Surface Laptop as well as entry-level devices, and is available to any school computers already on Windows Pro. It seems it should probably fall under the same category as Windows 10 Education. - Josh ( talk | contribs) 22:18, 3 May 2017 (UTC)
References
I reverted the headings changes that were made by Codename Lisa in edit 778958396, because 1. the order makes more sense, it flows logically from consumer to enterprise and then to the enterprise servicing branches (I'm not sure this should be in this article anyhow because half of the listed editions can't switch to CB, CBB, or LTSB). Additionally, calling them organizational editions is incorrect as Pro is licensed to small and mid-sized businesses [1] therefore saying that the listed enterprise editions are the only ones for all organizations is wrong.
Secondly, we should not have to clarify what an appliance is WP:MOS "Avoid ambiguity, jargon, and vague or unnecessarily complex wording". Device-specific means exactly what it is, they are preloaded on specific devices. Just as Mobile is not one device, S can also be on multiple devices. Only IoT really runs on Home_appliances and in any case PCs can be considered appliances too. WikIan -( talk) 04:25, 8 May 2017 (UTC)
References
{{
cite web}}
: Cite has empty unknown parameter: |dead-url=
(
help)
Does this belong in the edition article? I mean first of all, with delta updates Windows 10 is not being offered as a full image each time it upgrades. I'm reading through current branch and I am looking for any articles that say Windows 10 Home/Pro is part of current branch (CB). WikIan -( talk) 04:37, 8 May 2017 (UTC)
I don't see how On MSFT is an unreliable source, even if the wording was wrong On MSFT is as reliable as Engadget. Donald Trung ( talk) 00:00, 29 May 2017 (UTC)
Hello!
Recently, one of our editors, Shujenchang has added the following to the article:
After Fall Creators Update, Windows Defender Application Guard is introduced into Windows 10 Enterprise but not included in Windows 10 Education [1].
But the source given does not say this. It says nothing about the Education edition. It does not even say "only Enterprise edition". Actually, it looks like an article about the Enteprise edition that is simply not interest in the Education edition. I believe Shujenchang's novel interpretation is wrong and this sentence must be removed.
Best regards,
Codename Lisa (
talk) 11:16, 24 October 2017 (UTC)
References
@ Shujenchang: It appears the two editions don't have feature parity anymore anyway. The Education edition is missing support for creating ReFS volumes. Best regards, Codename Lisa ( talk) 09:55, 30 October 2017 (UTC)
Hi.
Because of a potential for factual inaccuracy, I deleted the statement saying Windows 10 free upgrade offer has ended (at least for some people). I believe it is best if Wikipedia remain silent on this matter, because of this:
To summarize them: They say Microsoft has explicitly announced that the free upgrade offer has ended, but it is still offering it. All you have to do is to perform a clean installation of the appropriate edition of Windows 10 and refuse to give (postpone giving) a product key, or perform the upgrade installation. Next time you try to connect to the Internet, Microsoft will activate your Windows 10 for you.
Now, these sources are quite old, respectively by 10 months and 5 months. But yesterday, I installed Windows 10 Pro on an HP and a Vaio laptop, one with upgrade and one with a clean installation; Microsoft activated them for me. (So, now, I have two extra Windows licenses which I had purchased!) Of course, both laptops previously had Windows 7 on them, so the Windows Activation Technology 2.0 certificate is already integrated into their firmware. Hence, Microsoft is able to confirm that I was indeed doing a de facto upgrade in both cases.
Best regards,
Codename Lisa (
talk) 05:56, 20 November 2017 (UTC)
The information here seems very outdated.
-- Ikar.us ( talk) 10:32, 3 January 2018 (UTC)
The edit is labeled as a graphical only fix, but it changes content of the Enterprise as well.
https://en.wikipedia.org/?title=Windows_10_editions&diff=807826178&oldid=807819004
Is there any information that the new
Since different versions of LTSB/LTSC would have different features, they should also have their own column.
I do not agree with the current setup, I would like if all the edition differences be split into versions, each having it's own column and then another chart for the each of the redstone releases. The point where there is no LTSB release would simply leave a placeholder column with N/A written to it. Herakotamo ( talk) 02:27, 20 January 2018 (UTC)
@ User:Codename Lisa You reverted my edit about Window 10 S mode. You reverted my edit about Window 10 S mode. I appreciate that there are a lot of announcements by MS that aren't followed up and computer news sites will publish anything that attracts readers. However this S mode is already actually implemented in the Redstone 4 (public beta) version of Windows. [1] In fact S mode is already present in the Entreprise edition of Windows 10. [2] The only news is that it's also going to be implemented in the Home and Pro versions. I agree that we should be cautious with roumors, but removing all mentions of S mode is overdoing it. PizzaMan ♨♨♨ 08:03, 4 February 2018 (UTC)
References
{{
cite web}}
: Missing or empty |title=
(
help)
{{
cite web}}
: Missing or empty |title=
(
help)
Hello, everyone
Please welcome our new editor,
Rd.Chrxlr. (Hi! I hope you are reading this.
)
Our new colleague had made extensive contributions to this article, which turned out problematic. But as is our policy with all the newcomers, I am writing a full description of what is wrong with them.
Windows 10 Home [...] In terms of upgrade paths, it is functionally equivalent to Starter, Home Basic, and Home Premium editions for [[Windows 8.1|Windows 7]], and core edition for [[Windows 8]] and 8.1.
They are not true. There is not such thing as "Windows 10 Professional" (only "Windows 10 Pro"). The comment on the upgrade path only stems from the observation of the free upgrade offer and is WP:SYNTH in nature; other upgrade paths are available. Also, the functionality of Windows 7 editions widely differ from the functionality of Windows 8.x and 10 editions; such a vague comment is far too inaccurate.Windows 10 Pro [...] In terms of upgrade paths, it is functionally equivalent to Professional and Ultimate editions for Windows 7, and Pro edition for Windows 8 and [[Windows 8.1|8.1]].
Windows 10 Mobile Enterprise (also known as Windows 10 Mobile for Business)
Windows 10 Pro (or Professional)
Best regards,
Codename Lisa (
talk) 08:28, 17 February 2018 (UTC)
No link, no explanation anywhere. Great article :P -- jae ( talk) 11:45, 11 January 2019 (UTC)
There are a lot of speculations that Microsoft may release Windows 10X as a separate OS. So, I think that it would be better if Windows 10X is scrapped off this article and a separate article is made for it instead. — Preceding unsigned comment added by 2405:204:A02D:2956:8C7C:E709:F091:ED47 ( talk) 07:41, 23 May 2020 (UTC)
The reference linked from Minimum Telemetry levels, seems to imply that Windows 10 Education should have same minimum telemetry level as Windows 10 Enterprise. Are there any references for this not being the case? — Preceding unsigned comment added by Win10tabledit ( talk • contribs) 20:49, 18 August 2020 (UTC)
Device-specific editions category isn't contain Windows 10 ARM version and Xbox firmware which is also based on Windows 10 core. — Preceding unsigned comment added by 92.38.72.233 ( talk) 13:01, 1 January 2021 (UTC)
The core count limits in the table are uncited, and I haven't been able to find an official source for these being actual limits. The closest I could find is a Microsoft MVP (not an employee) replying to someone on a forum in July 2015, saying "up to 256 cores" are supported on 64-bit SKUs.
SKU limitations are mostly applied via ProductPolicy, which on my Windows 10 Pro for Workstations install does not have any entry that limits core counts. There is a CPU socket count limitation (Kernel-RegisteredProcessors) which is set to 4, and this matches documented socket limits.
During reverse engineering of ntoskrnl I was unable to find anywhere where core counts are limited based on the SKU. KeRegisteredProcessors is set based on the Kernel-RegisteredProcessors entry in ProductPolicy. This sets the socket count limit. If that entry does not exist, it defaults to 1. KeNumprocSpecified is set based on the NUMPROC boot argument, which seems to limit the number of sockets that are enumerated when this is set. KeMaximumProcessors is set only when the MAXPROC boot argument is set, otherwise it defaults to 0x500 (1280). This appears to be the only limit on core counts, and it's hard-coded in the kernel. This all occurs inside Phase1InitializationDiscard. The only other place where KeMaximumProcessors is written to is in KeStartAllProcessors, and those writes are related to processor group initialisation in the context of dynamic partitioning. The values set here are not influenced by any policy or licensing values.
I suspect that the core count limits listed here are not actual limits, but are in fact based on the socket count limit multiplied by the highest logical core count CPUs that were available at the time, i.e. 1 socket * 64 logical cores = 64 core "limit" on Home, 2 sockets * 64 logical cores = 128 core "limit" on Pro/Edu, and 4 sockets * 64 logical cores = 256 core "limit" on Pro for Workstations. The Windows 10 Enterprise entry says 2 sockets max, which comes from the Groovypost source, but that article itself is unsourced and I can't find any official docs that match the claimed numbers. Based on this forum thread it looks like the Kernel-RegisteredProcessors policy value for Enterprise SKUs is indeed 4, not 2.
All in all, the values seem dubiously sourced and likely wrong. Can anyone find an official source to corroborate the existing values? What's my best approach for fixing the table without falling foul of original research? Gsuberland ( talk) 18:28, 6 April 2022 (UTC)
Even the applocker-article iteself says, applocker is available in Pro, the table on this article says its limited to enterprise. that's wrong. But as i'm absolutely not familar with wiki editing, i'm not going to mess with that table :D 62.153.61.217 ( talk) 11:54, 19 April 2024 (UTC)
![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||
|
![]() | The contents of the Windows 10 Cloud page were merged into Windows 10 editions. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
If this is true,
Microsoft has announced that upgrades made through July 29, 2016 will be free. This does not include upgrades for Windows Enterprise editions.[2]
Then why is Windows 7 Enterprise listed under Windows 10 Enterprise in that checkered table? -- 86.27.232.103 ( talk) 21:01, 3 June 2015 (UTC)
One of the only reasons I ever acquired Win 7 Ultimate editions was in order to be able to use multiple monitors with Remote Desktop.
Does anyone know and/or would it be useful to include information about whether/which editions of Win 10 support multi-monitor Remote Desktop? — Preceding unsigned comment added by Stokely ( talk • contribs) 13:36, 7 April 2016 (UTC)
Ugh, I'm horrible at editing...sorry this got inserted in the middle instead of at the bottom. — Preceding unsigned comment added by Stokely ( talk • contribs) 13:39, 7 April 2016 (UTC)
Originally on the Microsoft Windows 10 article the below wikitable was removed without any justification, while this article uses a completely different wikitable, personally I find the one below easier to read and would think that it would be more objective as it includes a more organised upgrade path and shows which versions and ineligible.
Windows version and edition | Eligible Windows 10 upgrade edition |
---|---|
Windows 7 Starter | Windows 10 Home |
Windows 7 Home Basic | |
Windows 7 Home Premium | |
Windows 8.1 with Bing | |
Windows 8.1 | |
Windows 7 Professional | Windows 10 Pro |
Windows 7 Ultimate | |
Windows 8.1 Pro | |
Windows 7 Enterprise | Not eligible |
Windows 8 Enterprise | |
Windows 8.1 Enterprise | |
Windows RT |
As the user hasn't given a reason for its removal I will ask if this model is better before inserting it and getting reverted. Sincerely, -- 86.81.201.94 ( talk) 07:19, 9 June 2015 (UTC)
Suggest that the data in this article be incorporated in main Windows 10 article. At the moment the sections on 'editions' are not consistent. CPES ( talk) 12:57, 29 June 2015 (UTC)
It has already been confirmed that these aren't Windows 10 editions, Wikipedia needs to be more consistent. Sincerely, -- 86.81.201.94 ( talk) 20:33, 9 October 2015 (UTC)
Locke411, your change does not include a reliable source. Your edits here and here (and now here, as you've reverted your changes yet again) - is not supported by a reliable source. If your change is correct and performing an in-place upgrade from the same Operating System to the exact same Operating System is not possible, then you need to provide a source that says that it isn't possible. Can you please discuss your concerns here instead of reverting? In the meantime, I am restoring the page back to its original state, as sources state that you can do this (it is essentially a system repair when you do so). See this source, as it is one of many sites that state that you can do this. ~Oshwah~ (talk) (contribs) 20:20, 22 March 2016 (UTC)
Please correct and improve my edit. Is it low-cost or free? Is it known what the maximum specs are? PizzaMan ( ♨♨) 11:41, 23 April 2016 (UTC)
Hi.
I recently reverted the following contribution in the article:
Windows 7 Ultimate's upgrade to Windows 10 Pro, is a functional downgrade, (W7U == W7 Enterprise, licenced for individual's use).
Apart from the fact that it is original research, it is wrong; i.e. upgrading Windows 7 Ultimate to Windows 10 Pro is not a functional downgrade. Windows 7 Ultimate had two set of extra features over Windows 7 Professional.
Here is feature set 1:
Although these features were available to owners of the Ultimate edition, only enterprises with appropriate software, licenses and a Windows Domain could use them. These features are not available in Windows 10 Pro.
Here is feature set 2:
These features can be used by the individuals at home. They are all available in Windows 10 Pro except SUA, which is deprecated in favor of Windows Subsystem for Linux. (Yes, Windows 10 Pro supports BitLocker too.)
So, as you can see, upgrading from Windows 7 Ultimate to Windows 10 Pro is not a functional downgrade.
Best regards,
Codename Lisa (
talk) 08:39, 10 June 2016 (UTC)
Hey. An IP editor has twice so far tried to add a "device-independent security updates" to the table, once without a source and once with a fake source. It is reverted once by Codename Lisa and once by your truly. If anyone has a source for this, please come forward. FleetCommand ( Speak your mind!) 07:23, 19 July 2016 (UTC)
What exactly is meant by this? There are many devices with hardware encryption around and they usually work independent from the OS. Thanks! 200.102.88.60 ( talk)
Re "Windows 10 Enterprise Long Term Servicing Branch (LTSB) ... is the most stripped down edition of Windows 10 available", I believe that Windows 10 Enterprise N LTSB is the most stripped down edition of Windows 10 available. -- Guy Macon ( talk) 18:36, 8 August 2016 (UTC)
I don't use Windows 10 so I can't verify or edit this myself, but in the comparison chart of Windows 10 editions, I would have expected the Remote Desktop feature in the Home edition of Windows 10 to be "host only", not "client only" - ie. someone can connect to you, but you can't connect to other people. That's how it's been with every other version of Windows that includes these features. -- TheSophera ( talk) 13:50, 13 August 2016 (UTC)
Hi.
Can this be proven by sources?
Best regards,
Codename Lisa (
talk) 15:03, 11 September 2016 (UTC)
I am trying to pull together a list of exactly what gets removed for N and KN editions. Here is my rough draft, mostly original research (random blogs, Korean and German sites using Google translate) WARNING: SOME OF THE FOLLOWING MAY BE INCORRECT.
"Due to a ruling for anti-competitive practices by the European Commission in 2004, Windows N editions have Media Player, Groove Music, Video Player, Voice Recorder, digital rights management, Windows Camera and Skype removed and are missing Audio and Video codecs (MPEG, WMA, AAC, FLAC, ALAC, AMR, Dolby Digital, VC-1, MPEG-4, H.264, H.265 and H.263)."
"Due to a ruling and fine by the Korea Trade Fair Commission in 2005, Windows KN editions have Media Player and Messenger removed and come pre-installed with links to competing instant messaging and media player software. KN Editions only support Korean and English."
(I think the K edition was XP only, but am not sure)
What I need to do to turn the above into something we can use are some reliable sources that detail exactly what was and was not removed so I can fact-check the above, add citations, and possibly add it to the article. Can anyone find sources on this? -- Guy Macon ( talk) 14:28, 12 September 2016 (UTC)
Hello
Today, WikIan made a host of good edits (resulting in 778448220), but I disagree with one of them. (As such I expressed by disagreement through BRD; I reverted to a last known good version, then restored all edits with which I had no problem.)
The problem is categorization of editions into "Main" and non-main variants. What is more questionable is that the editions designated as "Main" are actually the consumer editions: Home and Pro! Microsoft is a company whose motto should be: "Dear consumers, we couldn't care less about you." Its majority of income comes from the Enterprise sector and has not added a major consumers-only feature to Windows since Windows XP. How on earth these two editions are "Main"!?
Best regards,
Codename Lisa (
talk) 06:15, 3 May 2017 (UTC)
Right now Windows 10 S is listed as "device-specific", but isn't tied to any particular device type. It ships with the high-end Surface Laptop as well as entry-level devices, and is available to any school computers already on Windows Pro. It seems it should probably fall under the same category as Windows 10 Education. - Josh ( talk | contribs) 22:18, 3 May 2017 (UTC)
References
I reverted the headings changes that were made by Codename Lisa in edit 778958396, because 1. the order makes more sense, it flows logically from consumer to enterprise and then to the enterprise servicing branches (I'm not sure this should be in this article anyhow because half of the listed editions can't switch to CB, CBB, or LTSB). Additionally, calling them organizational editions is incorrect as Pro is licensed to small and mid-sized businesses [1] therefore saying that the listed enterprise editions are the only ones for all organizations is wrong.
Secondly, we should not have to clarify what an appliance is WP:MOS "Avoid ambiguity, jargon, and vague or unnecessarily complex wording". Device-specific means exactly what it is, they are preloaded on specific devices. Just as Mobile is not one device, S can also be on multiple devices. Only IoT really runs on Home_appliances and in any case PCs can be considered appliances too. WikIan -( talk) 04:25, 8 May 2017 (UTC)
References
{{
cite web}}
: Cite has empty unknown parameter: |dead-url=
(
help)
Does this belong in the edition article? I mean first of all, with delta updates Windows 10 is not being offered as a full image each time it upgrades. I'm reading through current branch and I am looking for any articles that say Windows 10 Home/Pro is part of current branch (CB). WikIan -( talk) 04:37, 8 May 2017 (UTC)
I don't see how On MSFT is an unreliable source, even if the wording was wrong On MSFT is as reliable as Engadget. Donald Trung ( talk) 00:00, 29 May 2017 (UTC)
Hello!
Recently, one of our editors, Shujenchang has added the following to the article:
After Fall Creators Update, Windows Defender Application Guard is introduced into Windows 10 Enterprise but not included in Windows 10 Education [1].
But the source given does not say this. It says nothing about the Education edition. It does not even say "only Enterprise edition". Actually, it looks like an article about the Enteprise edition that is simply not interest in the Education edition. I believe Shujenchang's novel interpretation is wrong and this sentence must be removed.
Best regards,
Codename Lisa (
talk) 11:16, 24 October 2017 (UTC)
References
@ Shujenchang: It appears the two editions don't have feature parity anymore anyway. The Education edition is missing support for creating ReFS volumes. Best regards, Codename Lisa ( talk) 09:55, 30 October 2017 (UTC)
Hi.
Because of a potential for factual inaccuracy, I deleted the statement saying Windows 10 free upgrade offer has ended (at least for some people). I believe it is best if Wikipedia remain silent on this matter, because of this:
To summarize them: They say Microsoft has explicitly announced that the free upgrade offer has ended, but it is still offering it. All you have to do is to perform a clean installation of the appropriate edition of Windows 10 and refuse to give (postpone giving) a product key, or perform the upgrade installation. Next time you try to connect to the Internet, Microsoft will activate your Windows 10 for you.
Now, these sources are quite old, respectively by 10 months and 5 months. But yesterday, I installed Windows 10 Pro on an HP and a Vaio laptop, one with upgrade and one with a clean installation; Microsoft activated them for me. (So, now, I have two extra Windows licenses which I had purchased!) Of course, both laptops previously had Windows 7 on them, so the Windows Activation Technology 2.0 certificate is already integrated into their firmware. Hence, Microsoft is able to confirm that I was indeed doing a de facto upgrade in both cases.
Best regards,
Codename Lisa (
talk) 05:56, 20 November 2017 (UTC)
The information here seems very outdated.
-- Ikar.us ( talk) 10:32, 3 January 2018 (UTC)
The edit is labeled as a graphical only fix, but it changes content of the Enterprise as well.
https://en.wikipedia.org/?title=Windows_10_editions&diff=807826178&oldid=807819004
Is there any information that the new
Since different versions of LTSB/LTSC would have different features, they should also have their own column.
I do not agree with the current setup, I would like if all the edition differences be split into versions, each having it's own column and then another chart for the each of the redstone releases. The point where there is no LTSB release would simply leave a placeholder column with N/A written to it. Herakotamo ( talk) 02:27, 20 January 2018 (UTC)
@ User:Codename Lisa You reverted my edit about Window 10 S mode. You reverted my edit about Window 10 S mode. I appreciate that there are a lot of announcements by MS that aren't followed up and computer news sites will publish anything that attracts readers. However this S mode is already actually implemented in the Redstone 4 (public beta) version of Windows. [1] In fact S mode is already present in the Entreprise edition of Windows 10. [2] The only news is that it's also going to be implemented in the Home and Pro versions. I agree that we should be cautious with roumors, but removing all mentions of S mode is overdoing it. PizzaMan ♨♨♨ 08:03, 4 February 2018 (UTC)
References
{{
cite web}}
: Missing or empty |title=
(
help)
{{
cite web}}
: Missing or empty |title=
(
help)
Hello, everyone
Please welcome our new editor,
Rd.Chrxlr. (Hi! I hope you are reading this.
)
Our new colleague had made extensive contributions to this article, which turned out problematic. But as is our policy with all the newcomers, I am writing a full description of what is wrong with them.
Windows 10 Home [...] In terms of upgrade paths, it is functionally equivalent to Starter, Home Basic, and Home Premium editions for [[Windows 8.1|Windows 7]], and core edition for [[Windows 8]] and 8.1.
They are not true. There is not such thing as "Windows 10 Professional" (only "Windows 10 Pro"). The comment on the upgrade path only stems from the observation of the free upgrade offer and is WP:SYNTH in nature; other upgrade paths are available. Also, the functionality of Windows 7 editions widely differ from the functionality of Windows 8.x and 10 editions; such a vague comment is far too inaccurate.Windows 10 Pro [...] In terms of upgrade paths, it is functionally equivalent to Professional and Ultimate editions for Windows 7, and Pro edition for Windows 8 and [[Windows 8.1|8.1]].
Windows 10 Mobile Enterprise (also known as Windows 10 Mobile for Business)
Windows 10 Pro (or Professional)
Best regards,
Codename Lisa (
talk) 08:28, 17 February 2018 (UTC)
No link, no explanation anywhere. Great article :P -- jae ( talk) 11:45, 11 January 2019 (UTC)
There are a lot of speculations that Microsoft may release Windows 10X as a separate OS. So, I think that it would be better if Windows 10X is scrapped off this article and a separate article is made for it instead. — Preceding unsigned comment added by 2405:204:A02D:2956:8C7C:E709:F091:ED47 ( talk) 07:41, 23 May 2020 (UTC)
The reference linked from Minimum Telemetry levels, seems to imply that Windows 10 Education should have same minimum telemetry level as Windows 10 Enterprise. Are there any references for this not being the case? — Preceding unsigned comment added by Win10tabledit ( talk • contribs) 20:49, 18 August 2020 (UTC)
Device-specific editions category isn't contain Windows 10 ARM version and Xbox firmware which is also based on Windows 10 core. — Preceding unsigned comment added by 92.38.72.233 ( talk) 13:01, 1 January 2021 (UTC)
The core count limits in the table are uncited, and I haven't been able to find an official source for these being actual limits. The closest I could find is a Microsoft MVP (not an employee) replying to someone on a forum in July 2015, saying "up to 256 cores" are supported on 64-bit SKUs.
SKU limitations are mostly applied via ProductPolicy, which on my Windows 10 Pro for Workstations install does not have any entry that limits core counts. There is a CPU socket count limitation (Kernel-RegisteredProcessors) which is set to 4, and this matches documented socket limits.
During reverse engineering of ntoskrnl I was unable to find anywhere where core counts are limited based on the SKU. KeRegisteredProcessors is set based on the Kernel-RegisteredProcessors entry in ProductPolicy. This sets the socket count limit. If that entry does not exist, it defaults to 1. KeNumprocSpecified is set based on the NUMPROC boot argument, which seems to limit the number of sockets that are enumerated when this is set. KeMaximumProcessors is set only when the MAXPROC boot argument is set, otherwise it defaults to 0x500 (1280). This appears to be the only limit on core counts, and it's hard-coded in the kernel. This all occurs inside Phase1InitializationDiscard. The only other place where KeMaximumProcessors is written to is in KeStartAllProcessors, and those writes are related to processor group initialisation in the context of dynamic partitioning. The values set here are not influenced by any policy or licensing values.
I suspect that the core count limits listed here are not actual limits, but are in fact based on the socket count limit multiplied by the highest logical core count CPUs that were available at the time, i.e. 1 socket * 64 logical cores = 64 core "limit" on Home, 2 sockets * 64 logical cores = 128 core "limit" on Pro/Edu, and 4 sockets * 64 logical cores = 256 core "limit" on Pro for Workstations. The Windows 10 Enterprise entry says 2 sockets max, which comes from the Groovypost source, but that article itself is unsourced and I can't find any official docs that match the claimed numbers. Based on this forum thread it looks like the Kernel-RegisteredProcessors policy value for Enterprise SKUs is indeed 4, not 2.
All in all, the values seem dubiously sourced and likely wrong. Can anyone find an official source to corroborate the existing values? What's my best approach for fixing the table without falling foul of original research? Gsuberland ( talk) 18:28, 6 April 2022 (UTC)
Even the applocker-article iteself says, applocker is available in Pro, the table on this article says its limited to enterprise. that's wrong. But as i'm absolutely not familar with wiki editing, i'm not going to mess with that table :D 62.153.61.217 ( talk) 11:54, 19 April 2024 (UTC)