Run chkdsk standalone - XP Microsoft Computers & Internet

<b> <p>How to display Errors found and Repairs made by the CHKDSK Command<br /></b> The Chkdsk command is used to verify the integrity of a file system and is capable of correcting discrepancies in system data files. This command has been with us since DOS days and has been modified by Microsoft as required to meet the requirements of new operating and file systems as they evolved. <br /> If you execute the Chkdsk command from a command prompt without using the F (fix) switch, Chkdsk runs in the read-only mode. As Chkdsk runs its tests on the drive, it displays the results of these tests on the monitor screen and the test results remain there for you to read until you close the CMD box.<br /> However there are several drawbacks to running Chkdsk in the read-only mode, especially on an active NTFS volume (usually C:) <br /> 1. Chkdsk cannot make any corrections to the drive while in the read-only mode.<br /> 2. If Chkdsk encounters more than minor errors, it will not complete all of its tests.<br /> 3. If you are running Chkdsk in the read-only mode on the active partition, Chkdsk frequently reports disk corruption and other file system errors which do not exist. This happens when the system modifies the disk during the Chkdsk testing sequence.<br /> Considering the above, there is little to be gained by running Chkdsk in the read-only mode.<br /> You need to run Chkdsk/F at the command prompt to test the drive and to correct any errors found.. As soon as you make this entry the system responds with:<br /> "The type of file system is NTFS. Cannot lock current drive."<br /> "Chkdsk cannot run because the volume is in use by another process. Would you like this volume to be checked the next time the system restarts? (Y/N)."<br /> After you key in "Y" (followed by enter) and re-boot, the operating system starts to load and you are advised that a disk check has been scheduled and unless you cancel it, Chkdsk/F will start to run in a few seconds. (Actually the file being executed at this time is Autochk.exe). Chkdsk will run through its phases but it only displays the test results on the monitor screen for about 2 seconds before the screen clears and the operating system continues to load!<br /> If problems were found wiith the file system, you will not have time to read any messages regarding what they were or what actions were taken. If corrupted files and/or orphaned files/directories were detected you would most probably like to know about it and other problems found by Chkdsk. So how do you display the errors found and actions taken?<br /> The answer is that since running Chkdsk/F is a system event, the information is recorded in the System Event Log under application events. To read the log, Click on Start, Control Panel, Administrative Tools, Event Viewer and Application. Look for "Winlogon" in the Source column and double click on it. An Event Properties dialog box will open and display the log for you to read..<br /> Yavacotech.<br />

How to display Errors found and Repairs made by the CHKDSK Command
The Chkdsk command is used to verify the integrity of a file system and is capable of correcting discrepancies in system data files. This command has been with us since DOS days and has been modified by Microsoft as required to meet the requirements of new operating and file systems as they evolved.
If you execute the Chkdsk command from a command prompt without using the F (fix) switch, Chkdsk runs in the read-only mode. As Chkdsk runs its tests on the drive, it displays the results of these tests on the monitor screen and the test results remain there for you to read until you close the CMD box.
However there are several drawbacks to running Chkdsk in the read-only mode, especially on an active NTFS volume (usually C:)
1. Chkdsk cannot make any corrections to the drive while in the read-only mode.
2. If Chkdsk encounters more than minor errors, it will not complete all of its tests.
3. If you are running Chkdsk in the read-only mode on the active partition, Chkdsk frequently reports disk corruption and other file system errors which do not exist. This happens when the system modifies the disk during the Chkdsk testing sequence.
Considering the above, there is little to be gained by running Chkdsk in the read-only mode.
You need to run Chkdsk/F at the command prompt to test the drive and to correct any errors found.. As soon as you make this entry the system responds with:
"The type of file system is NTFS. Cannot lock current drive."
"Chkdsk cannot run because the volume is in use by another process. Would you like this volume to be checked the next time the system restarts? (Y/N)."
After you key in "Y" (followed by enter) and re-boot, the operating system starts to load and you are advised that a disk check has been scheduled and unless you cancel it, Chkdsk/F will start to run in a few seconds. (Actually the file being executed at this time is Autochk.exe). Chkdsk will run through its phases but it only displays the test results on the monitor screen for about 2 seconds before the screen clears and the operating system continues to load!
If problems were found wiith the file system, you will not have time to read any messages regarding what they were or what actions were taken. If corrupted files and/or orphaned files/directories were detected you would most probably like to know about it and other problems found by Chkdsk. So how do you display the errors found and actions taken?
The answer is that since running Chkdsk/F is a system event, the information is recorded in the System Event Log under application events. To read the log, Click on Start, Control Panel, Administrative Tools, Event Viewer and Application. Look for "Winlogon" in the Source column and double click on it. An Event Properties dialog box will open and display the log for you to read..
Yavacotech.

If your computer "locks up" or reboots itself, the problem is frequently lost or corrupted files on your hard drive. Most of the time the problem can be corrected by running chkdsk. However, one of the exceptions is when chkdsk reports that the hard drive has volume bitmap errors.<br /> To run chkdsk, click on Start, All Programs, Accessories and Command Prompt. This will open a "DOS Box" where you can enter DOS commands without the results scrolling off the screen before you can read them. Then key in chkdsk C: (assuming that drive C is the letter of the hard drive where your operating system files and applications programs are stored).<br /> Chkdsk will run in the read-only mode and report (but not repair) problems found on your hard drive. Chkdsk will then ask you to run chkdsk with the F switch to fix the file system. Make a mental note whether or not chkdsk reported any problems with the volume bitmap, then key-in chkdsk C: /F <br /> You will get a message that the drive will be checked (and repaired) on the next system restart.<br /> Enter exit to close the DOS box and the restart your system. Chkdsk will run automatically when your system restarts. If no volume bitmap errors were noted earlier, chkdsk should have repaired the problems with the hard drive. You can verify this by opening another DOS Box and running chkdsk without the /F. However, if bit-map errors were reported initially, chances are they will still be there as chkdsk cannot repair them.<br /> If you still have volume bitmap errors, you can either take your PC to a professional who may be able to repair the volume bitmap with specialized software, or you can back-up all of your data, format the hard drive, and reload the operating system and all applications.<br /> A frequent cause of volume bitmap errors is cloning (copying) a hard drive with more than one partition to another (usually larger) hard drive. The partitions should be sized proportionately on the target drive but sometimes the partition sizes are not reported correctly in the partition table and sometimes in the master boot record. <br /> Avoid cloning drives with multiple partitions, or if you do, immediately run chkdsk on the target drive to check for bit-map errors.