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
Winget was always present in user context, so going to terminal / command line as a user, winget was also found for me. Now I see that recently installed Windows 11 machines does not see winget under user context.
I tried to add-package source2.msix, it adds its well but still command not present.
Steps to reproduce
Login without admin rights, open powershell, terminal or cmd. Type "winget" and you'll have "The term 'winget' is not recognized as the name of a cmdlet, function ..."
Expected behavior
Winget was always available under user profile, typing Winget listed all commands and availability of packages, searchint etc.
Actual behavior
Login without admin rights, open powershell, terminal or cmd. Type "winget" and you'll have "The term 'winget' is not recognized as the name of a cmdlet, function ..."
Environment
Package not found
The text was updated successfully, but these errors were encountered:
Brief description of your issue
Winget was always present in user context, so going to terminal / command line as a user, winget was also found for me. Now I see that recently installed Windows 11 machines does not see winget under user context.
I tried to add-package source2.msix, it adds its well but still command not present.
Steps to reproduce
Login without admin rights, open powershell, terminal or cmd. Type "winget" and you'll have "The term 'winget' is not recognized as the name of a cmdlet, function ..."
Expected behavior
Winget was always available under user profile, typing Winget listed all commands and availability of packages, searchint etc.
Actual behavior
Login without admin rights, open powershell, terminal or cmd. Type "winget" and you'll have "The term 'winget' is not recognized as the name of a cmdlet, function ..."
Environment
The text was updated successfully, but these errors were encountered: