R
Richard
This is what I figured out since the last post.
Hopefully someone has some sort of a solution. ChckDsk
runs on drive E (hard drive part') on startup. The
others part's are fine. I figured I would do as
much "cleaning" to the drive is possible to see if it
would help.
I figured I would first run another ChckDisk. I had to
restart to do this, it went through, no problems and
booted up. Next, I tried to run defrag on E and it said
that ChckDsk is scheduled to run on the drive, and to do
that first. BUT I had JUST ran the ChckDisk! Is it
possible that it is permanently scheduled? I know there
is a registry tweak to disable ChckDsk, but I'd rather
not do that just in case one day something does go
wrong.
FYI - I've been to the support link for the issue (caused
by a registry fault or HP scanner), and didn't find a
solution there.
Any suggestions? I'm completely baffled!
Thanks in advance,
Richard
Hopefully someone has some sort of a solution. ChckDsk
runs on drive E (hard drive part') on startup. The
others part's are fine. I figured I would do as
much "cleaning" to the drive is possible to see if it
would help.
I figured I would first run another ChckDisk. I had to
restart to do this, it went through, no problems and
booted up. Next, I tried to run defrag on E and it said
that ChckDsk is scheduled to run on the drive, and to do
that first. BUT I had JUST ran the ChckDisk! Is it
possible that it is permanently scheduled? I know there
is a registry tweak to disable ChckDsk, but I'd rather
not do that just in case one day something does go
wrong.
FYI - I've been to the support link for the issue (caused
by a registry fault or HP scanner), and didn't find a
solution there.
Any suggestions? I'm completely baffled!
Thanks in advance,
Richard