I have a script to run chkdsk and search the output for the "cannot continue in read-only" phrase that signals that the /f version needs to be enabled in the registry for the next re-start.

Everything works fine but I frequently get bogus information such that while the trigger phrase is in the output file, a second manual chkdsk does not report the errors.

i.e. on my own machines I may see my message displayed that a re-boot is required, but a manual chkdsk from the command prompt does not return the phrase although it does exist in the redirected output from the scripted chkdsk.

I originally had my script running daily and had frequent bogus alerts for re-boot, but after I decreased the script frequency to weekly, I very seldom get these bogus reports.

Can anyone comment, had similar experience, etc?

Legacy Forum Name: inconsistent chkdsk results,
Legacy Posted By Username: ggibbs@chartermi.net