You will note that according to the final version (above) of tasks that can be disabled, PushToInstall is not on that list.
I would like to know if is ok to disable, or if you want as little interference from MS as possible should it be disabled, or what is known to break if it is disabled.
Edit: I also notice that no updateorchestrator tasks are on the list.
In regards to SSD defragging, it does actually happen in specific scenarios and according to Microsoft is intended behaviour.
If VSS is enabled on an SSD partition (system restore) then this can cause excess fragmentation and an SSD with this enabled will occasionally get defragged, although its not a full defrag.
If it does do the defrag its done on boot, not as a background idle task.
Since larger cluster sizes decrease metadata and the reason for the defrag is metadata, its very likely using a larger cluster size would reduce the occurrences of VSS related defrags.
I used to have defrag automation disabled, but observed what appeared to be slow delays when saving files to the SSD, loading certain apps, then the first reboot after I enabled it again, the boot SSD got auto defragged and that delay disappeared. I do make frequent system restore points. It didnt auto defrag again until over 2 months later, so its not frequent, but something to be wary off when tinkering with defrag configuration including its task, as most people think SSDs will never get auto defragged.
It seems that a new task has appeared with the August update KB5029244.
\Microsoft\Windows\CloudRestore\<Backup> (Handles restoring settings from the cloud)
I think it's related to the 'new' Windows-Backup which is part of the Windows Feature Experience Pack 1000.19044.1000.0.
I have disabled that task because I don't shove my backups or settings to the cloud and did uninstall Onedrive right after installing Windows 10 a while ago. So there is nothing to restore from there for me anyway.
Quote