Reason I hesitated to answer your question is because parts of what you
describe made no sense, so I had to read up. That's also why I wanted more
details.
When you run CHKDSK /f on a partition with open files (drive cannot be
locked), it should refuse to run and prompt you to have it to run after a
restart. This should ALWAYS occur on the system partition. However, there is
this blurb in Help:
"If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive."
....which is what I think you're getting. What you describe doesn't really
match those words, but it's too close a coincidence to ignore. Perhaps,
somehow, CHKDSK is *always* putting up spurious error notices when what it
should be doing is prompting you to run CHKDSK on restart due to the
partition not being lockable. I won't speculate on *how* this might have
occurred (though that defrag program does come to mind), just that it sounds
like what like is happening to your system.
So, tentatively, I'd say the error notices you're getting are spurious. But
you still haven't given me the error notice(s) verbatim -- EXACTLY what do
they say? Is the error message EXACTLY the same whether prompted by O&O
Defrag or by CHKDSK?
When you do run CHKDSK /f on C:\, it *does* prompt you to let it run after a
restart, does it not? Also, since you mention other partitions, are you
multi-booting other OSes or are they all (except C:\) simple data storage
partitions? In particular, what's on that "other partition" that you mention
having the same problem.
Two things I'd try: Frist, I'd uninstall O&O and then try
CHKDSK C:
and see if it still reports errors.
After testing, reinstall O&O and then check for updates at the app's site.
Then run its defrag.
