Duplicate ShiningLight.OpenSSL that refuses to uninstall
Brief description of your issue
ShiningLight.OpenSSL package refuses to uninstall and duplicate entries show up
Steps to reproduce
winget install ShiningLight.OpenSSL
❯ winget upgrade
Name Id Version Available Source
-------------------------------------------------------------------------------------------------------------------
Microsoft Windows Desktop Runtime - 3.1.32 (x64) Microsoft.DotNet.DesktopRuntime.6 < 6.0.5 6.0.14 winget
OpenSSL (64-bit) ShiningLight.OpenSSL 1.0.0 3.0.8 winget
Adobe Acrobat DC (64-bit) Adobe.Acrobat.Reader.64-bit 22.001.20142 22.003.20310 winget
OpenSSL 3.0.8 (64-bit) ShiningLight.OpenSSL 1.0.0 3.0.8 winget
4 upgrades available.
then
❯ winget uninstall ShiningLight.OpenSSL --force
Found OpenSSL [ShiningLight.OpenSSL]
Starting package uninstall...
Uninstall failed with exit code: 1603
Expected behavior
I expect running winget uninstall to remove the package in question
Actual behavior
winget install ShiningLight.OpenSSL
then
❯ winget uninstall ShiningLight.OpenSSL --force
Found OpenSSL [ShiningLight.OpenSSL]
Starting package uninstall...
Uninstall failed with exit code: 1603
Environment
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22623.1325
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.441.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
Admin Setting State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
Do you have more than one version installed?
Run winget list OpenSSL to see if more than one version is installed. If you see multiple instances, you may need to manually remove one of them. We have a bug on removing a specific version of a package when more than one is installed.
It seems that there are more than one installed, but manually trying to uninstall the package refuses to work even through the control panel.
The issue seems to be dangling registry keys that point to installers that no longer exist in the file system. Forcibly deleting the registry keys fixes the issue. I'm not sure what winget could do here.
@musm Care to share the registry keys you had to delete to resolve this as I too face this issue ?
@Trenly have you found anything that could help here?
Revo uninstaller is really good at removing errant registry keys; I'll take a look to see if I can find where the registry keys for ShiningLight.OpenSSL live
After more digging, the uninstaller expects to find the uninstaller in the winget folder, but for some reason it does not exists. The other version of the openssl exists but the uninstaller ends up failing.
It would be helpful if winget could integrate the automatic removal of errant registry keys..
@musm, that's really up to the installer/uninstaller. WinGet will only modify entries it added (portable packages).
I have the same problem and can't find the answer :(
I had this same issue. I ran the Uninstallers from settings with no success... but the Program Install and Uninstall Troubleshooter was able to clean it up.
I have exactly the same issue regarding this package (ShiningLight.OpenSSL). When I try to upgrade the package, it creates another entry of the same package:
Name Id Version Available Source
--------------------------------------------------------------------
OpenSSL 3.1.2 (64-bit) ShiningLight.OpenSSL 1.0.0 3.1.2 winget
OpenSSL 3.1.1 (64-bit) ShiningLight.OpenSSL 1.0.0 3.1.2 winget
I strongly believe that something is going wrong with the package itself.
I was encountering an issue with this package's versioning and was about to report the same behavior as above, a little bit of searching informed me that the versioning issue is related to how the publisher uses the versioning number, all we can do is wait and see if they are willing to correct it.
related issues under winget-pkgs repo that details the issue: https://github.com/microsoft/winget-pkgs/issues/99634 https://github.com/microsoft/winget-pkgs/issues/38249