The subject text is the title for an alert I get when I try to run Disk
Defragmenter after I use Task Scheduler to modify the settings for the
ScheduledDefrag task. The alert body text informs me that I must remove
customized settings before I can modify the schedule. The alert presents 2
buttons - Remove Settings and Cancel. This looks like a bug. It's certainly
obnoxious behavior because it's impossible to run a manual defragement
without losing the settings changes made via Task Scheduler.
The only settings change I've made, btw, is to let the ScheduledDefrag task
wake my computer. This option (under the Conditions tab) is not set by
default. Since I leave my computer in an S3 sleep state when not in use, I
want ScheduledDefrag to wake my machine at 1AM on Wednesday (the default time
setting), get the defrag job done and be out of the way by the time I start
the machine first thing in the morning. Also the machine should put itself
back to sleep when the defrag work is done so it doesn't waste energy (I'm
pretty sure this will, but I haven't been able to verify it yet).
Granted, if automatic defrag is happening weekly, I shouldn't need to run a
manual defrag. But it's just dumb that Disk Defragmenter insists that I
remove settings changes I've made via Task Scheduler every time I try to
start it up. Besides the Manual Defrag button, the Disk Defragmenter dialog
provides information about the last time the defrag process ran successfully.
The Disk Defrag dialog basically becomes inaccessible unless I'm willing to
remove my setting changes and reapply them every time I want to view/use the
Disk Defrag dialog.
This may be a low severity bug, but it's the kind of defect that makes users
wonder whether the program managers, developers, and testers at Microsoft
really know what they are doing. You should seriously consider fixing this
one for SP1.