My friends computer gave an unable to write to disk error while Steam was updating a game (not sure exactly what the error was). She said she had also had issues with the computer hanging lately. She lives on a different coast now, so I can't help her hands on, but I walked her through scheduling a chkdsk task, figuring that would be a good place to start. That was Saturday night and it's been stuck at 22% since (over 24 hours now).
I've heard of chkdsk taking over 24 hours before, but what is the practical limit on how long chkdsk could take to complete? The consensus is that you should never do a hard restart to interrupt chkdsk. Will chkdsk always complete and the boot if given enough time? The machine had no problems booting before. Hard disk activity light is still flashing.
I've heard of chkdsk taking over 24 hours before, but what is the practical limit on how long chkdsk could take to complete? The consensus is that you should never do a hard restart to interrupt chkdsk. Will chkdsk always complete and the boot if given enough time? The machine had no problems booting before. Hard disk activity light is still flashing.
