-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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]: Microsoft.DotNet.* #117876
Comments
Except, that the mentioned workaround actually does not work - as described above. Thats because for winget both architectures have the same package ID - it is unable to differentiate. |
It seems to work for me.
|
You can initially tell which bitness to install this way, if no package is installed. Thats correct and working. But now try to make an Side by Side installation this way. Won't be successful, because "package already installed". Upgrading this way will run into the same issue. |
You can add the |
It look like still not work, |
I found a particular file which is AppsandFeaturesEntries. The data can be found on the installer. |
I'm running into this issue as well. I'm specifically looking at the As an example:
It seems like these should be different packages altogether. |
Thats what I asked for initially. Package ID should be unique for each architecture or else will mess things up |
Please confirm these before moving forward
Category of the issue
Side-By-Side installation.
Brief description of your issue
Not sure if this is package or winget related. Please move Issue Report accordingly if wrong here.
I tried to update Microsoft.DotNet.Runtime.3_1 via winget. There are both versions of this package installed on the system.
On upgrading it only upgrades the x64 package, not the x86 one. Manually telling the bitness with --architecture option won't help either.
Its vice versa, if I install x86 version first and after that trying to install x64 package will result in "already installed package found"
I think winget gets confused, because it cant tell apart x86 and x64 by its ID. If this is the case, then all packages (Microsoft.DotNet.*) are affected by this.
Steps to reproduce
Actual behavior
winget reports:
"An existing package has already been found. An attempt is made to update the installed package..."
Expected behavior
winget should be able to install x86 and x64 side by side.
For an possibly correct solution, please take a look at (Microsoft.VCRedist.*) packages:
Package architecture is part of package ID
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: