Build from Technet is newer !

[pmc]

It acepted upgrade from last version we had and the oem patch (Windows6.1-KB972636-x86 ) reported as already instaled.

Rgds

Mine continue to report as 7600.16385 (slmgr.vbs -dlv)

Old version= 7600.16385.090713-1255_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD
Newew Version= en_windows_7_ultimate_x86_dvd_x15-65921

both iso have same hash


Running "System Information", it reported this :

Hardware Abstraction Layer Version = "6.1.7600.16399"

Anyone know anything about this ?


Sorry "The Blessed One" english is not my native language,i dont understood/and what you mean

A GDR update that upgrades Windows 7 OS Kernel, HAL (Hardware Abstraction Layer), BootEnvironment Core BootManagerPCAT components to 6.1.7600.16399 or 6.1.7600.20495. This update package is responsible for changing the BuildLabEx string to 7600.16399.x86fre.win7_gdr.090722-1835 or 7600.16399.x64fre.win7_gdr.090722-1835 and changing win7_rtm in the BuildLab string to win7_gdr.
* KB972636 (Windows6.1-KB972636-x86.msu or Windows6.1-KB972636-x64.msu)

 

[Dinesh]

after downloading 1 update(i dont remember the name) and the build number changed from 7600.16385 to 7600.16399. Nothing else is that i have noticed with the newest updates.

 

[Crypto]

Newew Version= en_windows_7_ultimate_x86_dvd_x15-65921
65921 is in the name of the Download I think, and i guess it doesnt have any connection with the build number or anything. Check the other Download, it has 8592x something.

Edit : yup its the file name
Win 7 Ultimate x64- File Name: en_windows_7_ultimate_x64_dvd_x15-65922.iso
Win 7 Ultimate x86- File Name: en_windows_7_ultimate_x64_dvd_x15-65921.iso

So its the same ISO image.
On the other hand adding a newer build means Newer files are there, and that means the Hash Must Change. So you can think about it either way.

 

[The Blessed One]

@ pmc

You said you upgraded from a version which already had the new KB972636 installed? Then of course the TechNet or any other will report the new build number. How can you not realise this? :huh:

 

[Crypto]

@ pmc

You said you upgraded from a version which already had the new KB972636 installed? Then of course the TechNet or any other will report the new build number. How can you not realise this? :huh:

I think that he has misunderstood the build number with the File name

 

[Snufffed]

I have KB972636 installed as of Aug 8 2009, it did not change my Build number. so why would it change his Build Number? That does not make since to me.

Update for Internet Explorer 8 Compatibility View List for Windows 7 (KB972636)
Installation date: ‎8/‎7/‎2009 11:19 AM
Installation status: Successful
Update type: Recommended
This Compatibility View List update helps make Web sites that are designed for older browsers look better in Internet Explorer 8. When users install Internet Explorer 8, they will be given a choice about opting-in to a list of sites that should be displayed in Compatibility View. After you install this item, you may have to restart Internet Explorer.
More information:
Description of the Compatibility View list in Windows Internet Explorer 8
Help and Support:
A Compatibility View list update is available for Windows Internet Explorer 8: July 21, 2009

 

[Crypto]

I have KB972636 installed as of Aug 8 2009, it did not change my Build number. so why would it change his Build Number? That does not make since to me.

Hmm I would like to know that too,

@pmc > please dont edit the first post always, Its a bit hard to find new updates that uv posted. hope u get me

Did you use the Updates from a leaked or Any other source or by Windows updates ?

 

[poin2]

The handful of (leaked) updates that are out there will elevate the build to 16399.

I believe only one of them has officially made it to Windows Update so far. KB972636 installs an IE compatibility list update. I don't believe it's the one that updates the build number.

There is not a "newer" build via Technet. It remains the exact same thing MS declared RTM, and has been unaltered since.

Last I checked, KB675605 is the supposed GDR update that changes the kernel, and it's not yet officially out, nor was it incorporated into the (unaltered) Technet release.

 

[pmc]

Hi again i had 7600.16385.090713-1255_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD installed + the oem patches.

I upgraded to en_windows_7_ultimate_x86_dvd_x15-65921 ( i was surprised here ) and after installed again the oem patches.

The "Windows6.1-KB972636-x86" was the only one that didnt installed as it was already there.

I dont recall that update coming from windosupdate.

 

[Crypto]

Hi again i had 7600.16385.090713-1255_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD installed + the oem patches.

I upgraded to en_windows_7_ultimate_x86_dvd_x15-65921 ( i was surprised here ) and after installed again the oem patches.

The "Windows6.1-KB972636-x86" was the only one that didnt installed as it was already there.

I dont recall that update coming from windosupdate.

Can you pls. Explain these,
1. Did you get the Later Download from Technet ?
2. and What do you mean by OEM Patches ? (If its the Crack dont explain about it, just say yes)

 

[johngalt]

TechNet *purchased subscription* - legitimate license - here are my results using the same method as PMC listed:



PMC, please do not discuss any OEM patches that are illegal, as mentioned above - doing so will earn an infraction and possibly more severe penalties.

if these patches are legitimate M$ issued patches that you acquired through legitimate means (being an MVP, TechNet with your own legitimate subscription, MSDN with your own legitimate subscription) then you may continue to discuss them. If not, please notify me by PM so I can close this thread.

 

[3r1c]

PMC, please do not discuss any OEM patches that are illegal, as mentioned above - doing so will earn an infraction and possibly more severe penalties.

I believe he was referring to the zip file with some windows updates that are supposedly meant for testing by OEMs, not the OEM activation cracks.

Those windows updates are bogus/fake/trojans, the KB id's don't exist at microsoft.com which proves they are fake. KB1234567 should be obvious that its fake.

Reformat and reinstall your system and dont install any "updates" that dont come from the official windows update service.

Seriously, people should know better nowadays not to download some zip file with exe files and overwrite windows files with them :shock:

 

[EarlZ]

Better wait for those updates to hit Windows Updates instead of installing leaked files.

 

[SoLoR]

Those windows updates are bogus/fake/trojans, the KB id's don't exist at microsoft.com which proves they are fake. KB1234567 should be obvious that its fake.

how can update SIGNED by MS be fake/trojan whatever? all that updates are REAL updates. Worst they can be is some test updates,they are certanly not fake or include viruses. Reason why there is no KB article is, because they are not released yet...

 

[pmc]

Yes i was refering to that and they arent fakes or trojans.
But now on one of the pcs i have a strange problem with usb not working and i remember another user reporting too.
I loaded winxp (multiboot for diagnostic purpose) and usb working as normal) so it means its related to those patch.

Funny thing i had earlier version installed + patches and no problems, now i have technet version + patches and usb are broken.

 

[Dinesh]

how can update SIGNED by MS be fake/trojan whatever? all that updates are REAL updates. Worst they can be is some test updates,they are certanly not fake or include viruses. Reason why there is no KB article is, because they are not released yet...

+1.

 

[Crypto]

guys, so what is the latest build finally . I'm really confused. (post removed)

Hello Shreen, Please Dont post links to other sites unless relevent.
The Latest Official Build is 6.1 Build 7600 - 7600.16385.090713-1255