So what exactly does this update do? Are there any reasons to NOT install this update? And if this is a real MS windows update then why isn't it coming through win7 windows update? Sorry if this is a stupid question. Thanks.
Well, at least the build string "7600.16399.x86fre.win7_gdr.090722-1835" seems to indicate that this update was compiled on the 22nd. Today is the 31st. That *should* mean that this update was compiled (hopefully) before MS found out about the Lenovo OEM key leak... So I would think that the update should be safe... I am still gonna wait a day or two though to make sure no one has any problems.
Not a stupid question... It is valid, and is the same thing I am wondering. I can see the argument that "Win7 is not officially released to the general population, so why would they put updates for it on windows update..." But that is just an assumption, and I like to be on the safe side of things... I will wait a bit and see what happens, just to be sure... The update's build string seems to indicate (as mentioned in my previous comment) that it was compiled on the 22nd, so hopefully this means that the update was compiled before MS found out about the Lenovo OEM key leak... I cant wait until OCT 22nd...then I can finally get my retail copy that I have been waiting so long for. It seems so far away...
Please read all posts in this thread, reasons have been given from many users. And the files have their digital signatures. Files with digital signatures are real.
It only let you install the updates one by one at a time. Since there's no official descriptions there's no way that u can tell which update is which. So far, i only notice that Windows6.1-KB675605-x86 is responsible for the change in Buildsting # .
Description: updates that were released in July, not included in the RTM code. 8 updates. After the upgrade until it turns out any () you will have a new version винды 6.1.7600 16399. 7600.16399. win7_gdr. 090722 x86FRE.-1835 or x64fre 16399 7600... 090722-1835 win7_gdr. The GDR update releases contain only fixes that are produced everywhere and are intended to address critical problems common Some files become version 7600.16400 16401, some 7600 123334 name="Microsoft-Windows-IEInstal" version="8.0.7600.20495" name="Microsoft-Windows-IEInstal" version="8.0.7600.16399" 123456 name="Microsoft-Windows-notepad" version="6.1.7600.20495" name="Microsoft-Windows-notepadwin" version="6.1.7600.20495" name="Microsoft-Windows-notepad" version="6.1.7600.16399" name="Microsoft-Windows-notepadwin" version="6.1.7600.16399" 674103 resources 675605 name="Microsoft-Windows-BootEnvironment-Core-BootManager-PCAT" version="6.1.7600.16399" name="Microsoft-Windows-OS-Kernel" version="6.1.7600.20495" name="Microsoft-Windows-BootEnvironment-Core-BootManager-PCAT" version="6.1.7600.20495" name="Microsoft-Windows-HAL" version="6.1.7600.16399" 972636 name="Microsoft-Windows-IE-IECompat" version="8.0.7600.16400" name="Microsoft-Windows-IE-IECompat" version="8.0.7600.20497" 973751 name="Microsoft-Windows-Setup-Navigation-Wizard-Framework" version="6.1.7600.20497" name="Microsoft-Windows-ImageBasedSetup-Media" version="6.1.7600.20497" 974039 name="WindowsSearchEngine" version="7.0.7600.16401" name="WindowsSearchEngine" version="7.0.7600.20497" 974138 name="Microsoft-Windows-GDI" version="6.1.7600.20498" name="Microsoft-Windows-Font-Embedding" version="6.1.7600.20498" name="Microsoft-Windows-Font-Embedding" version="6.1.7600.16402" name="Microsoft-Windows-GDI" version="6.1.7600.16402"
For people who think its fake can better skip this topic. Also dont forget it whas zukona who leaked the untouched iso files from microsoft. Why on earth he would fake the updates
Two of those I am suspicious of the numbers, especially since they reference ancient KB articles. 123456 indeed. Looks like a "test update" to me. Replace a file with another where nothing has changed but the version number.
I mean, how you know the key has been blacklisted in these updates?, and yes, I used the retail disc.
i just ran windows update and there were security updates there.dont know if they have anything to do with the leak,but made sure i didnt download them.
Apparently these are Microsoft manufacturer (OEM) updates that are issued to manufacturers to slipstream in to the RTM when making their branded DVDs, in order to fix minor bugs and glitches...*should* not affect activation. Still trying to find out what bugs/glitches that these fixes are supposed to take care of though...
i've no updates, had just running windows update how many update did you have? on what day where they released?
i installed the updates, still activated, so far, checked ms updates..nothing here either. ..just signed up - cheers all.