Optimize and Defrag Schedule issue

I know this is an old thread but I have a clean install of windows 10 currently version 1909 and it does the very same thing ignoring my settings. I always have to perform it manually or it doesn't get done.

Try3 said:

To avoid misunderstandings, please explain exactly what each of the "it"s is and what settings are being ignored.
If your point is going to be that you have defrag set to weekly but trim only takes place monthly then note that this is normal behaviour [see https://docs.microsoft.com/en-us/win...ommands/defrag].

Denis

Weekly settings Dennis.....

HRPuffnstuff said:

Weekly settings Dennis.....

Same here (Clean install of 10) 1909 Build 18363.628. Had it set to 'weekly' and just noticed that none of the SSDs have been optimized for the last 29 days. Ran it manually.

Try3 said:

If you read the link I posted you might well conclude that Windows only trims monthly despite the weekly Optimise setting because MS don't think it worthwhile trimming any more frequently.


Denis

Didn't see anything in that link referencing setting to weekly will not run.

I just trim it manually as it only takes about 10 seconds max to initiate on my 4 drives.

I searched online and noticed that the same concerns are raised elsewhere, i.e., the defrag doesn't run as scheduled. That is, the schedule is set weekly and the last run was several weeks ago.

I checked the task created in the scheduler and there appears to be nothing in the settings that requires the program to stop if it ceases to be idle, and the option to start the task if the time is missed is activated. Given that, I don't know what's causing this problem. Similar problems took place for earlier versions of Windows.

I tried creating a defrag schedule but could not make it run. Given that, I'd like to know if it's possible to create a defrag schedule with the ff. options:

1. Wait for the machine to be idle and then start defragmenting, or do so at a certain time but run the scheduled task by force if the time is missed.

2. That is, try not to abort defragmentation if user activity takes place, or maybe set a processor load limit to the task given user activity.