2 Intern

 • 

18.8K Posts

December 11th, 2003 20:00

Chesty1,

If chkdsk /f has been scheduled it will attempt to run until you eventually allow it to. I have not heard of that program erasing data. If you lost data, something else must have been at work to cause the problem.

2 Intern

 • 

2.4K Posts

December 11th, 2003 22:00

If you didn't schedule it to run (it only runs on re-start) I'd do an online security scan at norton.com

2 Intern

 • 

2.4K Posts

December 11th, 2003 22:00

I should have mentioned this earlier: When you get to the anti-virus scan page EndTask *your* AV program. They may conflict.

35 Posts

December 11th, 2003 22:00

I will give it a try . Thanks

35 Posts

December 11th, 2003 23:00

I just scanned my system and I have no problems with viruses or trojans. I dont know what could be causing this automatic disk check to function like this.

35 Posts

December 12th, 2003 00:00

Thanks for your help maxd. I will give it a try.

2 Intern

 • 

2.4K Posts

December 12th, 2003 00:00

All I could find. If you're familiar with the Registry, backing up, etc. delete the values but as Denny said chkdsk /f normally wouldn't cause a loss of data. Run the command sfc /scannow (note space)first if you decide to let it run.

http://www.google.ca/search?q=cache:9F68oCvboXoJ:windows.about.com/library/tips/bltip018.htm+prevent+chkdsk&hl=en&ie=UTF-8

2 Intern

 • 

2K Posts

December 12th, 2003 01:00

When Windows is not shutdown correctly it will perform an AutoCheck using CHKDSK on the next restart. This setting controls the time delay before running Autochk or whether it is run at all.
 
Open your registry and find the key below.
 
Create a new DWORD value, or modify the existing value called 'AutoChkTimeOut' using the settings below.
 
Exit your registry, you may need to restart or log out of Windows for the change to take effect.
 
Settings:
System Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
Name: AutoChkTimeOut
Type: REG_DWORD (DWORD Value)
Value: Time in Seconds or 0 to disable (default = 10)
-----------------------
If you don't want to use Regedit , you can use  CHKNTFS  from Command Prompt window;

E:\>chkntfs  /?
Displays or modifies the checking of disk at boot time.
 
CHKNTFS volume [...]
CHKNTFS /D
CHKNTFS /T[:time]
CHKNTFS /X volume [...]
CHKNTFS /C volume [...]
 
  volume         Specifies the drive letter (followed by a colon),
                 mount point, or volume name.
  /D             Restores the machine to the default behavior; all drives are
                 checked at boot time and chkdsk is run on those that are
                 dirty.
  /T:time        Changes the AUTOCHK initiation countdown time to the
                 specified amount of time in seconds.  If time is not
                 specified, displays the current setting.
  /X             Excludes a drive from the default boot-time check.  Excluded
                 drives are not accumulated between command invocations.
  /C             Schedules a drive to be checked at boot time; chkdsk will run
                 if the drive is dirty.
 
If no switches are specified, CHKNTFS will display if the specified drive is
dirty or scheduled to be checked on next reboot.
------------------
You can use   chkntfs   /t:0    to disable CHKDSK at boot.
You can also use  chkntfs  C:   to display if Drive is marked dirty.

 

35 Posts

December 12th, 2003 01:00

Ok I fixed he problem. I went to Microsofts website and found the info I needed. Here is a link so you guys can check it out for yourselves. Windows has a utility built into it called CHKNTFS.EXE This is what you use to disable automatic chkdsk.       http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q160/9/63.asp&NoWebContent=1

 Thank you guys for the help you provided, it helped to steer me in the right direction

2 Intern

 • 

2.5K Posts

December 12th, 2003 01:00

You really don't want to stop autochk.  If the bad shutdown didn't corrupt the file system then chkfsk /f will do nothing, if the bad shutdown did corrupt the file system, then chkdsk /f is the only way you have to fix it.  I am not really clear about "lost clusters" on NTFS, but on FAT file systems chkdsk /f converts lost clusters to files, which creates new incomplese files and truncates the files with the missing clusters, effectively destorying files.  However the files werre bad before chkdsk /f got into the act.  Same for cross linked files.
No Events found!

Top