Windows File System Errors: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Open a command prompt | Open a command prompt | ||
Click Start → Click Run → type <tt>CMD</tt> → Click OK | Click Start → Click Run → type <tt>'''CMD'''</tt> → Click OK | ||
At the command prompt, type the following: | At the command prompt, type the following: | ||
| Line 17: | Line 17: | ||
(Where X is the drive letter that you would like to scan, most commonly C:) | (Where X is the drive letter that you would like to scan, most commonly C:) | ||
If there are files in use that cannot be scanned, such as core Windows system files, you will be prompted to run the Check Disk at the next reboot. Answer <tt>Y</tt> to this. | If there are files in use that cannot be scanned, such as core Windows system files, you will be prompted to run the Check Disk at the next reboot. Answer <tt>'''Y'''</tt> to this. | ||
Revision as of 01:58, 15 January 2009
Created: 15 January 2009. Last Reviewed: 15 January 2009
Disk Corruption
One of the main reasons for Database corruption in Enabler is the underlying Hard Disk and/or Windows File System becoming corrupt. This can happen for numerous reasons including physical hardware failure or virus activity.
Often, problems can be resolved by running a Check Disk command over the drive that Enabler is installed on as follows:
Open a command prompt
Click Start → Click Run → type CMD → Click OK
At the command prompt, type the following:
C:\> CHKDSK X: /F
(Where X is the drive letter that you would like to scan, most commonly C:)
If there are files in use that cannot be scanned, such as core Windows system files, you will be prompted to run the Check Disk at the next reboot. Answer Y to this.
When the machine is rebooted, the Check Disk will scan for and repair any hardware or file system issues.
