48 replies to this topic

[Jordan M. Jacob]

A critical show stopper bug has been found in the Final Windows 7 RTM 7600.16385 and in the updated 7600.16399 builds! Thanks to mikerolsonw7c of Windows7Center for informing us of the critical bug. The issue is related to the "chkdsk /r" command on a drive other than the system drive. For example if you have drive C: and drive D: with C: being Windows 7. If you open "cmd" and run "chkdsk /r D:" on "Stage 4" of chkdsk it will have a very critical memory leak and max out the system memory then BSOD due to lack of memory available. This issue is present on non-Patched 7600.16385 and Patched 7600.16399 RTM builds. This is a very critical bug that Microsoft should have caught before sending 7600.16385 to OEMs. Sadly, now Microsoft will have to fix this and then re-distribute RTM code to OEMs or patch it. I would not doubt myself when Microsoft gets word of this Show Stopper bug if the TechNet/MSDN releases on Thursday the 6th get pushed back to re-implement new code into the RTM build.

[Jordan M. Jacob]

UPDATED ARTICLE!

A critical show stopper bug has been found in the Final Windows 7 RTM 7600.16385 and in the updated 7600.16399 builds on both 32-bit (x86) and 64-bit (x64) installs! Thanks to mikerolsonw7c of Windows7Center for informing us of the critical bug. The issue is related to the "chkdsk /r" command on a NTFS drive other than the system drive (Issue not present for FAT32 Drives). For example if you have drive C: and drive D: with C: being Windows 7. If you open "cmd" and run "chkdsk /r D:" on "Stage 4" of chkdsk it will have a very critical memory leak and max out the system memory then BSOD due to lack of memory available. This issue is present on non-Patched 7600.16385 and Patched 7600.16399 RTM builds. This is a very critical bug that Microsoft should have caught before sending 7600.16385 to OEMs. Sadly, now Microsoft will have to fix this and then re-distribute RTM code to OEMs or patch it. I would not doubt myself when Microsoft gets word of this Show Stopper bug if the TechNet/MSDN releases on Thursday the 6th get pushed back to re-implement new code into the RTM build.

[#13 D. Limes]

Nice find!

Off-Topic

Where did you get those hard drive and CPU/RAM Gadgets?

[Jordan M. Jacob]

Nice find!

Off-Topic

Where did you get those hard drive and CPU/RAM Gadgets?

Off-Topic

Search for MultiMeter and Hard Disk Drive Meter they are made by the same guy.

Edited by Jordan M. Jacob, 04 August 2009 - 03:17 AM.

[Diablofan]

And I was hoping that nothing like this would show up. Damn, I guess were waiting...again.

[redrumy3]

they wont release a new rtm iso they will have hotfixes via windows update im guessing thats what those updates that were leaked by the person who leaked rtm

since those hotfixes he leaked did change build number

[Jordan M. Jacob]

they wont release a new rtm iso they will have hotfixes via windows update im guessing thats what those updates that were leaked by the person who leaked rtm

since those hotfixes he leaked did change build number

If you read my post exactly as is redrumy3, this issue has been confirmed by other users running on the Hotfixed 7600.16399 Build and is still present.

[redrumy3]

If you read my post exactly as is redrumy3, this issue has been confirmed by other users running on the Hotfixed 7600.16399 Build and is still present.

yeah i messed up and didnt see that one part :X lol sorry

[Franpa]

7600.16399

Where is this? can't disable bold... I already have 8 hotfix/updates applied.

Edited by Franpa, 04 August 2009 - 04:19 AM.

[Witt3439]

If I'm not mistaken Franpa, the update KB972636 (included in the update package) is the one that installs the GDR update and changes the build number.

Edited by Witt3439, 04 August 2009 - 05:19 AM.

[Scott]

any ome running the rc or beta to see if this is present in older builds
just wanna kow how longs its been in it
that one program that i might have to run once a year

[Franpa]

I have KB972636 installed and "slmgr -dlv" still says 16385. Can't figure out where to look in the registry, but I'm pretty sure the only change to the Windows version # the 8 updates did was change it from RTM to GDR.

Edited by Franpa, 04 August 2009 - 05:41 AM.

[#13 D. Limes]

HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrent Version

displays 16399 GDR in there

7600.16399.amd64fre.win7_gdr.090722-1835 in BuildEx

Edited by #13 D. Limes, 04 August 2009 - 05:42 AM.

[Franpa]

7600.16399.amd64fre.win7_gdr.090722-1835

Ok then, maybe it did change

[#13 D. Limes]

And the updates gave me a bit more of a performance boost I installed like all 7 updates or something like that in a zip package on here somewhere

[Jordan M. Jacob]

7600.16399

Where is this? can't disable bold... I already have 8 hotfix/updates applied.

If you check in your regedit under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version" you will see the 7600.16399 build string.

[shatrughan]

great find

what will microsoft do now

will it re issue a new RTM build to all OEM or
will it patch the holes with a hot fix

[Franpa]

I already mentioned it did change...

[#13 D. Limes]

It may be a bit of a hassle to recall all those OEMs but it's a huge bug that needs to be implemented into the "official" RTM. They need to fix that, and should have caught it before the release. A hotfix is nice, but it needs to be integrated.

[Apocalypse]

so does it mean Microsoft will re-distribute RTM build for TechNET/MSDN on Aug 6th?I know RTM build still is still unchange (16385) but hope we can get the clean build without any critical bugs in it