wouldn't go THAT far just from a build change -- just wait for some descriptions on these which should pop up soon. i'm sure some are real and legitimate, and maybe just 1 is taking the build number down -- but theres no way to know until someone actually posts on these updates as official like the last batch. anybody? any idea?
So, uninstalled all of them, one can't install either, said: Not for your computer. Waiting for description as you mentioned above, store them on my backup HDD.
Downloaded from rapidshare with 1.9m/sec, from MegaFTP 300k/sec. Rapidshare works! Maybe your online connection doesn't, or you live in the wrong part of the world. To TS, thanks!
Copy the following in to notepad, and save with the .cmd extension. Say, Updates.cmd PHP: @echo off Echo The window will close off or the command line return (depending on load method) once all updates are installed. Echo Installation of all updates may take considerable time. Please be patient! FOR /F "delims==" %%W in ('dir *.msu /od /b') do start /wait %%~nW.msu /quiet /norestart Run this file from in the folder where you have your .msu files. The same command can be used with office updates, except replace .msu with .exe, and replace the /quiet and /norestart with office update related commands. If you wish to see each update progress, remove the '/quiet' command. When a very large number of .msu's a present (think 100+ updates and hotfixes), running an automated script isn't a good idea, at least all at once. Under Vista and no doubt Windows 7, the more updates installed past a certain point the slower the updates get and some will be missed. To get around this, just separate the updates in to batches of say fifty, and restart after each batch is run. This really only applies if you get every update including hotfixes available. Hotfixes aren't freely available to the public, and it can get a bit tedious at times as some hotfixes can be superceded many times over. I also have to point out I got this command (with some modifications) off the internet a very long time ago, and now have no idea where I got it from. Just thought I'd say that before someone flames me!
ok so the x86 ones don't mess your version number up, but this KB123456 has got to be fake... damnit... now both of my x64 boxes are riddled with these 'updates'. should've taken my own advice. oh well, i'm just going to uninstall them and hope the version number fixes in the registry... ...actually no.. i'll wait 2 days until they're on windows update. hah.
did that alone fix your version number? and if so, are you x64 or x86? i tried uninstalling KB123456 and it just came back with the rest of the updates installed... so i just uninstalled them all now and am testing to see if the version fixes. i'll just get them online in 48 hours the safe way since i have legit keys.. edit -- yep, that fixed the problem. best we find which update is fake before installing these now, although x86 users aren't having the same build change issue.
Hmm, the first post in this thread describes, that the updates will be uploaded to the Windows Update Servers at the 22nd of October.... The thread title itself says, that the updates will be released saturday (22nd of August).....???? I am a little bit confused now? When do they come official????
I found that: KB123334 (Windows6.1-KB123334-x86.msu or Windows6.1-KB123334-x64.msu) Microsoft-Windows-IEInstal assembly that updates IEInstal.exe in ogramFiles ternet Explorer folder to version 8.0.7600.16399 or 8.0.7600.20495. KB123456 (Windows6.1-KB123456-x86.msu or Windows6.1-KB123456-x64.msu) Microsoft-Windows-notepad revision distribution that updates Notepad.exe to 6.1.7600.16399 or 6.1.7600.20495. KB674103 (Windows6.1-KB674103-x86.msu or Windows6.1-KB674103-x64.msu) A update that upgrades Win32k, User32, TCP/IP Binaries (tcpip.sys), SxS, NDIS (ndis.sys), GDI32 and Common Controls components to version 6.1.7600.14000 or 6.1.7600.20496. KB675605 (Windows6.1-KB675605-x86.msu or Windows6.1-KB675605-x64.msu) 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) IE compatibility update with new version of 6.1.7600.14000 or 6.1.7600.20497. KB973751 (Windows6.1-KB973751-x86.msu or Windows6.1-KB973751-x64.msu) Update to Windows 7 Image Based Setup-Media and Setup Navigation Wizard Framework to version 6.1.7600.20497. KB974039 (Windows6.1-KB974039-v2-x86.msu or Windows6.1-KB974039-v2-x64.msu) Update to Windows Search Engine to version 7.0.7600.16401 or 7.0.7600.20497. KB974138 (Windows6.1-KB974138-x86.msu or Windows6.1-KB974138-x64.msu) Update to Windows GI and Font Embedding components to version 6.1.7600.16402 or 6.1.7600.20498
KB675605 (Windows6.1-KB675605-x86.msu or Windows6.1-KB675605-x64.msu) 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. but Windows6.1-KB675605-v2-x86.msu BuildLabEx string is 7600.16397.x86fre.win7_gdr_staging.090720-1852 and other string seems be fine