Are there any Windows 9 builds?

[HedgehogWin7]

Does anyone know of any Windows 10 builds with the Windows 9 name? All I know about them is that they triggered code for 9x, and it said that the program is not compatible.

[Windows Thunderstruck]

no they arent any windows 10 builds called windows 9
the earliest two (9780 and 9785) just called themselves windows 8.1

[captainlinux8880]

Does anyone know of any Windows 10 builds with the Windows 9 name? All I know about them is that they triggered code for 9x, and it said that the program is not compatible.

I think not. For this, a release version of Windows 9 should have been released, but Tony Prophet, the head of Windows marketing said that the name Windows 9 could get Windows 8.1, but Microsoft did not want Windows 9 to be associated with the unpopular Windows 8. So they already decided that windows 9 was already there, albeit with the name windows 8.1, so the decision was immediately made to name the new product "Windows 10".

[Fanta Shokata]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

[captainlinux8880]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

also a good option

[Meow]

Do some research (not much) and you will quickly find out that there were NEVER any Windows 9 branded builds.

[Xeno]

The closest you're going to get to Windows 9 is in the file "C:\windows\System32\migwiz\replacementmanifests\CommandPrompt-Win8-Replacement.man"

Code: Select all

  <!-- Gather blocks required for collecting data from Windows 8, Windows Blue, and some Windows 9 systems -->
  <!-- Apply blocks required for applying to Windows 9 versions built BEFORE the correct CommandPrompt.man reaches winmain -->
  <!-- The body of this should match CommandPrompt.man to fix Win9 systems before the changes reach winmain -->
  <!-- 9845 is a guess of the build version when this will reach main. The correct CommandPrompt.man will be used after that build -->

[dixieLH]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

thats what they say...
to me its most likely just the moniker "10" as in X (osx anyone ?), more appealing to masses

[HedgehogWin7]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

Did they test it out?

[Random_User]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

That's not how the version check works. When applications check the Windows version, they rely on the version number -- (NT) 9.0 being mistaken for 4.0 or 4.1 would have been unlikely.

[winnt32]

actually, it is, because they - supposedly - weren't checking ir properly and were checking for the string "Windows 9" somewhere.

[HedgehogWin7]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

That's not how the version check works. When applications check the Windows version, they rely on the version number -- (NT) 9.0 being mistaken for 4.0 or 4.1 would have been unlikely.

Then why did they skip Windows 9?

[ToMi1]

It is hard to understand Microsoft's product branding.

[HedgehogWin7]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

That's not how the version check works. When applications check the Windows version, they rely on the version number -- (NT) 9.0 being mistaken for 4.0 or 4.1 would have been unlikely.

Well, if NT 9 didn't trigger code, then don't call it 10, call it 9! Simple!

[Meow]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

That's not how the version check works. When applications check the Windows version, they rely on the version number -- (NT) 9.0 being mistaken for 4.0 or 4.1 would have been unlikely.

Well, if NT 9 didn't trigger code, then don't call it 10, call it 9! Simple!

I don’t think you understand what MS wanted to do. They said Win10 was the last version of windows (which might not be true now) and MS wanted to stop on a number that would be appealing to most people and 9 was not that. 10, on the other hand, was.

[AlphaBeta]

actually, it is, because they - supposedly - weren't checking ir properly and were checking for the string "Windows 9" somewhere.

indeed, I believe the rumor called out Java apps in particular that checked the OS version by using `System.getProperty("os.name")`

[rixolino]

Microsoft skipped Windows 9 because some programs would check if Windows version was 95 or 98.

I'm agree with you

[Googulator]

Also, Windows 8 and Windows 8.1 together were being referred to online as "Windows 8x". Imagine what that would've meant for Windows 9 and 9.1... (at the time, Redstone was planned to be numbered 9.1, and later 10.1, although that never happened)

[HedgehogWin7]

What's the real reason they skipped Windows 9?

[tarquin44]

What's the real reason they skipped Windows 9?

Windows 95. Windows 98 and Windows ME were collectively known as Windows 9x.

[Pluto950]

The closest you're going to get to Windows 9 is in the file "C:\windows\System32\migwiz\replacementmanifests\CommandPrompt-Win8-Replacement.man"

Code: Select all

  <!-- Gather blocks required for collecting data from Windows 8, Windows Blue, and some Windows 9 systems -->
  <!-- Apply blocks required for applying to Windows 9 versions built BEFORE the correct CommandPrompt.man reaches winmain -->
  <!-- The body of this should match CommandPrompt.man to fix Win9 systems before the changes reach winmain -->
  <!-- 9845 is a guess of the build version when this will reach main. The correct CommandPrompt.man will be used after that build -->

Checked my PC and these strings are still here on my Version 2004 Win10 setup.

[Pluto950]

The closest you're going to get to Windows 9 is in the file "C:\windows\System32\migwiz\replacementmanifests\CommandPrompt-Win8-Replacement.man"

Code: Select all

  <!-- Gather blocks required for collecting data from Windows 8, Windows Blue, and some Windows 9 systems -->
  <!-- Apply blocks required for applying to Windows 9 versions built BEFORE the correct CommandPrompt.man reaches winmain -->
  <!-- The body of this should match CommandPrompt.man to fix Win9 systems before the changes reach winmain -->
  <!-- 9845 is a guess of the build version when this will reach main. The correct CommandPrompt.man will be used after that build -->

I assume 9845 would be considered a Win9 build, then?

[EverythingeeB]

What's the real reason they skipped Windows 9?

Microsoft said they skipped Windows 9 because "it didn't feel right" to them. They also wanted to prioritize development on Windows 10. It's kinda like today where Microsoft skipped Windows 10 Sun Valley to prioritize Windows 11 development. (Not saying Sun Valley won't come out, it's just that feature development likely will stop for it.

[AlphaBeta]

What's the real reason they skipped Windows 9?

Microsoft said they skipped Windows 9 because "it didn't feel right" to them. They also wanted to prioritize development on Windows 10. It's kinda like today where Microsoft skipped Windows 10 Sun Valley to prioritize Windows 11 development. (Not saying Sun Valley won't come out, it's just that feature development likely will stop for it.

...but Windows 11 is literally Windows 10 with Sun Valley?

[EverythingeeB]

What's the real reason they skipped Windows 9?

Microsoft said they skipped Windows 9 because "it didn't feel right" to them. They also wanted to prioritize development on Windows 10. It's kinda like today where Microsoft skipped Windows 10 Sun Valley to prioritize Windows 11 development. (Not saying Sun Valley won't come out, it's just that feature development likely will stop for it.

...but Windows 11 is literally Windows 10 with Sun Valley?

Not exactly. I feel like there are quite a few key differences with Windows 11 and Windows 10 Sun Valley. If you actually use it like I have been for the past week or so you'll know that there are quite a few differences compared to Windows 10.