I have set it to run as SYSTEM and only when the user is logged in.
In that context, the "user" is SYSTEM, not any desktop user. To get it to run when a user logs on, you should set it to run as INTERACTIVE.
I have no experience with SystemUI.exe. I don't know what requirements/restrictions it has in order to properly function.
Another option would be to modify the scripts that I provided in your prior post. In the Server script, change the Client task to run at user logon.
SCHTASKS /Create /tn "ClientTask" /tr "Powershell.exe -File ""$ScriptFolder\Client.ps1""" /ru interactive /sc onlogon /f
So the Server task will launch, and create the Client task with a trigger to run at logon time. If a user is logged on at the time, the schtasks /run will launch it for them immediately. If no user is logged on, I would expect that the ONLOGON trigger would start the task when the next user logs in. But I have not tested that.
The Server script will just sit and wait until a Client.msg file shows up.
Check the Server task settings for "Stop the task if it runs longer than:" setting. Adjust for however long you want to wait.
https://learn.microsoft.com/en-us/answers/questions/246173/scheduled-task-to-launch-powershell-script-in-syst.html