chkdsk in start-up repair versus in Windows Command Prompt

I recently had a laptop crash (Windows 7 Home Premium x64) during a windows update, had to go through lengthy process which ultimately resulted in need to do system recovery from protected partition on an Acer laptop.

One of the interim steps i had tried was to run chkdsk from a command prompt after having been able to reach "repair your computer". I originally had to create a repair disk to get there, but eventually was able to access it from the computer's hard drive.

Run from the command prompt under start-up repair, the chkdsk was PAINFULLY slow, running for more than 12 hours and without getting through the first step. Granted, it did seem to be trying to fix errors.

I came across something about it being slow based on allocation of system resources in the start-up repair. I wanted to see if anyone could elaborate on that. Now that I've gotten the system recovery working, I'd like to run chkdsk again, and I don't want that to take days. My thought is to run it from an elevated command prompt (run as administrator). I'm also thinking that the /x switch will be needed to run this on the c:drive.

Any thoughts on this are appreciated!

I just ran it from winpe on all my drives - it was fairly quick.

Might be something to do with the fact I have 512mb scratch space - the default is only 32 mb in winre.

Ztruker said:

You can't run chkdsk in repair mode (/f or /r) against the boot drive. You will have to allow it to run on the next boot.

>chkdsk /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

I've never seen any difference in performance when run as above or from the Recovery console Command Prompt. DO you have a link to the article that talks abut the system resource allocation problem? I'd like to read it.

On your question, I'm pretty sure that I saw the resource allocation mentioned somewhere on this forum, but I haven't tried to find it again.

I ran sfc /scannow yesterday, and it found and corrected errors, but when i boot up, I still get an autock error, about recently installed software.

I tried to run chkdsk on the boot drive from an elevated command prompt this morning, thinking I could force a dismount with the /x switch, but that apparently won't work on the boot drive. I was thinking that if it would dismount, with Windows already loaded, that I could just reboot the PC when it was done.

When i try to set chkdsk to run at start-up, I believe that autock is interfering, so I have to fix that first, I guess.

Hey I had to get in on this because I am also suffering a lot of windows errors and I think the cause of it is an MBR virus. I cannot run chkdsk /r from elevated command disk cannot be locked etc. No scan I have used has found it. Afraid of low level format because I am using a sata drive and dont want to brick it. I have reinstalled windows7 and nothing changed. In fact it got worse. I will offer what ever help I can.

WIn x64
4 gb ddr3
x4 core AMD Phenom II
Nividia GE-Force 9800 GT plus
wd sata black? sixg.s

Try running Startup Repair a few times which may also automate SFC but will test many other things as well.

Here are other steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums