Win7-RTM, when will be the MSDN/Technet release?

[Argi]

I wouldn't bother with any of these while there's still talk of another minor build in the works. Start preparing to install, but wait until it's officially up.

[FaiKee]

x64 running, full ISO in small devil.(Please don't ask/PM for links) :o

[Yusuf M. Veteran]

I guess it won't be available on MSDN/TechNet today. :(

[deletedxyz]

Awesome! This means my laptop will turn to Windows 7 Ultimate early next month. Come on Technet!

[Raa]

I guess it won't be available on MSDN/TechNet today. :(

We knew it wouldn't. Give it ~2 weeks ;)

[FaiKee]

The RTM Final Build would be expected in a few days(ATM Jul. 16), since everybody had been expecting the RTM to be 7300(I had mentioned it won't be), this is the reason, please correct me if I am wrong:

The Final RTM Build number has a requirement: it must be divisible by 16, and MS had a tradition to round the number to 100, the closest candidate is 7600, the next one would be 8000. This is required because the QFE Team needs it to develop Service Packs, max. 16 SP's. MS wouldn't choose the number 8000 because Windows SPI Getversion could only support the greatest build number of 16383, MS had to leave room for the later releases.

Please therefore do not speculate on something like 7700 or 7777, it just won't happen, it has to be 7600.

As for the minor build number 16384, it's because hotfix rquires on the binary string of the minimum minor build number has to be [1] for the 14th bit, i.e. 2^14=16384, there are no further restrictions on the following minor build numbers, therefore, if zukona is right, we might be seeing MS announcing the Win7 RTM Final Build 7600.19000 on Jul. 16, 2009.(Hopefully I could report earlier than that.)

[sjaak327]

Glad to see you decided not to stop posting on this site, and instead being the one that can report the news.

Now I just wait for something from Redmond, if you don't mind, it seems there is too much bull**** doing the rounds on the Win7 RTM.

[FaiKee]

Glad to see you decided not to stop posting on this site, and instead being the one that can report the news.

Now I just wait for something from Redmond, if you don't mind, it seems there is too much bull**** doing the rounds on the Win7 RTM.

Thanks. Now the world is watching the key-note, I do hope that the Ruskies were wrong, and the RTM would be announced.

Edit: WZOR new report (I always check that my reports are not posted elsewhere.)

[Google translation]

The branch builds WIN7_RTM:

6.1.7600.16384.win7_rtm.090710-1945 - possible FINAL RTM build.

6.1.7600.16385.win7_rtm.090713-1255 - possible FINAL RTM build.

We can confirm that the assembly actually 6.1.7600.16385.090713-1255 opportunities, but at the moment the tag 16385 - this is just WDK, have left the system over the last 16384 tag that is itself a system with such a tag 7600.16385 - have not yet met ! may build happening right now.

Prior to the signing of the (sign-off) RTM builds of the branch WIN7_RTM their tags can be changed with the advent of new assemblies. It is naive to believe that was the final release will be the first assembly in the final series of legislative assemblies 7600.WIN7_RTM.

When the audit of the code will stop and will then finally assembled a single-tion "gold code" Windows 7, and then in the final assembly of all WIN7_RTM we'll see something like this build: 7600.18000, 7600.19000, or this. But even when the resulting code is given PC manufacturers that is still possible OEMschikam audit RTM code, because the assembly of multiple signatures, the final signature (sign-off) will end on 31 August and 1 September, it has given subscribers via MSDN and TechNet.

This in no way affect the quality of products delivered to manufacturers of new PC because all changes made to the system once the producers get assembled after July 24 will be available through Windows Update, as new sales of PCs preloaded with Windows 7 will start from 22 October.

PS: Numerology in the Microsoft case is very ungrateful and slippery, so I would recommend tack to take bets, not progadaete! :)

Therefore, my reasoning on hypothetical numbers of tags must be read exactly as was correctly understood some of these visitors:

- The eyes, however, it is possible to rebuild 7600.16386 because Vista was 6000.16386. Most likely, and would be similar to Vista: 6000.16384, 6000.16385, 6000.16386. - Raiker

... the likelihood of re-7600 is very high. Let me remind you that Vista build 6000 has met three times (6000.16384, 6000.16385 and 6000.16386 RTM).

So I have to celebrate the RTM wait until there is reliable information on the signing of the final. - Spellozz

Edited July 14, 2009 by FaiKee

[red77stars]

Are you guys saying that one of these sub builds might bring new icons and sound scheme?

[FaiKee]

Are you guys saying that one of these sub builds might bring new icons and sound scheme?

most unlikely, mate, don't believe they have the leisure at this stage. :wacko:

[FaiKee]

[Google translation]

tomorrow (in the MSK will be after) signing, then they will start to spread, and then merge it and will not until 18 so that the rest until I then my words (which up to 19 +) confirmed

(side note: zukona had mentioned it is 99% sure the RTM Final within this week)

[Cldmani]

Awesome news FaiKee, thanks for the update =)

[wguimb]

[Google translation]

tomorrow (in the MSK will be after) signing, then they will start to spread, and then merge it and will not until 18 so that the rest until I then my words (which up to 19 +) confirmed

(side note: zukona had mentioned it is 99% sure the RTM Final within this week)

Yes, thanks FaiKee. This is good news, I think. ;) Aww, can you translate the translation for us?

[Cldmani]

Yes, thanks FaiKee. This is good news, I think. ;) Aww, can you translate the translation for us?

This seems to have popped up in WZOR too now.

[BoDEAN]

Waiting for links.

[Lindkvist]

And we need to know that, because...?

Could we drop the 'twitterish' posts, and stick to relevant info for a change...

[Gio Takahashi]

While I hope that this is true, I'll be content with the official news.

[Robbie Khan Reviews]

Am I right in thinking that if I installed a 7600.xx build since that's now locked that I can simply reactivate with my retail key once win7 pro arrives in the mail?

I'll be installing Home Pro btw from the 7600 build not ultimate as it automatically defaults to. To choose simply delete ei.cfg after extracting the ISO image's contents.

[Yusuf M. Veteran]

Am I right in thinking that if I installed a 7600.xx build since that's now locked that I can simply reactivate with my retail key once win7 pro arrives in the mail?

I'll be installing Home Pro btw from the 7600 build not ultimate as it automatically defaults to. To choose simply delete ei.cfg after extracting the ISO image's contents.

Assuming build 7600.16384 goes gold, then maybe. But even then it might not work. According to Tom W, build 7600.16385 has been compiled.

[Cldmani]

Assuming build 7600.16384 goes gold, then maybe. But even then it might not work. According to Tom W, build 7600.16385 has been compiled.

And uploaded.

[Robbie Khan Reviews]

Ah hmm, I would have thought they'd not make any further changes to activation process regarding keys though :(

[FaiKee]

Yes, thanks FaiKee. This is good news, I think. ;) Aww, can you translate the translation for us?

Sorry, that was nighttime in Hong Kong....."translate the translation"?? Couldn't get your meaning.

btw, you're going strong on the new liver.

Assuming build 7600.16384 goes gold, then maybe. But even then it might not work. According to Tom W, build 7600.16385 has been compiled.

Of course Tom knew about 16385, I provided all the reports and proofs in another thread he closed one day before the other guy started another thread on 16385. (btw, I just realized that I had learned the hard way, don't mention pxxxxxx-jokes, it triggers thread closings LOL).

[Inctye]

Assuming build 7600.16384 goes gold, then maybe. But even then it might not work. According to Tom W, build 7600.16385 has been compiled.

So then 16385 is the final? Guess we have to find out.

[FaiKee]

So then 16385 is the final? Guess we have to find out.

From what I learn from a "friend": Big partners like Intel, HP....etc are constantly calling the MS big-shots asking for current situations, and MS had to explain things like what the win7 core guys are upto, build-strings maybe, these info eventually leaks. But then when things like full MD5 or even the ISO is accessible, it means the build had been put to a lower level of authorization.......

[Raa]

It's not finished. Give it a few more days. Then a few more for a leak. Then a week or three for the MSDN/Technet release. (The topic.)