"Run whether user is logged on or not" is broken since 22H2 update. Microsoft is being eerily silent around the subject, which leads me to believe that this is a 'feature' instead of a 'bug'.
It makes the task scheduler very useless for a large number of use cases. If you enable "Run whether user is logged on or not" but also put a check in "Do not store the password" the task will run, but you won't have any access to network resources. Again, very useless for a number of use cases.
This is where Microsoft should learn a thing or 2. 'Communicate'. The company always pats itself on the back for being so great (I can know, I've been a blue badge for 8 years), but when it comes around these type of issues no one is having the decency to either confirm or deny the problem; We just ignore it all together because no1 wants to steer the hornet's nest (not my problem mentality).
Prove me wrong?