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.

Photo

Chkdsk Halts


  • Please log in to reply
1 reply to this topic

#1 Squeeshy

Squeeshy

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 28 May 2013 - 07:49 PM

Mod Edit:  Split from http://www.bleepingcomputer.com/forums/t/483046/checking-file-system-in-c/#entry3063149 Hamluis.

 

 

Hey guys. Sorry to bother you again but when I try to reset the Dirty Bit:

* chkdsk /f /r C: <--- (To manually run a full chkdsk operation on the specified drive)
* Y <--- (To accept having it run on the next boot)


This should take you through 5 stages of the scan and will unset the Dirty Bit.

 

my computerstops at step 3 again (even when it says 100 complete) causing me to have to manually reset my computer again.


Edited by hamluis, 28 May 2013 - 08:16 PM.
PM sent new OP - Hamluis.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:07:01 AM

Posted 29 May 2013 - 07:45 AM

Let's start with the correct command. Please run checkdisk as follows and see if the results are any better:

 

To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r  (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users