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

[Package Issue]: Dell.DisplayManager #107808

Closed
2 tasks done
Andrew-J-Larson opened this issue May 22, 2023 · 2 comments
Closed
2 tasks done

[Package Issue]: Dell.DisplayManager #107808

Andrew-J-Larson opened this issue May 22, 2023 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@Andrew-J-Larson
Copy link

Andrew-J-Larson commented May 22, 2023

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Trying to update Dell Display Manager from 2.0 to 2.1.x from winget causes issues, depending on where the installer is located.

In this case, since the installer is downloaded to C:\Users\axla\AppData\Local\Temp\WinGet\Dell.DisplayManager.2.1.1.17\ddmsetup.exe, ddmsetup.exe doesn't elevate correctly...

However, if trying to navigate to this directory and trying to elevate manually, it also errors out the same way. The only way to elevate the program properly is to move it to another folder outside of the AppData folders (e.g. to the user's downloads folder), and then open and elevate from there.

Steps to reproduce

  1. Make sure that Dell Display Manager 2.0 is installed
  2. Run winget upgrade --id Dell.DisplayManager as an unelevated (non-admin) user.
  3. Elevate with an admin user when the prompt shows for install.

Actual behavior

Fails to install, thinks the user is aborting the install, when that's in fact not the case.

Expected behavior

Should upgrade from 2.0 to the 2.1.x version of Dell Display Manager.

Environment

Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.1702
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0

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

User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json

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

Screenshots and Logs

WinGet-2023-05-22-16-28-52.418.log

@Andrew-J-Larson Andrew-J-Larson added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 22, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label May 22, 2023
@stephengillie stephengillie removed the Needs-Triage This work item needs to be triaged by a member of the core team. label May 24, 2023
@mdanish-kh
Copy link
Contributor

Can you please install the latest preview version of WinGet from aka.ms/getwingetpreview and see if the package upgrades correctly for you?

There was a known CLI bug related to permissions on the TEMP folder that was patched in the preview version. That may be the fix here?

@Andrew-J-Larson
Copy link
Author

Tested this today, appears to be fixed now. Closing.

@denelon denelon added this to the 1.7 Packages milestone Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

4 participants