microsoft / microsoft/winget-pkgs
[Package Issue]: SmartBear.SoapUI
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 616
Description
### Please confirm these before moving forward
- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.
### Category of the issue
No applicable update found.
### Brief description of your issue
With SmartBear.SoapUI version 5.9.0 installed doing `winget upgrade` it shows an update to version 5.9.1 being available.
However when trying to install the update the message:
```
No applicable upgrade found.
A newer package version is available in a configured source, but it does not apply to your system or requirements.
```
Looking for updates from within SmartBear.SoapUI it also says that there is an update available.
### Steps to reproduce
With SmartBear.SoapUI version 5.9.0 installed:
1. Do `winget upgrade`
2. Verify the availability of an update to version 5.9.1
3. Do `winget upgrade SmartBear.SoapUI --uninstall-previous`
4. Verify that the update does not get installed but only the message `No applicable upgrade found....` is shown
### Actual behavior
The update to SmartBear.SoapUI version 5.9.1 does not get installed and the below message is shown:
```
No applicable upgrade found.
A newer package version is available in a configured source, but it does not apply to your system or requirements.
```
### Expected behavior
The update to SmartBear.SoapUI version 5.9.1 does get installed successfully.
### Environment
```raw
Windows Package Manager v1.12.460
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26100.7623
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.27.460.0
Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
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 State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
DefaultProxy Disabled
```
### Screenshots and Logs
[WinGet-2026-02-18-18-10-12.699.log](https://github.com/user-attachments/files/25396673/WinGet-2026-02-18-18-10-12.699.log)
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 reported commands, `winget upgrade` and `winget upgrade SmartBear.SoapUI --uninstall-previous`, with SmartBear.SoapUI 5.9.0 installed. Review the linked WinGet log and package metadata to identify why version 5.9.1 is considered inapplicable; done means the upgrade installs successfully without the reported error.
Written by the indexing model from the issue text.
Assessment
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100