Right Sidebar

Pages

Monday, 29 October 2012

CHKDSK in Window 8 compared to Window 7

Chkdsk has been one of those great little tools built  in  about every version of Windows OS that Micosoft has released that help fix NTFS file system errors, corruption in file system and hard disk errors.


Because of that inherent design, it could take several hours for chkdsk to finish scanning a large drive with lots of files but there were some significant improvement to allow chkdsk to run faster but this is still depending on how large the files are.

In Windows 8 there is an improvent in the funstionality of Chkdsk. There has been an  additional features added to Windows 8 to catch and repair file system errors, so tthere may never be need to run chkdsk again.

In this article, I’ll tell you about the changes to chkdsk in Windows 8 and the additional file system health tools that have been added.

In Windows 8, a lot of errors will now be fixed automatically while running Windows that used to require running chkdsk after a reboot.

Check the screenshot of Window 8 compare to Window 7


Here is a screenshot of the list of parameters for chkdsk in Windows 7:
windows 7 chkdsk

Here are the list of parameters for chkdsk in Windows 8:
windows 8 chkdsk


From the above screenshot,  there are about 6 more new parameters after /b.

 The new options are:

- /scan - This will fix whatever can be fixed without restarting by running online scan
- /forceofflinefix - has to be used with /scan and is basically the same thing as running /spotfix
- /perf - The online scan will be  faster using this parameter.
- /spotfix - The new magical spot fixing feature of chkdsk that fixes errors in seconds rather than hours
- /offlinescanandfix – This run an offline scan and fix

When /spotfix or /offlinescanandfix is run on the current used volume, you’ll be asked to schedule the scan the next time the system restarts.
scanandfix


To see if a drive is scheduled for scan, open CMD and chkntfs c: or whatever the volume you want to check.
chkntfs

0 comments:

Post a Comment