[RTM] Windows 8 - CONFIRMED Windows 8 RTM Build = 9200.16384.win8_rtm.12072


Recommended Posts

The Windows Team blog confirms: Windows 8 has reached RTM. As for availability:

  • August 15th: Developers will be able to download the final version of Windows 8 via your MSDN subscriptions.
  • August 15th: IT professionals testing Windows 8 in organizations will be able to access the final version of Windows 8 through your TechNet subscriptions.
  • August 16th: Customers with existing Microsoft Software Assurance for Windows will be able to download Windows 8 Enterprise edition through the Volume License Service Center (VLSC), allowing you to test, pilot and begin adopting Windows 8 Enterprise within your organization.
  • August 16th: Microsoft Partner Network members will have access to Windows 8.
  • August 20th: Microsoft Action Pack Providers (MAPS) receive access to Windows 8.
  • September 1st: Volume License customers without Software Assurance will be able to purchase Windows 8 through Microsoft Volume License Resellers.

Source: Windows Team Blog

The Windows Team blog confirms: Windows 8 has reached RTM. As for availability:

  • August 15th: Developers will be able to download the final version of Windows 8 via your MSDN subscriptions.
  • August 15th: IT professionals testing Windows 8 in organizations will be able to access the final version of Windows 8 through your TechNet subscriptions.
  • August 16th: Customers with existing Microsoft Software Assurance for Windows will be able to download Windows 8 Enterprise edition through the Volume License Service Center (VLSC), allowing you to test, pilot and begin adopting Windows 8 Enterprise within your organization.
  • August 16th: Microsoft Partner Network members will have access to Windows 8.
  • August 20th: Microsoft Action Pack Providers (MAPS) receive access to Windows 8.
  • September 1st: Volume License customers without Software Assurance will be able to purchase Windows 8 through Microsoft Volume License Resellers.

Source: Windows Team Blog

Why does it not say when pirates get it ? :p

Great!

So DreamSpark (MSDNAA) will get it August 15th as MSDN?

I'm wondering this as well.

really want to get this through my school DreamSpark account :)

Good morning Guys! ..... I already said discussions on manipulating the RTM images is dangerous LOL :cry:

Anyway, WZOR just updated his post, first part is just blah-blah over the 8888 things where nobody is interested - just note the high-lighted part - Hope that he's right this time !

screen1150.jpg

Google translate:

added 08/01/2012 An hour ago Sinovsky Steven (Steven Sinofsky) announced on his blog that the final build of Windows 8 build was 9200, so that the dispute WZor vs Canuona won youth. Maybe it's a good excuse to go to bed uncle? None of our sources in the corporation was unable to foresee, for many it came as a surprise. Although if you honestly say that for me just seemed to build 8888 Steve Sinovski joke, so to speak in anticipation of the opening of the Olympic Games in London, too much like 8888 Olympic "Ring of Destiny" .... But that is little utishenie, and therefore "can throw stones" in the comments .. The first drain I expect around 6 am GMT

I'm not trusting anything wzor says, he's been wrong FAR too many times to be considered a reputable source of information.

LOL, I trust him 50/50. His luck went out when MS got a glitch when testing 8888 with OEM's and decided they don't have any more time to fix it;

But what he said about 9200 being win9 just lmao, like he's just a total noob. :laugh:

LOL, I trust him 50/50. His luck went out when MS got a glitch when testing 8888 with OEM's and decided they don't have any more time to fix it;

But what he said about 9200 being win9 just lmao, like he's just a total noob. :laugh:

Actually the 8888 thing had nothing to do with any bug. 8888 and 9200 are basically identical except for the fact that 8888 broke their servicing infrastructure because of the 16 and 10 rule. And since they already went past 8800 with the 8888 joke they have to rev up to 9200 (next number divisible by 16 while also being divisible by 10)

Actually the 8888 thing had nothing to do with any bug. 8888 and 9200 are basically identical except for the fact that 8888 broke their servicing infrastructure because of the 16 and 10 rule. And since they already went past 8800 with the 8888 joke they have to rev up to 9200 (next number divisible by 16 while also being divisible by 10)

That's my point, the number 8888 caused a QFE glitch, MS had almost fixed it and kept the intended RTM no. they always wanted. I suspect canouna knew something about it(if I caught wind thru my channels, he has better connections than me). Anyway, it's all history. :D

More Windows 8 RTM Screenshots.

post-301496-0-15783200-1343885817_thumb.

post-301496-0-47720300-1343885828_thumb.

post-301496-0-94589000-1343885858_thumb.

Source (More walls shown here): http://bbs.pcbeta.co...085086-1-1.html

:D

I can't believe that they are shipping with the same icon set! Legitimacy of these screenshots is very very questionable!

I can't believe that they are shipping with the same icon set! Legitimacy of these screenshots is very very questionable!

MS is just being lazy and not changing their old Aero icons (some of which from Vista) to a more newer Metro look. But RTM is indeed shipping with Aero icons for desktop mode :(. (I guess they are saving some features/UI to be added in the more refined Windows 9)

Slightly OT:

A friend of mine has an OEM copy of Windows Vista Ultimate. Will she be eligible for the Windows 8 Pro upgrade pricing?

I was afraid they were going to do this thing with the icons(actually i was sure they were gonna leave them as is).

It is AMAZING how hard they try to achieve a unified look among their products and services making them all metro but yet they leave something so important that users will have in front of them almost all the time,unchanged.

If you want consistency then icons is a major factor and it is surprising how smth so small makes such a big difference in the feeling of the OS.

  • Like 2
This topic is now closed to further replies.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop 'Google Chrome' is downloading without you agreeing to it. Fun right? Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!