-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Multiple installed packaged found #1083
Comments
@AdilHindistan can you share the output for We've run into some challenges with packages that have a different version number than what shows up in "Add / Remove Programs". The Visual Studio Code manifests have a four part version number, and only the first three appear to be registered in Windows. |
I'm also wondering if you have the "stable" release and a daily build installed on your machine. I've seen some interesting interactions with packages that have side by side install support. |
How do I check @denelon ? |
Run |
I think you are onto something here @denelon
When I launch appwiz.cpl to check, it shows two entries.
System-wide one is the older version, the one shown on top and it is installed at
user version is installed at I don't recall installing 2 different versions. Judging by the date, it looks like I wanted to update the vscode and update ended up in the %appdatalocal%\ |
The Windows Package Manager has "settings" and an argument to specify "User" vs. "Machine". The default is "User" when not specified (assuming the manifest is configured correctly). Depending on when and how the first version was installed, this could have been the result of the Windows Package Manager not being able to map to the version or scope on your machine. We will need to perform some additional testing to see if the behavior is correct in the client, or if we need to make some additional changes in the code paths to see if it is possible to detect which one a user has installed, and at least provide a warning to avoid this scenario. We have a feature to look at "UpgradeCode" in MSI packages, and I'm hoping that will properly address at least this scenario. Thank you so much for the detailed analysis! It really helps when we have sufficient data to be able to troubleshoot and reproduce errors |
I believe we have narrowed down what has happened in this case. The previous version was installed as "machine" and the installer in the manifest currently defaults to "user". We see the earlier version, but when we install we install the new version as "user". This shows up as a second entry. I'm not sure what we could do in cases like this to help improve experience. If you can think of a better behavior, let us know. I'd be happy to have a new "Feature" request additional behavior or user control. |
@denelon I'm experiencing this issue when trying to uninstall a package.
One of those packages (the new one) was installed via an .exe downloaded from the internet, the other one was installed via winget (at least that's how I remember it, don't count on it though). So I wanted to remove one of the packages:
I totally understand why the command would fail, so I found out about the "exact" flag and tried that:
The ids are clearly not the same, why is this failing? I'm also confused as to why the I also reported the issue here: #282 (comment), but I assume it's the wrong issue as that is specifically about installing powershell. In case you are wondering about the version:
|
Brief description of your issue
Cannot upgrade Visual Studio Code as winget fails to properly use the provided criteria
Steps to reproduce
All of the following commands fail:
Expected behavior
It should match just the top one:
Actual behavior
Matches another install that actually does not have the id I typed.
Environment
The text was updated successfully, but these errors were encountered: