5 replies
by stevehirahara Accepted solution
by garycoryer Accepted solution
Steve,
Did you figure this out, my system started putting out these messages today?
Gary
by stevehirahara Accepted solution
actually, it's still doing it. but I understand that you need to boot in "safe mode" and then let it complete chkdsk /f and then it will be okay.
I had this happen once before, and ended up crashing the whole system, and having to restore Windows from cd's, and having three quarters of my hard drive inaccessible. so you can see why i am reluctant to do anything about a minor annoying message at boot. sometimes, i end the message by hitting boot, and sometimes i let it run it's silly little command, but it's sometimes better not to bother with trying to fix it, unless it's really slowing down your boot up.
by stevehirahara Accepted solution
Thank you for your timely reply. Between the time I posted my question and your response, I did take the Safe Mode approach, but with the command prompt. Poking around for options, I followed a recommendation to enter the command chkntfs /x c: directing the computer to exclude the c: drive from the chkdsk operation. It worked.
it would seem to make sense that this would be a direct instruction to the os to stop being so stupid.
by older mycroft Accepted solution
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending