Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot update sources with Administrator promt #3082

Open
simkoG opened this issue Mar 16, 2023 · 1 comment
Open

Cannot update sources with Administrator promt #3082

simkoG opened this issue Mar 16, 2023 · 1 comment
Labels
Command-Source Issue related to WinGet Source Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@simkoG
Copy link

simkoG commented Mar 16, 2023

Brief description of your issue

We have a small office with about ten computers. I am using Winget to keep my apps up-to-date. All these machines have an administrator account and a standard user. I only use the administrator account if it's necessary. I just log in as the standard user for every day usage.

The problem is that I cannot update the winget sources with an elevated command prompt. Because of this, I cannot use winget to upgrade all my apps with a single command.

If I run a command prompt without admin rights, I will have to type my password for every application upgrade. With ten computers and about five applications it's a nightmare, just to think about it.

Steps to reproduce

  1. Create a "Standard" and an "Administrator" Windows user.
  2. log in to the "Standard" user.
  3. Run the cmd.exe with admin rights.
  4. winget source update.
  5. The winget source will be stuck at 0% and returns a Done message.
  6. winget upgrade will output: No installed package found matching input criteria.
  7. Run the cmd-exe without admin rights.
  8. winget source update.
  9. winget upgrade --all will update the applications now, but you will have to log in to the admin account for every application install.

Expected behavior

Be able to update winget sources with the admin command prompt.

Actual behavior

I can only update the sources with a non-admin command prompt.

admin prompt non-admin prompt
01 02

Environment

> winget --info
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.2604
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Mar 16, 2023
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Mar 16, 2023
@denelon denelon added this to the v.Next-Client milestone Jun 5, 2023
@denelon denelon added the Command-Source Issue related to WinGet Source label Jun 10, 2023
@Alarith
Copy link

Alarith commented Aug 8, 2023

I have the same issue. I work in a domain without local admin rights. I can start winget as a normal user and everything works fine, but I need to enter the admin credentials for every software updated (A workaround might be to cache the authorization). When I use the "run as administrator" function on powershell and then start winget, I get the searching for sources error.#
A solution for this issue would be greatly appreciated :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-Source Issue related to WinGet Source Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

3 participants