Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


When should the following tools be used?

  • Please log in to reply
2 replies to this topic

#1 wishmakingfairy


  • Members
  • 212 posts
  • Gender:Female
  • Local time:05:47 PM

Posted 11 November 2014 - 02:07 PM

I use these common tools and for me, its a hit or miss when they work so... my question is, when and when should I not use....?


1. system file checker


2. chkdsk /f or /r


And... am I missing other built in system tools that I should be using?

Edited by wishmakingfairy, 11 November 2014 - 02:10 PM.

Using ubuntu and sharing how to as well as collecting how to scripts for common programs. Feel free to ask or share ^-^

BC AdBot (Login to Remove)


#2 Allan


  • BC Advisor
  • 8,629 posts
  • Gender:Male
  • Location:New Jersey
  • Local time:06:47 PM

Posted 11 November 2014 - 03:51 PM

1) Use sfc /scannow if you believe one or more system files are missing or corrupt.


2) Use chkdsk /r to check the your hard drive for errors and repair them. There is no need to ever use the /f switch (chkdsk /r assumes the /f switch).

#3 hamluis



  • Moderator
  • 56,281 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:47 PM

Posted 16 November 2014 - 08:45 AM

What Allan said :).


I use both routinely, but on an unscheduled "whenever I feel it needs to be done" basis.  I consider each a part of basic system maintenance, much more important than updating drivers and all the other small fish that some users obsess over.


In general...if the 3-step chkdsk runs on its own prior to boot...that should be followed by running chkdsk /r on whatever partition prompted the 3-step chkdsk at boot (it's not always the system partition that needs chkdsk /r).  Every partition (other than those on an SSD) needs chkdsk /r, followed by an occasional defrag, IMO.


A user can take a look at the errors reflected in Event Viewer and make a guess as to what might be wrong.  Windows will usually start compiling various errors when system files are damaged or missing...a good start to troubleshooting errors with no obvious clues...would be to run chkdsk /r and follow with sfc /scannow, eliminating obvious possible causes before moving on to other guesses.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users