Commander_Cool
Senior Member
- Joined
- Jun 29, 2009
- Messages
- 343
- Thread Author
- #1
Hi,
okay, so after booting my PC earlier today Windows System Maintenance started up without prompting and after a while had this to say:
Attempt repairs of disk volume errors
Reboot computer to repair volume problems such as bad sectors, lost clusters, cross-linked files, and directory errors.
in the next screen it says:
Restart computer and begin repairs to bad sectors, lost clusters, cross-linked files, and directory errors. Correcting such errors will allow Windows to accurately report volume information and will free up disk space.
okay, so there are problems that System Maintenance has found, okay. Got it. But not a word as to how I go about reparing these errors, just a very facile 'restart and begin repairs'.
So I assumed that CHKDSK or some other low-level utlity would automatically start on reboot but it didn't.
Sure, I can run CHKDSK manually with the appropriate switches as I have been using computers since DOS 2.0 and am comfortable in the command-line environment, but how about people that aren't?
And what's the point of a utility telling you there is a problem but not how to fix it?
I have probably missed something and would be grateful for a pointer. Thanks.
okay, so after booting my PC earlier today Windows System Maintenance started up without prompting and after a while had this to say:
Attempt repairs of disk volume errors
Reboot computer to repair volume problems such as bad sectors, lost clusters, cross-linked files, and directory errors.
in the next screen it says:
Restart computer and begin repairs to bad sectors, lost clusters, cross-linked files, and directory errors. Correcting such errors will allow Windows to accurately report volume information and will free up disk space.
okay, so there are problems that System Maintenance has found, okay. Got it. But not a word as to how I go about reparing these errors, just a very facile 'restart and begin repairs'.
So I assumed that CHKDSK or some other low-level utlity would automatically start on reboot but it didn't.
Sure, I can run CHKDSK manually with the appropriate switches as I have been using computers since DOS 2.0 and am comfortable in the command-line environment, but how about people that aren't?
And what's the point of a utility telling you there is a problem but not how to fix it?
I have probably missed something and would be grateful for a pointer. Thanks.