Main issue here is, we dont even know what MS considers as "showstopper". I guess bugs that can happen on every computer and result is data loss is showstopper anything else, i doubt it. But in all honesty... how often do average user even run chkdsk? For example my self i run it maybe 4-5 times in last 2 years and i actualy know why chkdsk is for, average user doesnt...
The only thing found correct in that whole thing was the fact that the RTM isn't even out yet for that error to be genuine. Anything else is simply being seen on preRTM build. "Attention Getter"! is all that amounts to in order to fill a blog page!
Vista RTM corrupted all iPods when they where inserted
The question now.. Does this issue reoccur when the auto-chkdsk is executed on all drives during its once a week job and will it be an issue after its executed?
Hes got a Watermark
A Failed Cracked Version i guess.
Wait I see some users getting this error.
Trying now,
edit : I get a Access Denied ( I ran the cmd using admin)
why is that ?
That bug, if indeed common, might be in the potentially "critical" or "important" category, but it's not a "showstopper." It certainly hasn't gotten MS to issue an RTM recall yet, which is what "showstopper" would imply.
I'd expect a patch, but not a stopped show and recall. That bug isn't going to impact most consumers and cause a disaster before they download patches.
Hi all
I couldn't reproduce the defect on W7 X-64 build 7137.
I'll be trying the RTM version as soon as it hits technet but I'm sure this isn't a problem in the 64 bit version.
The OP doesn't say if he / she was using X-86 or X-64, whether the processor was dual / quad core, whether RAID was involved, / SATA IDE etc etc.
Posts like that which leave out CRITICAL missing information when reporting alleged defects are usually fairly worthless and cause unnecessary concerns.
Cheers
jimbo
Can someone explain me why i cant run the command in the elavated cmd ?
I get Access Denied for every Partition, even C: ?
I can replicate the phenomenon - 500 GB non-RAID. The "issue" did not present until the free space, stage 5/5, was scanned. Waiting patiently for the crash. 102,nnn,nnn free clusters.
Quote
