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 use winget for distributing and updating software across various computers and VMs. Since the scripts are distributed and executed via an RMM, they run in the system context. Normally, winget is executed in the user context, making the simple execution of the "winget" command impossible. Therefore, in the script, I directly call winget.exe located in the path C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller**. This method works flawlessly on computers that were newly installed in October 2023 and before. However, it does not work on newer installations. When calling "winget -v", I correctly get the version output on older installations, but I get no output (not even an error message) on new installations. I have performed basic debugging, such as checking the path, etc., and could not find any differences. All Windows updates and Windows Store updates are current.
Additionally, although this might not be directly related, I used the Sysinternals tool ProcMon to compare the processes on two computers. On the new installations, I noticed that a process is started, but then its process ID changes. This does not happen on existing installations, where the process ID remains the same.
Steps to reproduce
Perform a fresh installation of Windows 10.
Install all Windows updates and Windows Store updates
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Brief description of your issue
I use winget for distributing and updating software across various computers and VMs. Since the scripts are distributed and executed via an RMM, they run in the system context. Normally, winget is executed in the user context, making the simple execution of the "winget" command impossible. Therefore, in the script, I directly call winget.exe located in the path C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller**. This method works flawlessly on computers that were newly installed in October 2023 and before. However, it does not work on newer installations. When calling "winget -v", I correctly get the version output on older installations, but I get no output (not even an error message) on new installations. I have performed basic debugging, such as checking the path, etc., and could not find any differences. All Windows updates and Windows Store updates are current.
Additionally, although this might not be directly related, I used the Sysinternals tool ProcMon to compare the processes on two computers. On the new installations, I noticed that a process is started, but then its process ID changes. This does not happen on existing installations, where the process ID remains the same.
Steps to reproduce
Expected behavior
The version should be output.
Actual behavior
No output is produced.
Environment
winget --info] on a fresh installation:
[winget --info] on an existing installation:
The text was updated successfully, but these errors were encountered: