Windows 10 2004 optimization/defrag bug

All I know is that when you check  disk optimizer, it wil say that your  SSD has never been optimized and that it needs  to be optimized. If you do this, it will trim the SSD, as it is supposed to to. The problem is that it then 'forgets' that it has optimized the SSD. The next time you start your computer, it will say that the SSD has never been optimized and that it needs optimization. 

If you do a manual maintenance (via control panel, security and maintenance), then Windows starts defragging the SSD, which it is not supposed to do and then, again, forgets that it has done so the next time you start your computer. I know, it sounds weird...  

Following a closed thread I opened Task Scheduler and looked under the defrag node. I had the optimization app set for weekly, but the defrag action had I think "forgotten" to include a trigger. Could be interconnected with the "never run" aspect of things?

That is a good thought but personally I feel we should not have to go out and hunt for workarounds to this. This is clearly a MS problem they introduced with their flawed Version 2004 update along with the annoying push notification a lot of members are getting about needing to fix their account in that worthless Shared Experiences in Settings and also Edge Chromium and Chrome not showing your saved passwords unless you sign into your accounts so they can see what you are doing on the web. These three are just a few of the bugs that Ver. 2004 has let loose in our computers and MS needs to kill these bugs with a fix. I am going to wait for a fix to be deployed as I fear more damage will be done trying to solve problems MS created. I do not know what MS considers having a smooth experience but this has been far from that.

All I know is that when you check  disk optimizer, it wil say that your  SSD has never been optimized and that it needs  to be optimized. If you do this, it will trim the SSD, as it is supposed to to. The problem is that it then 'forgets' that it has optimized the SSD. The next time you start your computer, it will say that the SSD has never been optimized and that it needs optimization. 

If you do a manual maintenance (via control panel, security and maintenance), then Windows starts defragging the SSD, which it is not supposed to do and then, again, forgets that it has done so the next time you start your computer. I know, it sounds weird...  

Following a closed thread I opened Task Scheduler and looked under the defrag node. I had the optimization app set for weekly, but the defrag action had I think "forgotten" to include a trigger. Could be interconnected with the "never run" aspect of things?

does this mean im safe from auto Defrag on restarts? i only use SSD's

The 2004 build is flawed on more than one account! As suggested I switched off automatic defrag/trim but I had a snappy 1909 build system and 2004 turned into a sluggish, erratic system! I got the update on April 17th BTW.

System now is slow to start and even slower to shut down! (over a minute) Did they reset the system close down time or even make it longer? A PITA!

Staring up 3rd party programs now takes like forever! Coral Paintshop 35 seconds! really? I get the "not responding" message more than I care to tell and then of course the message suddenly disappears which means that some system stuff is really not in sync! 

Mouse has become erratic in some apps perceiving "mouse clicks" where none were made ... it is really an absolute PITA!

I already did a DISM with restorehealth using the 2004 install.wim ... solves nothing.

I'm stuck with one irremovable app in the store and startcomponentcleanup now mysteriously breaks off at 20%, something I've never seen in whole my life and I've been using Windows from version 1.0 (yes not 10!)

And I was just too late to roll the darned thing back to 1909 ... 10 days grace period. 

FYI I'm running an I7-4790 cpu with 16 gig RAM and a 500 GB Samsung SSD, just to make sure ...

if microsoft dont wanna fix it start asking for help  / forbes /bussiness insider .....  on twitter ?  maybe they will have a solution ....