You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have it run on my systems in the SYSTEM context which never results in windows pop-ups and that's perfect. Logs perfectly and updates the majority of my apps system-wide.
However, one limitation is that if the app was installed in the USER context, then Winget_SYSTEM will not update it.
Normally Winget runs as USER. If I have it scheduled like this:
I get a pop-up of an empty cmd terminal while the script is finished, and my apps are updated to the latest version. This is "suboptimal" and "annoying". Is there a way to have winget run as USER but still NOT give you any pop-ups? As SYSTEM this indeed does work, but not as USER at least I haven't found a way to do it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have it run on my systems in the SYSTEM context which never results in windows pop-ups and that's perfect. Logs perfectly and updates the majority of my apps system-wide.
However, one limitation is that if the app was installed in the USER context, then Winget_SYSTEM will not update it.
Normally Winget runs as USER. If I have it scheduled like this:
It will result in windows pop-ups.
If in TSK SCHDLR, the program is: "powershell.exe"
If in TSK SCHDLR, I pass this arguement:
I get a pop-up of an empty cmd terminal while the script is finished, and my apps are updated to the latest version. This is "suboptimal" and "annoying". Is there a way to have winget run as USER but still NOT give you any pop-ups? As SYSTEM this indeed does work, but not as USER at least I haven't found a way to do it.
Beta Was this translation helpful? Give feedback.
All reactions