microsoft / microsoft/winget-pkgs
[Dependency Issue]: Microsoft.DotNet.DesktopRuntime (6/7/8)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
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
Other
Brief description of your issue
Whenever a DotNet DesktopRuntime dependency is required, during package install, if any other version is installed already then the required DotNet dependency is not installed.
My laptop already had Microsoft.DotNet.DesktopRuntime.7 but when I installed HandBrake it required Microsoft.DotNet.DesktopRuntime.6 which was not installed by winget.
Similarly when I installed WHONET.AMRIE which requires Microsoft.DotNet.DesktopRuntime.8 was not installed.
There seems to be matching problem with Microsoft.DotNet.DesktopRuntime packages. They are separate packages, not different versions of same package. Different programs require different DotNet packages so they need to be installed side-by-side. Winget seems to not understand that.
- Related issue #145850
Steps to reproduce
winget install handbrake or winget install WHONET.AMRIE
Actual behavior
Does not install dependency.
When manually try to install
PS C:\Users\drsht> winget install Microsoft.DotNet.DesktopRuntime.6
Found an existing package already installed. Trying to upgrade the installed package...
No available upgrade found.
No newer package versions are available from the configured sources.
Expected behavior
Install both package and its dependency.
Environment
PS C:\Users\drsht> winget --info
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22631.3447
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0
Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
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
Admin Setting State
--------------------------------------------------
LocalManifestFiles Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Enabled
Screenshots and Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the dependency behavior with winget install handbrake and winget install WHONET.AMRIE, then review related issue #145850 and the package dependency metadata involved. Done means required Microsoft.DotNet.DesktopRuntime versions can be installed side-by-side when separate applications require them, with regression coverage for the reported commands.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100