I downloaded an AOL (Security?) update yesterday. Now everytime I boot up
Check Disk runs a check on my external H: drive which comes out OK and waste
time. How do I stop this nuisance?

To stop the scan, logon with the Administrator or any administrative account
and go to Start\Run\and type; "regedit" (no quotes) and hit Enter... next
browse to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\
double click on the REG_MULTI_SZ value named "BootExecute" and type:
"chkntfs /x h:" (no quotes), click OK and exit the Registry. The nuisance
will be gone on the next boot.



------------------------------
"PSRumbagh" <(E-Mail Removed)> escribió en el mensaje
news:1D7A50B0-A915-438D-9EEC-(E-Mail Removed)...
>I downloaded an AOL (Security?) update yesterday. Now everytime I boot up
> Check Disk runs a check on my external H: drive which comes out OK and
> waste
> time. How do I stop this nuisance?

Open a Command Prompt and issue the following command:

chkntfs /d

John

PSRumbagh wrote:

> I downloaded an AOL (Security?) update yesterday. Now everytime I boot up
> Check Disk runs a check on my external H: drive which comes out OK and waste
> time. How do I stop this nuisance?

Running "chkntfs h:" produces message that h: is NTFS file system and that it
is dirty. What does "dirty" mean? A mix of FAT, FAT32, NTFS files or
something is physically wrong with the h: drive? Running "chkdsk h:" shows
no problems.

"John John (MVP)" wrote:

> Open a Command Prompt and issue the following command:
>
> chkntfs /d
>
> John
>
> PSRumbagh wrote:
>
> > I downloaded an AOL (Security?) update yesterday. Now everytime I boot up
> > Check Disk runs a check on my external H: drive which comes out OK and waste
> > time. How do I stop this nuisance?
>

The "Dirty Bit" is set by the operating system when changes are made to
the disk but not yet committed, once the change is committed to the disk
(written to the disk) the dirty bit is removed. If there is a file
system error or disk corruption or if something fails before the changes
are committed to the disk (like a power failure) the dirty bit remains
set and on reboot Windows automatically checks the disk for errors, upon
successful completion of the disk check the dirty bit is removed. If
the dirty bit was set by the operating system it cannot be removed
manually by the user.

Try running a chkdsk on the disk while Windows is up and running. Make
sure that there are no open handles on the disk, make sure that there
are no open files on the disk or that no applications have a handle on
the disk, for example make sure that you are not exploring the volume
with Explorer.exe. At the Command Prompt issue chkdsk /f and let the
command run its course.

John

PSRumbagh wrote:

> Running "chkntfs h:" produces message that h: is NTFS file system and that it
> is dirty. What does "dirty" mean? A mix of FAT, FAT32, NTFS files or
> something is physically wrong with the h: drive? Running "chkdsk h:" shows
> no problems.
>
> "John John (MVP)" wrote:
>
>
>>Open a Command Prompt and issue the following command:
>>
>>chkntfs /d
>>
>>John
>>
>>PSRumbagh wrote:
>>
>>
>>>I downloaded an AOL (Security?) update yesterday. Now everytime I boot up
>>>Check Disk runs a check on my external H: drive which comes out OK and waste
>>>time. How do I stop this nuisance?
>>