History Of Naming Windows (feat.
Вставка
- Опубліковано 23 сер 2024
- Socials and merch @ www.windowsonwi...
Over the years, Microsoft has used different naming strategies for Windows. Originally, names corresponded to version numbers (1/2/3). In 1995, Microsoft chose to name the newest version of Windows "Windows 95", to "herald in a new epoch of Windows", according to Windows team leader, Brad Silverberg. Since then, Microsoft has also named Windows releases using monikers and numerals. Watch to find out more...
With thanks to @Everything.Windows for Rowland Hanson's narration, @BlueOSMuseum for the footage of Steve Ballmer's Windows 1 "ad", Windows 95's usability testing and launch, Microsoft for the audio of Brad Silverberg (from their podcast, Beyond The Blue Badge), @CNETSecurity for the footage of Mike Nash and @MichaelMJD for Mike Nash's narration.
Disclaimer: Any images and/or video clips used in this video are believed to be in the public domain, unless otherwise credited. If you recognise an image and/or video clip that is not credited and believe this is in error, please contact admin@windowsonwindows.com. Credit will be happily given, or the content in question removed, as per the copyright holder's wishes.
#WindowsOnWindows #Microsoft #Windows #Windows95 #Names #Naming
👨🏻🏫 Count to 11 with Microsoft: 1, 2, 3, 3.1, NT 3.1, NT 3.5, 95, NT 4, 98, 98 SE, 2000, ME, XP, Vista, 7, 8, 8.1, 10, 11. 🤓
What about 11.1?
@@hibbiea8841 Windows 11 2022 Update (22H2) would be 11.1 if Microsoft used normal version numbers.
U forgot 3.51
and 3.11
@@mrlemonade281
To be honest, Windows version numbers aren't really relevent to anything. They're often weird for compatibility reasons. Windows 95 reports its version number as 3.95, because there were tons of buggy apps which would break if they saw 4.0. Windows 10 sometimes says it’s 6.2, again for compatibility reasons. Windows developer Raymond Chen doesn't know the version numbers, as he once stated in a blog post titled "How to tell the poseurs from the actual Windows developers".
Very good point!
I assume they would think that 4.0 means Windows NT 4, what does Windows Me report? Windows NT kernel version reported 5.0 on XP and 2000, 6.x on Vista, 7, 8, and 10.0 on Windows 10 and 11
@@kreuner11 Windows 95 came out one year before NT 4, the compatibility was with software that would lazily check for Windows 3.1+ with (major == 3 && minor > 0), or slightly less lazily with major >= 3. The correct check would be ((major == 3 && minor > 0) || major > 3)). I believe the fake numbers the later 9x versions reported were 3.98 and 3.99.
never thought about how the naming system basically came full circle. Very informative vid!
Glad you liked it!
Love the comedic ending to this, the genuine confusion in your voice sells it.
And now this year’s release will be “Windows 11 2024 Update”, so we’ll have to wait even longer for the next chance to sync the NT version back up (or get rid of it-it’s mostly been replaced by YYHX now).
@@techwithtyler20 YYHX? what is this a new song by Rush in the vain of YYZ 🤣
@@PH96Official YYHX is the format of Windows version numbers as of 2020 (e.g. 24H2 for 2024 half 2).
No surprise-they deprecated the NT number’s use with Windows 10 1511, with the YYMM/YYHX number being used instead. Now with Windows 10 and 11 being 10.0, the version number is slightly different internally. For example, Windows 11 21H2 had an internal release ID of CO21H2, while Windows 10 21H2 was simply 21H2.
Not only that, but starting with Windows 10 v1511, the build number must divide by 3 rule was eliminated. For whatever reason, starting with Windows Vista and ending at Windows 10 RTM, all RTM build numbers must be divisible by 3. Reports suggest that Windows 8's final RTM build number was supposed to be 8888 instead of 9200, but due to the number 8888 being indivisible by 3, it was instead compiled as a Pre-RTM build and build 9200 would become the RTM build. I still don't understand why the Windows build numbers starting at Vista and ending with 10 RTM, all had to divide by 3.
@@winelectronic101 Excluding service packs.
@@winelectronic101 9200 isn't divisible by 3. BetaWiki says the rule was that it must be divisible by 16.
_Microsoft at their office_
an employee : show me the difference between these two.
*shows Windows 10 and Windows 11*
Panos Panay : I can see no difference
😂😂😂
btw great time to make a cameo voiceover the 2nd time haha
6:38 Actually, Windows 9 is Windows 8.1, why? Because, 9^2 (9 Squared) is Equals to 81 and then divided by 10 is 8.1. So :
9^2/10 = 81/10 = 8.1
Even VMware expected it to be called Windows 9. If you create a Windows 10 VM, the guestOS variable will be set to "windows9" or "windows9-64" depending on the guest machine's "bitness." I've now learned that bitness is a term that people have documented.
With Windows 11 still being marked as Windows NT 10.0, it is likely that most (if not all) apps designed for Windows 10 will run on Windows 11.
Windows 11 was going to be just another 10 update, but the massive changes and raised system requirements were too much for an update to "Windows 10". People would've been looking for ways to "make Windows 10 look like...Windows 10?".
Most likely the NT number is deprecated, as the YYHX and build numbers are what to check for now. As both Windows 10 and 11 have a "21H2", 21H2 refers to 10 and CO21H2 refers to 11, so apps can know that way. I would guess 11 22H2 is NI22H2.
And the feature updates didn't add .1 to the version number.
@@techwithtyler20 the ridiculous part is, the Windows 8.1 has a different NT version number compared to Windows 8.
@@GinanjarUtomo I know, so I was expecting Windows 10 Anniversary Update to be NT 10.1, Creators Update 10.2, etc.
Windows is all about versions, and sometimes codenames are also legit to be heard in development cycle.
MajorSky17's videos are always cool.
December 18, 2022 3:03AM
Glad you enjoy them. 😄
I'm a software developer and in my professional life I have struggled many times with the Windows Kernel version number. In Windows server this number has not changed since 2016 I believe. Instead you have to look at the year/month of release. E.g.: 1910, or 1704. THEN: Windows 11 came around. Which has the SAME kernel number as WIndows 10: kernel 10. And many times, the SAME year/month of release!!! So: Windows 10 21H1 would be the same as WIndows 11 21H1 as far as the Windows registry is concerned...
My reaction upon discovering that 'feature', was exactly the same as yours at the end of the video :'-)
You can imagine that the simple code that used to be is littered with if/else statements now. Upon that discovery I gave up, deleted the function, wrote a new one, had countless discussions with the product manager and finally the code works as intended. Now we use the OS string and extract the "2016" from "Microsoft Windows Server 2016 Enterprise" for instance.
Then I found out that Windows Vista has a trademark symbol after I believe "Windows". And Windows 2008 has a copyright sign if I remeber correctly. Sooo... the if statements are back baby!
Sorry, I needed to vent haha O:-)
Internally, the Windows 11 version number has the element abbreviation in front of it, so Windows 10 21H2, for example, is 21H2, while Windows 11 21H2 is CO21H2.
Did I hear Michael MJD’s voice in this episode?
Hol' up! Is Windows 11's version number NT 10.0?! :O
Yep! Windows 11 is the first Windows version to have the exact same kernel version number as its predecessor. 🤓
@@WindowsOnWindows Damn Microsoft xD
NT version is likely deprecated in favor of YYHX and increasing use of build numbers. In some cases, you need a specific dot revision of a given build to run some apps. For example, Apple says the store version of iCloud only runs on 18362.145 and later, not just any 18362. This will likely be the norm as the UI and major features can now come in minor updates, just like with everyone else.
Yeah I was like WTF MICROSOFT
Windows Vista and Windows Me are my favourite Windows names.
Yeah, Microsoft and their weird ways to count
They don't even do point releases for 10/11 feature updates (e.g. Windows 10 Anniversary Update should've been 10.1).
Great video
Glad you liked it! 👍
Windows 11 with version 10
Let's not forget it was going to be just another 10 update, but the massive changes would've not worked out as well if so. Making "Windows 10" look like the old "Windows 10" wouldn't be an easy thing to search for.
They deprecated the kernel version and probably pushing applications to rely on version YYMM/YYHx or build numbers.
@@ThatRandomToast That's most likely the recommended approach now when an app detects NT version 10.
Thats because for compatibility with Windows 10 apps
@@jacquelinedelossantos426 They would've only had those apps report 10.0 if that was the case--they appear to have deprecated the use of the NT version number, with the YYMM/YYHX and build numbers being what to check instead.
Windows 10, while the reported NT number is 10.0, it will always be 6.4, and Windows 11, its NT 6.5, after all these years of making Fun of Vista (NT 6.0) we are still runing it, or at least its base code, dont believe me? check the date of the default windows drivers, and compare them to the timing of windows releases
imo windows 11 isn't even a true upgrade, it's like comparing windows vista and 7 and saying 7 was a major upgrade over vista. 11 just changed the ui
And system requirements. Both things would get tons of negative reception in an update to "Windows 10". It isn't easy to search how to make Windows 10 look like...Windows 10, although we already had that with Windows 10 Anniversary Update's start menu redesign.
@@techwithtyler20 even the system requirements can be bypassed
also true, however if they were planning an all out new os they should've went ahead and made few more major changes like bringing nt kernel 11
@@aanjaneya_meaow NT version was deprecated as of Windows 10 version 1511. Developers should now check against the YYMM/YYHX version number or the build number if the NT version is 10. Apps not updated for 8.1 or later will report NT 6.2.
@@techwithtyler20 oh gosh it's even worse
If windows kept the simple numbering system I think this is how it would have gone
9x based systems:
Windows 95 - Windows 4
Windows 98 - Windows 4.1
Windows 98 SE - Windows 4.5
Windows ME - Windows 4.5+
(Basically, all 9x versions of windows are some variant of Windows 4, comparing windows 95 to ME, you really see how similar they are at the core)
NT (Not including pre-2000)
Windows 2000: Windows 5
Windows XP: Windows 6
Windows Vista - 7
Windows 7 - 8
8 becomes 9, 8.1 would probably be 9.1, and then 10 would be 10
@MichaelMJD, when is your face reveal?
It'll be included in the 50th anniversary of his channel.
@@alexander_strachan are you joking?
@@AEIOUY234689 Umm, yes...
Mjd will reveal his face in Mid 2024
@@hibbiea8841 too late to wait
7:52 Why the Kernel Version of Windows 11 is still 10.0, not 10.1 or 11.0? But, Version 10.0 is for Windows 10.
NT version was deprecated as of Windows 10 version 1511. Developers should now check against the YYMM/YYHX version number or the build number if the NT version is 10.
It's for app compatibility. But the NT version is no longer shown on winver, and is hidden.
Is that Ballmer promoting windows 1?
Yep!
To be honest I see windows 11 as windows 10.1