Disk Defragment Schedule Bug

  • Thread starter Thread starter AAndonian
  • Start date Start date
A

AAndonian

As an FYI,

Vista x64 does not allow a disk defragment schedule of monthly - last
day - 1:00AM to be accepted. The OK button is greyed out. Steps to
reproduce:

1) Click on Start Orb then click Control Panel
2) Click on the Control Panel Home in the left hand pane
3) Click on System and Maintenance
4) Under the Administrative Tools heading click on Defragment your
hard drivve
5) Click Continue for the User Account Control screen
[Take note of the Next Scheduled Run date and time]
6) In the window titled Disk Defragmenter click Modify schedule
7) In the window titled Disk Defragmenter: Modify Schedule choose the
following settings:
* How often: Monthly
* What Day: Last Day
* What time: 1:00 AM
8) Click OK

Note: The OK button on the window titled Disk Defragmenter is greyed
out. Note the Next Scheduled Run date and time is incorrect which
shows the previous scheduled date and time.

I've already contacted the vendor and informed them of the bug.
 
As an FYI,

Vista x64 does not allow a disk defragment schedule of monthly - last
day - 1:00AM to be accepted. The OK button is greyed out. Steps to
reproduce:

1) Click on Start Orb then click Control Panel
2) Click on the Control Panel Home in the left hand pane
3) Click on System and Maintenance
4) Under the Administrative Tools heading click on Defragment your
hard drivve
5) Click Continue for the User Account Control screen
[Take note of the Next Scheduled Run date and time]
6) In the window titled Disk Defragmenter click Modify schedule
7) In the window titled Disk Defragmenter: Modify Schedule choose the
following settings:
* How often: Monthly
* What Day: Last Day
* What time: 1:00 AM
8) Click OK

Note: The OK button on the window titled Disk Defragmenter is greyed
out. Note the Next Scheduled Run date and time is incorrect which
shows the previous scheduled date and time.

I've already contacted the vendor and informed them of the bug.
Click to expand...

Confirmed bug to be fixed in SP2.
 
Back
Top