Brief Description of the Issue

Oct 13, 2025 by thesweetdesigns.com 22 views

[Package Issue]: Winget Finds a Non-Existent Microsoft.VisualStudioCode Installation When It's Been Installed with Scoop

In this article, we will discuss a package issue related to Winget, a package manager for Windows. The issue arises when Winget finds a non-existent Microsoft.VisualStudioCode installation, even though it has been installed using Scoop. We will explore the steps to reproduce this issue, the actual behavior, and the expected behavior. Additionally, we will provide the environment details and screenshots/logs.

The category of this issue is Multiple installed packages found.

Brief Description of the Issue

After installing the vscode package with Scoop and adding the recommended registry entries, Winget finds the non-existent installation with version Unknown and the source Winget. The vscode works fine, and Scoop recognizes its version correctly. However, the behavior is specific to the vscode package only, and it is suspected to be relatively new.

Steps to Reproduce

To reproduce this issue, follow these steps:

Install the vscode package using Scoop: scoop install vscode
Add the recommended registry entries:

reg import "C:\Users\xyz\scoop\apps\vscode\current\install-github-integration.reg"
reg import "C:\Users\xyz\scoop\apps\vscode\current\install-associations.reg"
reg import "C:\Users\xyz\scoop\apps\vscode\current\install-context.reg"

Actual Behavior

After following the steps to reproduce, run Winget list to see the actual behavior:

Microsoft Visual Studio Code           Microsoft.VisualStudioCode             Unknown              1.98.1        winget

As you can see, Winget finds the non-existent installation with version Unknown and the source Winget.

Expected Behavior

The expected behavior is that Winget should not list the vscode installation.

Environment

Here are the environment details:

Windows Package Manager v1.10.340
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.5487
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.25.340.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
Configuration Modules: %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

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:

LocalManifestFiles: Disabled
BypassCertificatePinningForMicrosoftStore: Disabled
InstallerHashOverride: Disabled
LocalArchiveMalwareScanOverride: Disabled
ProxyCommandLineOptions: Disabled
DefaultProxy: Disabled

Screenshots and Logs

Unfortunately, there are no screenshots or logs provided for this issue.

In conclusion, this article discusses a package issue related to Winget, where it finds a non-existent Microsoft.VisualStudioCode installation, even though it has been installed using Scoop. The issue is specific to the vscode package only and is suspected to be relatively new. We have provided the steps to reproduce the issue, the actual behavior, and the expected behavior. Additionally, we have included the environment details and links. We hope that this article will help to identify and resolve this issue.
[Package Issue]: Winget Finds a Non-Existent Microsoft.VisualStudioCode Installation When It's Been Installed with Scoop - Q&A

In our previous article, we discussed a package issue related to Winget, where it finds a non-existent Microsoft.VisualStudioCode installation, even though it has been installed using Scoop. In this article, we will provide a Q&A section to help answer some of the common questions related to this issue.

Q: What is the cause of this issue?

A: The cause of this issue is not yet fully understood, but it is suspected to be related to a bug in Winget or a compatibility issue between Winget and Scoop.

Q: Is this issue specific to the vscode package only?

A: Yes, this issue is specific to the vscode package only. Other packages installed using Scoop do not exhibit this behavior.

Q: How can I reproduce this issue?

A: To reproduce this issue, follow these steps:

Install the vscode package using Scoop: scoop install vscode
Add the recommended registry entries:

reg import "C:\Users\xyz\scoop\apps\vscode\current\install-github-integration.reg"
reg import "C:\Users\xyz\scoop\apps\vscode\current\install-associations.reg"
reg import "C:\Users\xyz\scoop\apps\vscode\current\install-context.reg"

Q: What is the expected behavior of Winget in this scenario?

A: The expected behavior of Winget is that it should not list the vscode installation.

Q: How can I troubleshoot this issue?

A: To troubleshoot this issue, you can try the following:

Check the Winget logs to see if there are any error messages related to the vscode package.
Try uninstalling and reinstalling the vscode package using Scoop.
Check the registry entries to ensure that they are correct and up-to-date.

Q: Is there a workaround for this issue?

A: Yes, there is a workaround for this issue. You can try using the --no-registry flag with Winget to prevent it from checking the registry for installed packages.

Q: Will this issue be fixed in a future version of Winget?

A: We are working to resolve this issue in a future version of Winget. In the meantime, we recommend using the workaround mentioned above.

Q: Can I report this issue to Microsoft?

A: Yes, you can report this issue to Microsoft using the Winget feedback channel.

In conclusion, this article provides a Q&A section to help answer some of the common questions related to the package issue with Winget and Scoop. We hope that this article will help to provide more information and clarity on this issue. If you have any further questions or concerns, please don't hesitate to reach out to us.