Talk:Microsoft Windows/Archive 1

Locked

Why has this page been locked for editing? Is it because someone vandalised it? Tau Ceti (talk) 08:03, 28 October 2014 (GMT)

I don't know, AlphaBeta has did protected page with Edit Trust.--BillyHatcher2012 (talk) 08:37, 28 October 2014 (GMT)
Yes, it's protected because of two reasons:
1. The page is changed only with new Windows version announcements.
2. It's been vandalized.
--AlphaBeta (talk) 14:03, 28 October 2014 (GMT)
New Windows version announcements? You're forgetting MultiPoint Server 2011 and 2012, Windows CE (should that go on its own page), Windows Mobile and Phone (same there), and so on? There are plenty of older versions not here. Tau Ceti (talk) 02:45, 1 November 2014 (GMT)
Those are actually SKU's of the base versions (Windows / Windows Server). If you need to link those, please do so from the base version article (which would be Windows:Server2008R2 for MPS2011, Windows:Server2012 for MPS2012). --AlphaBeta (talk) 18:06, 25 November 2014 (GMT)
I was going to add about Internet Explorer. Some pages are already there. --Tau Ceti (talk) 02:46, 25 November 2014 (GMT)

Longhorn and Blackcomb

According to Wikipedia, Longhorn and Blackcomb isn't cancelled versions of Windows, Longhorn is the codename of Windows Vista and Blackcomb is the codename of Windows 7. https://en.wikipedia.org/wiki/List_of_Microsoft_codenames#Windows_NT_family --Yue Ling (talk) 09:04, 30 March 2019 (UTC)

Longhorn itself wasn't cancelled, it was reset, but many of its original features did end up cancelled as a result. Which means that pre-reset Longhorn was actually never released as it was before the reset. The Blackcomb-to-Vienna change appears to be another journalist rumour from back in the day, the only source seems to be Robert Scoble, who was an evangelist blogger for Microsoft, but even he barely spoke of it and provided no source. Fact is that Windows 7 is far from what Blackcomb was originally meant to be, the development and reset of Longhorn changed a lot of things. Just because Blackcomb was to follow Longhorn, Longhorn eventually became Vista, and 7 came after Vista, doesn't mean that Blackcomb was always meant to be 7. Projects and their codenames and goals change over time, even if their chronological order stays the same. --Overdoze (talk) 12:05, 30 March 2019 (UTC)
No matter what features got removed, but it's still the codenames. --Yue Ling (talk) 13:26, 5 April 2019 (UTC)
So let's call XP "Neptune" while at it. Windows 7 was codenamed '7', not Blackcomb. --AlphaBeta (talk) 17:54, 5 April 2019 (UTC)
Did you read Wikipedia? Also Neptune was originally codename of a successor to Windows 2000 for consumers, but later merged with Whistler and Whistler is codename of Windows XP. --Yue Ling (talk) 13:23, 10 April 2019 (UTC)
Yes, I read Wikipedia. The codename list also claims that Janus was the codename for Windows 3.1, which it was not. See where this is going? --AlphaBeta (talk) 13:34, 10 April 2019 (UTC)
Wikipedia doesn't understand how codenames work with Windows--sArAmTaCoJeSUs (talk) 13:51, 10 April 2019 (UTC)
But Blackcomb was well-known codename of Windows 7. --113.20.101.202 14:21, 11 April 2019 (UTC)
Well-known by whom? --Ryuzaki (talk) 14:35, 11 April 2019 (UTC)
By the internet (countless) as Blackcomb renamed to Vienna in 2006 and Windows 7 in 2007. --Yue Ling (talk) 13:09, 12 April 2019 (UTC)
The internet can be wrong. Ex: Mac System Software version names. --LilShootDawg (talk) 13:36, 12 April 2019 (UTC)
Surely you can provide at least a few links to online sources then, if there's countless of them?--Overdoze (talk) 13:41, 12 April 2019 (UTC)
https://betanews.com/2006/01/19/blackcomb-renamed-to-vienna/ For more, just google. --Yue Ling (talk) 13:27, 26 April 2019 (UTC)

Change request

I request a minor change in the Windows 10 Update section. The April 2019 Update is now the May 2019 Update. --109.180.145.38 17:33, 4 April 2019 (UTC)

Done --Cvolton (talk) 17:39, 4 April 2019 (UTC)

Wrong latest release

The latest release is the Windows 10 May 2019 update, not the October update anymore. Can someone who can edit the page change it? Meow (talk) 15:45, 25 May 2019 (UTC)

It is now June

It is June, but the page still says May. Can someone fix this?--Winins (talk) 15:08, 9 June 2019 (UTC)

Could you pinpoint the exact sentence that is wrong? --Ryuzaki (talk) 16:12, 9 June 2019 (UTC)
It was the "The latest released version as of 2019-05 is Windows 10 May 2019 Update." It has been corrected. BF10 (talk) 16:15, 9 June 2019 (UTC)
I don't get what's wrong with that sentence. It just says that in May the latest version released was the May update. There is no need to update the date every single month. --Ryuzaki (talk) 17:19, 9 June 2019 (UTC)
It makes the page look outdated though. That sentence makes it look like it hasn't been updated in months and that the situation has most likely changed since then. --Cvolton (talk | contribs) 17:49, 9 June 2019 (UTC)
I agree with Cvolton. -- 2.30.192.116 17:28, 10 June 2019 (UTC)

"Memphis NT" is not an official codename (Please fix)

Although the IA-64 release (a.k.a the 64-Bit release) of Windows 2000 got the codename "Janus" (re-used from Windows 3.1 for an unknown reason), the original release (the 32-Bit release) didn't get any codenames. Take a moment to read this text from Wikipedia: "Windows 2000 did not have a codename because, according to Dave Thompson of Windows NT team, 'Jim Allchin didn't like codenames'". So the "Memphis NT" codename is not official. Please fix this and add a note about the "Janus" thing. TheReleaseTester09 (talk) 09:23, 24 August 2019 (GMT)

Memphis NT is mentioned in PX02013 from early 1994 as the NT release to come after Cairo, but since we've established that Blackcomb can't be the codename of Windows 7 (see relevant discussion on this wiki), I agree with your proposal.--Overdoze (talk) 10:34, 24 August 2019 (UTC)
Can you please give me a link to PX02013? I want to see this Memphis NT thing for myself.
Arkan9 (talk) 10:39, 24 August 2019 (UTC)
PX02013--Overdoze (talk) 17:29, 24 August 2019 (UTC)
Huh, i've never heard of this codename named "Memphis NT" officially before. Weird. Anyways, sorry for the inconvenience TheReleaseTester09 (talk) 14:19, 24 August 2019 (UTC)
Just to get the facts straight, Janus was not the codename of Windows 3.1. It was the codename for a combined MS-DOS 5.0 and Windows 3.1 bundle. --Ryuzaki (talk | contribs) 14:38, 24 August 2019 (UTC)
My bad, i thought it was one of the codenames for Windows 3.1. TheReleaseTester09 (talk) 15:10, 24 August 2019 (UTC)

Just to not to waste effort

I have a suggestion, just change the "The latest released version as of [date]" sentence to "The latest released version as of now" so that admins won't have to edit it every month. TheReleaseTester09 (talk) 16:48, 4 October 2019 (UTC)

Or we could just use {{CURRENTYEAR}} and {{CURRENTMONTH}}. -Meow (talk) 14:39, 20 October 2019 (UTC)

NT 4.0 Codename

According to the Logopedia, the codename of NT 4.0 is SUR (Shell Update Release) but here in the Betawiki.net it's say Shell Release Update (SRU)2001:8A0:E579:7F01:F151:A1E9:5C1E:2337 13:10, 26 December 2019 (UTC)

Because a wiki about logos is surely an authoritative source of information about Windows development... See below for explanation. Sorry, I thought you wanted to correct SUR to SRU. This was a typo that was present for quite a few years. Fixed now. --Ryuzaki (talk | contribs) 14:25, 26 December 2019 (UTC)

In NT 4.0 it says Shell Release Update instead of Shell Update Release, can someone fix this?2001:8A0:E579:7F01:F151:A1E9:5C1E:2337 13:13, 26 December 2019 (UTC)

Same as above. --Ryuzaki (talk | contribs) 14:25, 26 December 2019 (UTC)

This page is 35% vandalsided with the following content. And how we should fix.

  • Remove links for Cardfile, Clipboard Viewer, Clock, Control Panel, Spooler, Terminal and MS Write.
  • Since "Nashvile", "Cairo" and "Neptune" have "italic text", they don't need Never released as their is an indication and for who dosen't know the indications put a 'code' for the indication. Ex.: "Italic" text means version that were never released.
  • NT 4.0's codename show Shell Release Update instead of Shell Update Release.
  • 2000's codename is shown as NT 5 and not NT 5.0.
  • Memphis NT is an unofficial codename for 2000.
  • 3.1x's codename dosen't shows Janus (3.1)
  • Windows 7 has codenames: Vienna and Blackcomb.
  • You're missing MultiPoint servers 2011 and 2012.
  • You should remove 'Whistler era' since Longhorn is the codename of Vista and Blackcomb is a codename of 7.
  1. Remove links for Cardfile, Clipboard Viewer, Clock, Control Panel, Spooler, Terminal and MS Write.
    This change has little to no benefit.
  2. Since "Nashvile", "Cairo" and "Neptune" have "italic text", they don't need Never released as their is an indication and for who dosen't know the indications put a 'code' for the indication. Ex.: "Italic" text means version that were never released.
    See #1.
  3. NT 4.0's codename show Shell Release Update instead of Shell Update Release.
    Fixed.
  4. 2000's codename is shown as NT 5 and not NT 5.0.
    See #1.
  5. Memphis NT is an unofficial codename for 2000.
    This was discussed before on this very page.
  6. 3.1x's codename dosen't shows Janus (3.1)
    Janus was not the codename of Windows 3.1.
  7. Windows 7 has codenames: Vienna and Blackcomb.
    See #5.
  8. You're missing MultiPoint servers 2011 and 2012.
    That's pretty much the only legitimate issue in your post.
  9. You should remove 'Whistler era' since Longhorn is the codename of Vista and Blackcomb is a codename of 7.
    See #1.
--Ryuzaki (talk | contribs) 14:25, 26 December 2019 (UTC)

Please add Windows 10 20H2 and 21H1

Now 20H2(or 21H1)has been pushed to Insiders.Please add them.Thanks! — Preceding unsigned comment added by GT610 (talkcontribs)

No, 20H2 and 21H1 hasn't been actually confirmed by Microsoft yet. Builds 19536 and up are for an unknown release of Windows 10. Arkan9 (talk) 02:19, 9 March 2020 (UTC)

there is a new leaked version of windows 11

i only found an article from XDA, so i dont know if it is real. https://www.xda-developers.com/windows-11-se-cloudeditionl/ — Preceding unsigned comment added by 47.218.253.81 (talkcontribs)

If you check Windows 11 build 21996 page, there is already a mention of Win11 SE Xeno (talk) 21:15, 17 June 2021 (UTC)

Windows 7 and Server 2008 unsupported

This page shows that Windows 7, Windows Server 2008 and Windows Server 2008 R2 are supported. This is no longer true since official support has ended since January 14th 2020. — Preceding unsigned comment added by 222.252.32.221 (talkcontribs)

Windows 7 and server 2008 r2 are still supported under the esu program. for more information, click here MShinoda8768 08:04, 7 September 2021 (UTC)
Those are MS special programs for businesses to keep their W7 machines updated during their migration to Windows 10. — Preceding unsigned comment added by 222.252.32.221 (talkcontribs)

Windows 11 and Legacy BIOS

Actually Windows 11 is still can be booted using Legacy BIOS, as the bootmgr, winload.exe files is still present and it can be installed by using this bypass methods. User:91.213.33.105 (talk) 08:18, 8 November 2021 (UTC)

But it's not officially sanctioned, therefore it's listed as not supported. --Ryuzaki (talk | contribs) 15:22, 8 November 2021 (UTC)

Nearly all builds can be installed on a BIOS PC through this way. Besides there's also NT installer. :) GT610 | Sorry for my poor English! (talk) 15:03, 8 November 2021 (UTC)

What about sections for Windows 8.x, Windows 10 and Windows 11 in the history section?

As of now, the history section of the Microsoft Windows page has detailed history entries from 16-bit Windows to Windows Vista and Windows 7.

However, I think that a history section should be added for Windows 8.x, Windows 10 and Windows 11 at least because this was an era where Windows undergone massive changes like when Microsoft massively updated the UI for Windows 8 to better complete with Android and iOS at the time, When Microsoft released Windows 8.1 to address many of the shortcomings of the original release of Windows 8 like adding the start button back to the Taskbar. After that, in 2014 Microsoft shifted to a new development model called Windows as a Service starting with the release of Windows 10 in 2015.

Do you think that I should at least add detailed history entries for Windows 8.x, Windows 10 and Windows 11? Share your thoughts below.

WindowsGuy2021, 8:29 14 February 2022

Update: Windows 8.x has recently been added to the history section. Only 2 more to go!

WindowsGuy2021, 6:58, 9 June 2022

About the Windows Thin PC ESU mention...

In the notes section, it states that Windows Thin PC will be supported until October 10, 2023 via ESU.

I have been looking at Microsoft's website and there is no mention of Windows Thin PC being eligible for the ESU program.

It is also not listed in the ESU list either.

Support for Windows Thin PC already ended back in October 2021.

WindowsGuy2021, 12:18, 5 May 2022

I think that we should replace the first picture to 22621’s picture.

Hi there. 22621 is the RTM build of Windows 11 22H2, I think we should replace it instead of 22000’s. Thanks!YLMF (talk) 00:10, 16 September 2022 (UTC)

We're not yet at GA. Xeno (talk) 00:11, 16 September 2022 (UTC)
Okay.YLMF (talk) 01:47, 16 September 2022 (UTC)