New
#1
Win Pre-Environment (boot) CHKDSK -- can it be aborted safely?
Back story is that I'd run into a problem when trying to clone my aging HDD to my new SSD. Apparently there were some bad sectors in an initially non-critical area so Windows didn't trip over it (I could run Windows 10 with no problems). But for some reason, the cloning programs weren't intelligent enough to skip the bad sectors and provide a report--they just fail. I first tried Samsung's Data Migration tool, which kept failing at various progress points (usually early on) by suddenly restarting the computer (no warning). I then tried 3 other 3rd party tools, all failed to some degree but at least the system wasn't abruptly restarted.
Trying to fix this sent me down a rabbit hole... as things got progressively worse, to the point where I couldn't boot into the desk top any longer. FINALLY, after discovering the SeaTools FIX utility for repairing bad sectors (took a few cycles due to LBA limitations), I was able to fix the drive enough so that it would boot.
All generalized tests showed healthy partitions. The bad sector issue looked to be isolated to some data segments. I ran "chkdsk /f" and that went to completion. But when I did a scan of the drive using the internal checker from the Explorer tools menu, the Event Viewer suggested running CHKDSK again.
I ran "chkdsk /f /r /x". I realized later that "/f" is redundant, as the "/r" switch covers that.
Now 3 hours later, CHKDSK is still running at 12%. Not budging. I've read some people suggesting to let it complete, that the progress reporting routine is not showing what's really going on, while others saying CHKDSK is probably stuck. I need to travel now and want to take the computer with me. Can I abort the CHKDSK somehow? Keyboard entry of CTRL+C doesn't do anything.