Windows 8 RTM build reportedly 8500, announcement coming late July

Pull up a seat if you want to hear about some new information regarding the RTM of Windows 8. Wzor, who has been known to leak Windows information in the past, has just updated a post that says Windows 8 RTM build will be  8500.0.120623-1707. We should note this contradicts Win8China's claim that the final build will be in the 8600 class.

Additionally, the source states that Microsoft will make the announcement in late July and says sometime between the 17-20. We should note that two Microsoft events happen during this timeframe. First, on the 19th, Microsoft has their earnings call and also there is the MGX, which runs from July 17-20; the source specifically states that it is coming at the MGX event.

This information lines up to previously released information that says Microsoft will finish the Windows 8 RTM build in July; it would appear that Windows 8 RTM is literally right around the corner.

Windows 8 has been noted to be Microsoft's biggest gamble yet. But, with the hardware/software that was just announced (Microsoft Surface and Windows Phone 8), the entire ecosystem around the platform is coming together. If true, July will be yet another busy month as the company takes one giant step towards Windows 8 retail availability. 

Is it in the 8500 or 8600 class? That we do not know. But, there have now been several sources pointing towards a July sign-off which bodes well for the speculated October release date. 

Thanks to @AngelWZR for the tip and translation!

Report a problem with article
Previous Story

Firefox for Android: Something "big" is coming

Next Story

Some Apple Retina display MBPs suffering from ghosting

38 Comments

Commenting is disabled on this article.

Windows 8 will be a massive flop on the PC side, guaranteed. Tablets will be the only things that keep it alive for any amount of time.

only attraction is hyper-v for me but it seems that it kills video playback on the host so I guess I am passing on windows 8

netsendjoe said,
Whats more interesting is that at this point they've probably already forked development and started working on Windows 9

Probably, but you don't get any interesting features worth writing an article about for 1-1.5 years. And I highly suspect a lot of the features will be in the Metro environment, specifically APIs, so we aren't going to see any tangible leaks about them (how do you leak the screenshot of an API?)

All candidates for release..
Same as these:

8500.0.winmain_win8rtm.120​619-2000
8500.0.winmain_win8rtm.120​620-2000
8500.0.winmain_win8rtm.120​621-2000
8500.0.winmain_win8rtm.120​622-2230
8500.0.winmain_win8rtm.120​623-1707
8500.0.winmain_win8rtm.120​623-2000

Niekess said,
All candidates for release..
Same as these:

8500.0.winmain_win8rtm.120​619-2000
8500.0.winmain_win8rtm.120​620-2000
8500.0.winmain_win8rtm.120​621-2000
8500.0.winmain_win8rtm.120​622-2230
8500.0.winmain_win8rtm.120​623-1707
8500.0.winmain_win8rtm.120​623-2000

We'll have candidates for weeks as they look for bugs. And even after they have an RTM build, they will have bugs to be fixed with day 1 patches.

dagamer34 said,

We'll have candidates for weeks as they look for bugs. And even after they have an RTM build, they will have bugs to be fixed with day 1 patches.

Actually, there will be some 8500 builds compiled now which each something fixed but another thing broke. Out of a collection from these builds will there be one voted. The one with the most votes to be most stable is the real RTM.

Nice. I will now tattoo the build number on my butt cheek. Seriously, I wonder what we're supposed to do with this information, haha

Canouna's latest post is stating that 8500 is only an Escrow and Candidate Build.
Also, whilst it might be 8500, I have a feeling they'll round it off to 8600. Don't they usually have a set divisible pattern for major build numbers?

Possession said,
Canouna's latest post is stating that 8500 is only an Escrow and Candidate Build.
Also, whilst it might be 8500, I have a feeling they'll round it off to 8600. Don't they usually have a set divisible pattern for major build numbers?

Yes, it has to be a multiple of 16 and 100 afaik.

Possession said,
Canouna's latest post is stating that 8500 is only an Escrow and Candidate Build.
Also, whilst it might be 8500, I have a feeling they'll round it off to 8600. Don't they usually have a set divisible pattern for major build numbers?

Why would they want to round off an already round number?

dagamer34 said,

2600 is not divisible by 16.

The rule of "multiple of 16 and 100" was started in Vista, XP did not count.

And obviously MS has changed the rule again.

I don't understand how they can go to RTM so soon. If you look at the surface demo there were obvious problems with the Metro part of Windows 8. I hoping they fix at least 95% of the bugs before release but some how I doubt it.

Melfster said,
I don't understand how they can go to RTM so soon. If you look at the surface demo there were obvious problems with the Metro part of Windows 8. I hoping they fix at least 95% of the bugs before release but some how I doubt it.

Who knows even the RTM is just a "Preview"

Melfster said,
I don't understand how they can go to RTM so soon. If you look at the surface demo there were obvious problems with the Metro part of Windows 8. I hoping they fix at least 95% of the bugs before release but some how I doubt it.

the surface demo mishap I call hardware issue.

rfirth said,
Are you talking about when the Surface froze? That was probably graphics drivers. It was terrible timing, though.

What have graphics drivers to do with Internet Explorer not properly responding to touch input? It began with that.

Melfster said,
I don't understand how they can go to RTM so soon. If you look at the surface demo there were obvious problems with the Metro part of Windows 8. I hoping they fix at least 95% of the bugs before release but some how I doubt it.

Well. Unfortunately, they won't be fixed until it comes out of the market. It happened on a little scale with Windows 7. After a few months of stability patches, the OS will be good to go.

.Neo said,

What have graphics drivers to do with Internet Explorer not properly responding to touch input? It began with that.
If the hardware driver or the hardware itself fails to respond properly, then the software appears to have crashed?

Just as a heads-up and because I don't see it mentioned in the article, if WZor's right then the RTM was compiled yesterday.

8500.0.120623-1707
12 - 06 -23 = June 23rd 2012.

SekaiStory said,
Just as a heads-up and because I don't see it mentioned in the article, if WZor's right then the RTM was compiled yesterday.

8500.0.120623-1707
12 - 06 -23 = June 23rd 2012.

It can be true , coz even RP had a 2 week long voting period . But i don't want to believe.

SekaiStory said,
Just as a heads-up and because I don't see it mentioned in the article, if WZor's right then the RTM was compiled yesterday.

8500.0.120623-1707
12 - 06 -23 = June 23rd 2012.

It's more accurate to call it an RTM escrow build. Its not officially RTM until it passes all of their checks.

I do have a question though. Since Metro apps need to be tested against the RTM build of the OS, wouldnt Microsoft need to give the final bits to developers before general availability?

dagamer34 said,

I do have a question though. Since Metro apps need to be tested against the RTM build of the OS, wouldnt Microsoft need to give the final bits to developers before general availability?

Yep, we'll get Windows 8 final on MSDN shortly after it RTMs (we got Win7 15 days after RTM). I imagine we'll have Visual Studio 2012 on or around the same day, too.

I don't think they have fixed bugs like context menu going behind the windows, some music players going mad on pressing enter (iTunes) , Start Screen is still not isolated from explorer.exe , makes you feel that Desktop app is not an app but instead the metro interface is part of Desktop app hence it feels so wrong (to try this kill explorer.exe) http://trunc.it/l5pj1 . Further adding new GUI without public testing , is lil weird... I mean to me Win8 RP doesn't feel as polished as Win7 RC was...

bogas04 said,
I don't think they have fixed bugs like context menu going behind the windows, some music players going mad on pressing enter (iTunes) , Start Screen is still not isolated from explorer.exe , makes you feel that Desktop app is not an app but instead the metro interface is part of Desktop app hence it feels so wrong (to try this kill explorer.exe) http://trunc.it/l5pj1 . Further adding new GUI without public testing , is lil weird... I mean to me Win8 RP doesn't feel as polished as Win7 RC was...

The RP build we all are using is from way back in mid-May. And explorer.exe is not desktop, but the entire Windows Explorer shell which was also true of Windows 7 and earlier.

Abhinav Kumar said,

The RP build we all are using is from way back in mid-May. And explorer.exe is not desktop, but the entire Windows Explorer shell which was also true of Windows 7 and earlier.

You are not getting my point , of course explorer is explorer as it was since idk Win 98. I am saying that by including Metro interface and calling Desktop as some another app doesn't make sense when the entire interface still depends on "explorer.exe" , they way it is depicted is not the way it is implemented.
Further yes i agree the 8400 build is quite old and separate branches even in that period were quite advanced , but it still is not as , you know , good and solid , as Win7 RC was... I do run into problems mentioned above every now and then... Especially that context menu going to back most layer making it impossible to work...

bogas04 said,

You are not getting my point , of course explorer is explorer as it was since idk Win 98. I am saying that by including Metro interface and calling Desktop as some another app doesn't make sense when the entire interface still depends on "explorer.exe" , they way it is depicted is not the way it is implemented.

Why does that matter? Sure, it looks like the desktop is an app. And of course, it isn't. That's because Microsoft decided to not add another layer on top of the desktop, but instead just add it to the desktop. That's not a bad thing. This is also why the metro snap works.

bogas04 said,
I don't think they have fixed bugs like context menu going behind the windows, some music players going mad on pressing enter (iTunes) , Start Screen is still not isolated from explorer.exe , makes you feel that Desktop app is not an app but instead the metro interface is part of Desktop app hence it feels so wrong (to try this kill explorer.exe) http://trunc.it/l5pj1 . Further adding new GUI without public testing , is lil weird... I mean to me Win8 RP doesn't feel as polished as Win7 RC was...

Why does it need to be separate? Metro IS the OS, not just some addon. Which means it'll never be separate, and nor should it.

Out of curiosity, if it did RTM in July and retail release is set for October, when would it be available on MSDNAA? I seem to remember Windows 7 showing up just before retail release, but I can't really remember.

WelshBluebird said,
Out of curiosity, if it did RTM in July and retail release is set for October, when would it be available on MSDNAA? I seem to remember Windows 7 showing up just before retail release, but I can't really remember.

Yeah, I also seem to remember Win7RTM going on MSDNAA early.

Xerax said,

Yeah, I also seem to remember Win7RTM going on MSDNAA early.

From a quick google, Windows 7 RTM'd in July and had an October retail release too, and it seems it went ob MSDNAA in August. Really hope that is the same for windows 8. I am graduating this year and lose access to MSDNAA at the end of August. So if I can get a copy beforehand, then I'll be happy

WelshBluebird said,
Out of curiosity, if it did RTM in July and retail release is set for October, when would it be available on MSDNAA? I seem to remember Windows 7 showing up just before retail release, but I can't really remember.

MSDN/Technet got windows 7 15 days after RTM. I think MSDNAA is up to your school admin to publish it.