Can't Run ChkDsk on C: - Vista32 Home Prem

[Margaret]

I'm running Diskeeper Pro 2007 on Vista32 Home Premium, and last time I
attempted to run a manual defrag job, I got a message that Diskeeper
couldn't even analyze the partition, because chkdsk needed to be run on
the partition.

I've tried entering the chkdsk cmd from an admin command prompt, and I
get the message that the chkdsk job will be scheduled to run after a
reboot. But chkdsk fails to run, just boots right into Windows. I've
also tried using the GUI (properties | tools) and scheduled a disk check
to run at the next reboot. And once again, the machine boots right to
the OS.

I've tried turning off UAC and setting the machine to run in safe mode,
but to no avail. (My account has admin priv.) Chkdsk won't run, but I
keep getting a message that it needs to be run.

Any ideas on this one?

Thx and Regards,

Margaret

 

[Richard Urban]

When asked if you wanted to run chkdsk at the next reboot, did you type in Y
and then press enter? Did you do this from an elevated command prompt (run
as administrator)? Try again. It should work - unless the hard drive is so
bad that chkdsk refuses to run.

Also, download the drive test utility from the hard drive manufacturer and
run those tests to see what they have to report.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

 

[Margaret]

When asked if you wanted to run chkdsk at the next reboot, did you type
in Y and then press enter? Did you do this from an elevated command
prompt (run as administrator)? Try again. It should work - unless the
hard drive is so bad that chkdsk refuses to run.

Also, download the drive test utility from the hard drive manufacturer
and run those tests to see what they have to report.

Yes, I entered Y to run chkdsk at the next reboot, and as I said in my
original post, I did this from an "admin," i.e., elevated command
prompt. Upon doing further searching of TechNet, I see that this
problem has been reported by a number of tablet PC users. (I'm using a
laptop.) And apparently their solution is to run chkdsk from the
recovery console off the Vista install disk.

http://tinyurl.com/2vg98s

http://tinyurl.com/2qkqe6

This is a new machine, and as a former computer professional, I'm
pretty meticulous about maintaining my machines. I could revert to a
prior disk image, but I'd like to avoid that ... and I'd like to learn
more about Vista in the process.

Anyway, thx for the tip on downloading the test utility from the drive
manufacturer. Slipped my mind this time.

Regards,

Margaret

 

[Richard Urban]

Remember, if a drive has a physical problem (it happens on new drives also)
recovering an image to that drive is not going to solve the condition. You
have to first verify that the drive is in tip-top condition.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

 

[Margaret]

Hi Margaret,

You can try booting into the "Advanced Boot Options" screen and run
Chkdsk from "Safe Mode with Command Prompt". See this tutorial for how.

http://www.vistax64.com/tutorials/88009-safe-mode.html

Here is a reference for Chkdsk.

http://www.vistax64.com/tutorials/67612-checkdisk.html

Shawn, thanks for the pointers to this forum, it'll definitely come in
handy. Unfortunately, I'd already tried running chkdsk from safe mode's
command prompt, and once again, the system just boots right into
Windows. I finally dragged out my install CD and ran the recovery
console, where I was able to run chkdsk and correct the disk errors. If
you check my previous reply to Richard, you'll see that I'm not alone
with this problem.

Anyway, I'm used to running Windows XP Pro SP2 and having more
management options available to me via MMC, so the management
limitations in Vista HP32 can be frustrating. Although I'll ultimately
be willing to spring for Vista Ultimate when I upgrade my main machine,
I figure HP32 is sufficient for a laptop. Now if the price would come
down..... ;-)

Thx and Regards,

Margaret

 

[AJ Babao]

try this while on dos mode type chkdsk/f