CRITICAL SHOW STOPPER BUG in Windows 7 RTM Build 7600.16385 and Patched 7600.16399
#41
Posted 05 August 2009 - 07:11 PM
I say that just a patch through Windows Update is more than enough, is not a big deal as long you don't use that command I guess
#42
Posted 06 August 2009 - 02:45 AM
OEMs can patch their preload images = problem solved. The official release date is October 22nd so there's a lot of time to release patches and whatnot.
#43
Posted 06 August 2009 - 02:57 AM
This has been confirmed not a bug or showstopper !
http://www.thehotfix.net/forums/index.php?/topic/25430-windows-7-rtm-bug-is-not-a-showstopper- not-a-critical-bug/page__pid__174812__st__0&#entry174812
#46
Posted 06 August 2009 - 04:33 PM
Megatron, on 06 August 2009 - 02:57 AM, said:
This has been confirmed not a bug or showstopper !
http://www.thehotfix.net/forums/index.php?/topic/25430-windows-7-rtm-bug-is-not-a-showstopper- not-a-critical-bug/page__pid__174812__st__0&#entry174812
Honestly if this is a chipset driver issue I highly doubt we would have to install chipset drivers when booting from the DVD just to run a stupid "chkdsk" command. I have found the leak present on 4 computers with the "/r" and "/f" commands, and when booting from the DVD.
#47
Posted 06 August 2009 - 11:10 PM
From the Microsoft Connect forums for Office 2010 in regards to the "chkdsk" bug.
Quote
Try reproducing this bug before complaining. I haven't been able to
and neither has Microsoft. Keep in mind Neowin gets news very quickly
but that comes at a downside. News postings can be modified and
rectified as more information comes out. The "more information that
came out" indicates that this bug is not a showstopper. It's is not
critical because first it doesn't happen very often, even MIcrosoft
cannot reproduce the bug, and second, no data is being corrupted or
lost. If you need to chkdsk, do it from the recovery CD, not from
windows. I mean it'll be so much easier doing from the recovery
environment because you don't have to dismount the drive you want to
check. It's a non-issue that isn't urgent. Let me ask you, have you
tried reproducing this bug? You'll help the windows engineering team
more by reproducing it and providing instructions on how to reproduce
it rather than ranting about it on here. I'm sure they already know
about it.
-Geo
and neither has Microsoft. Keep in mind Neowin gets news very quickly
but that comes at a downside. News postings can be modified and
rectified as more information comes out. The "more information that
came out" indicates that this bug is not a showstopper. It's is not
critical because first it doesn't happen very often, even MIcrosoft
cannot reproduce the bug, and second, no data is being corrupted or
lost. If you need to chkdsk, do it from the recovery CD, not from
windows. I mean it'll be so much easier doing from the recovery
environment because you don't have to dismount the drive you want to
check. It's a non-issue that isn't urgent. Let me ask you, have you
tried reproducing this bug? You'll help the windows engineering team
more by reproducing it and providing instructions on how to reproduce
it rather than ranting about it on here. I'm sure they already know
about it.
-Geo
#49
Posted 07 August 2009 - 01:44 AM
Why did I just know some thing like this would happen?
It is just Microsoft's luck.
And their luck was mine as well, as I won the tech department pool with the closest time to an announcement. Though to tell you the truth, I would have preferred that NO ONE would have won this one.
It is just Microsoft's luck.
And their luck was mine as well, as I won the tech department pool with the closest time to an announcement. Though to tell you the truth, I would have preferred that NO ONE would have won this one.

Help
Sign In »
Register Now!













