7600.16399.amd64fre.win7_gdr.090722-1835

[nekrosoft13]

There is a new build number

yesterday on the web 7 windows 7 updates leaked, after installing these updates the windows build get changed to 7600.16399.amd64fre.win7_gdr.090722-1835

Dated July 22nd 2009.

not my screenshot

[mailman2]

x86 and x64 both included:
http://hotfile.com/dl/9453482/b1c262...dates.rar.html

x64:
Code:
http://rapidshare.com/files/262171872/x64.rarx86:

x86:
http://rapidshare.com/files/262171846/x86.rar

[AthlonXP1800]

Thanks for the download links.

I wonder what had changed from build 7600.16385 to 7600.16399?

I think Microsoft had rushed 7600.16385 as RTM, but on 22 July 7600.16399 is the real final that should be RTM. Maybe 7600.16399 will be on Technet on 6 August.

Got the updates installed fine and I can confirmed that the build changed from 7600.16385 to 7600.16399.

[crainger]

This is why you wait for TechNet, now all j00 guys have you reinstall again because you jumped the gun.

[hell_of_doom227]

Originally Posted by crainger

This is why you wait for TechNet, now all j00 guys have you reinstall again because you jumped the gun.

No they don't have to.

[mailman2]

Originally Posted by crainger

This is why you wait for TechNet, now all j00 guys have you reinstall again because you jumped the gun.

I don't see the image file changing at all, they signed off on it, I dont think they can just recompile it, retag it and post it without everyone signing off on it again. MS will just put these files on Windows Update and you will have to grab them after an install. ...and why would you need to reinstall the OS? I installed the patches and I'm sitting at 7600.16399 already...

[crainger]

I decided you will have to reinstalled. Deal with it. kk

[mailman2]

http://www.mydigitallife.info/2009/0...n7_gdr-branch/

"If you think that Windows 7 RTM should be a stable release, and once Windows 7 been released to manufacturing at build 7600.16385, it’s ripe for prime time or product use, you may want to think again. Microsoft will release several update packages or hotfixes through Windows Update, which will upgrade and update Windows 7 RTM build string on BuildLab from 7600.win7_rtm.090713-1255 to 7600.win7_gdr.090722-1835 and BuildLabEx from 7600.16385.x86fre.win7_rtm.090713-1255"

I was right.

[K007]

thats a good thing right?

[crainger]

Originally Posted by mailman2

http://www.mydigitallife.info/2009/0...n7_gdr-branch/

"If you think that Windows 7 RTM should be a stable release, and once Windows 7 been released to manufacturing at build 7600.16385, it’s ripe for prime time or product use, you may want to think again. Microsoft will release several update packages or hotfixes through Windows Update, which will upgrade and update Windows 7 RTM build string on BuildLab from 7600.win7_rtm.090713-1255 to 7600.win7_gdr.090722-1835 and BuildLabEx from 7600.16385.x86fre.win7_rtm.090713-1255"

I was right.

http://www.dailypuppy.com/puppies/lu...ver_2009-08-02

"If you think mailman2 is right, think again. He's wrong about most things. It's k though. Everyone makes mistakes and can be updated to the latest build 7600.mail_man.090722-1835."

[mailman2]

Originally Posted by crainger

http://www.dailypuppy.com/puppies/lu...ver_2009-08-02

"If you think mailman2 is right, think again. He's wrong about most things. It's k though. Everyone makes mistakes and can be updated to the latest build 7600.mail_man.090722-1835."

I am right, as I usually am. Back to your hole.

[mailman2]

Originally Posted by K007

thats a good thing right?

Yes, that means there wont be another build released and that 7600.16385 is still the same version that will be out on technet and to customers. Others will get these patches through windows update - like I had stated earlier. They cant just rebake a new revision. They'd have to re-compile, retest and sign off on it. The RTM build can't just be changed now, but it can be patch through Windows update.