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
Issue: 0x80070005 Access denied for winget commands after usage of gsudo (owner of folder %localappdata%\Temp\WinGet is changed to the used admin account)
#376
Open
coka4you opened this issue
Sep 10, 2024
· 4 comments
After executing the command ‘gsudo winget xyz (e.g.: list)’, the owner of the folder %localappdata%\Temp\WinGet is changed to the local admin account. Explicit permissions are set for the admin account used. As a result, all subsequent winget commands under normal user rights fail with the message ‘Access denied’. This does not occur with a regular shell with elevated rights (via UAC).
Only manually taking ownership and granting full access for the normal user or deleting the folder %localappdata%\Temp\WinGet will allow further winget commands without admin rights.
Steps to Reproduce
cmd: winget list -> everything fine
cmd: gsudo winget list -> everything fine
cmd: winget list -> access denied
take ownership for %localappdata%\Temp\WinGet
cmd: winget list -> everything fine
Screenshots
Context:
Windows version: Win10 22H2, Build 19045.4780
gsudo version: v2.5.1
The text was updated successfully, but these errors were encountered:
Issue Description
After executing the command ‘gsudo winget xyz (e.g.: list)’, the owner of the folder %localappdata%\Temp\WinGet is changed to the local admin account. Explicit permissions are set for the admin account used. As a result, all subsequent winget commands under normal user rights fail with the message ‘Access denied’. This does not occur with a regular shell with elevated rights (via UAC).
Only manually taking ownership and granting full access for the normal user or deleting the folder %localappdata%\Temp\WinGet will allow further winget commands without admin rights.
Steps to Reproduce
Screenshots
Context:
The text was updated successfully, but these errors were encountered: