Re: Autocheck disk on restart - endless loop

The chkntfs command is for the next boot. After that, the standard (normal) rules apply. If the scanner is attached to the problem pc, you may want to consider getting the latest driver from the manufacturer.

--
Maurice N
MS-MVP Windows (Shell / User), Aumha.net VSOP , DTS-L
-----

"hlago" <hlago@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:794BD71B-2D66-4D09-92B5-4A052632FFCF@xxxxxxxxxxxxxxxx
Will this command solve the probelm just for the next boot or for all boots
until I cancel it out? What if the disk legitimately needs to be checked on
subsequent boots? I do have a scanner as part of a multi-function printer on
my network.

"Maurice N ~ MVP" wrote:

Use CHKNTFS

chkntfs /x c:

That would exclude checking of C drive on the next boot.
The /x command-line option is not accumulative. If you type it more than
once, the most recent entry overrides the previous entry. To exclude
multiple volumes, list them all in one command. For example, to exclude
both the E: and F: volumes, type:

chkntfs /x e: f:

If you have a scanner on your system, some "may" cause a conflict, which then leads to chkdsk problem.

--
Maurice N
MS-MVP Windows (Shell / User), Aumha.net VSOP , DTS-L
-----

"hlago" <hlago@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3BE7861D-3D19-4300-87D1-464BDF498066@xxxxxxxxxxxxxxxx
My computer will check and re-check the disk endlessly on startup and restart
until I cancel out of it. Chkdsk /f and chkdsk /p or /r from the recovery
console will not solve the problem even though they run through to completion
and appear to fix all errors. Event viewer for autocheck disk (Winlogon
1001) indicates that the disk has been cleaned of errors but when I run
fsutil dirty query C: the response I get is Volume C: is dirty. I have
checked the registry settings under session manager\boot execute and they are
correct as per Article ID 831426. Neither Chkdsk nor Autochk are listed
under scheduled tasks so that does not seem to be the problem. The computer
seems to be running fine except for this annoying problem. I cannot defrag
the disk because I get the message that chkdsk /f is scheduled to run on
Volume C:. Any ideas on how to solve this problem will be appreciated.
Thank you.

.

Relevant Pages

  • Re: good tool to scan without installing?
    ... NTFSDOS' memory model was incompatible with the ... McAfee command line scanner which is a DOS/Win32 utility. ... | non-booting machine, scan BOTH NTFS and FAT partitions from a boot cd. ...
    (microsoft.public.security.virus)
  • Re: One Ultra320 drive and SCSI scanner - Controller?
    ... before a new command has to be issued at which time the faster device get's ... It's devices that keep the bus longer than necessary without ... the scanner have to place his deadtimes somewhere if it cannot disconnect. ... only two mandatory commands for scanners: SET WINDOW and READ. ...
    (comp.periphs.scsi)
  • Re: XP wont boot from a volume formated in WinPE 2 (Vista)
    ... Today I included the format command in my Diskpart script. ... missing Vista boot files. ... when I copy the Vista boot files but this is no solution as Windows ... I didn't use Diskpart to format, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Format Hard Disk
    ... So it's like that - the 2 files reside only in the boot partition.. ... As you suggested, I opened Command ... No problem....I don't intend to use the programs existing in Win2K. ... - Buy a 100 GByte disk and install it as a slave drive. ...
    (microsoft.public.win2000.general)
  • Re: How do I remove XP Pro setup at boot?
    ... Reggie D. wrote: ... I can see FDISK.EXE but not a sys command file. ... I made the boot disk ages ago, and the FDISK.EXE and I think the sys utilities are also there. ...
    (microsoft.public.windowsxp.general)