Please confirm these before moving forward
Category of the issue
No applicable update found.
Brief description of your issue
The manifest lacks scope: machine, so this package can not be updated, when using the scope parameter.
Steps to reproduce
winget remove Microsoft.DotNet.DesktopRuntime.10
winget install Microsoft.DotNet.DesktopRuntime.10 --version 10.0.8 -> installs whether admin or user (note: as user with UAC prompt for elevation)
winget upgrade --scope=machine -> shows Microsoft.DotNet.DesktopRuntime.10 (10.0.8 -> 10.0.9)
winget upgrade --scope=user -> nothing
winget install Microsoft.DotNet.DesktopRuntime.10 --scope=machine -> quits with -1978335189 ("No Applicable Upgrade Found")
Actual behavior
Since the scope is missing from the manifest, environments/tools that rely on programmatically running through user/machine updates, can not upgrade this package anymore. The upgrade is only applied when omitting the scope parameter completely, which fundamentally breaks such workflows.
Expected behavior
scope: machine should be included in the manifest, since the package installs machine-wide stuff and asks for elevation.
Environment
Windows-Paket-Manager v1.29.280
© 2026 Microsoft. Alle Rechte vorbehalten.
Windows: Windows.Desktop v10.0.26200.8737
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.29.280.0
WinGet-Verzeichnisse
-----------------------------------------------------------------------------------------------------------------------
Protokolle %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Local…
Benutzereinstellungen %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Local…
Verzeichnis für portierbare Links (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portables Linkverzeichnis (Computer) C:\Program Files\WinGet\Links
Portierbarer Paketstamm (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portierbarer Paketstamm C:\Program Files\WinGet\Packages
Portierbares Paketstamm (x86) C:\Program Files (x86)\WinGet\Packages
Installationsprogrammdownloads %USERPROFILE%\Downloads
Konfigurationsmodule %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules
Links
-----------------------------------------------------------------------------------------
Datenschutzerklärung https://aka.ms/winget-privacy
Lizenzvereinbarung https://aka.ms/winget-license
Hinweise von Drittanbietern https://aka.ms/winget-3rdPartyNotice
Startseite https://aka.ms/winget
Windows Store-Nutzungsbedingungen https://www.microsoft.com/en-us/storedocs/terms-of-sale
Administratoreinstellung Status
-----------------------------------------------------
LocalManifestFiles Deaktiviert
BypassCertificatePinningForMicrosoftStore Deaktiviert
InstallerHashOverride Deaktiviert
LocalArchiveMalwareScanOverride Deaktiviert
ProxyCommandLineOptions Deaktiviert
ConfigurationProcessorPath Deaktiviert
DefaultProxy Deaktiviert
Screenshots and Logs
Note: This problem does also exists for Microsoft.DotNet.DesktopRuntime.8 + Microsoft.DotNet.DesktopRuntime.9 and has been confirmed as a bug there.
Please confirm these before moving forward
Category of the issue
No applicable update found.
Brief description of your issue
The manifest lacks
scope: machine, so this package can not be updated, when using the scope parameter.Steps to reproduce
winget remove Microsoft.DotNet.DesktopRuntime.10winget install Microsoft.DotNet.DesktopRuntime.10 --version 10.0.8-> installs whether admin or user (note: as user with UAC prompt for elevation)winget upgrade --scope=machine-> shows Microsoft.DotNet.DesktopRuntime.10 (10.0.8 -> 10.0.9)winget upgrade --scope=user-> nothingwinget install Microsoft.DotNet.DesktopRuntime.10 --scope=machine-> quits with -1978335189 ("No Applicable Upgrade Found")Actual behavior
Since the scope is missing from the manifest, environments/tools that rely on programmatically running through user/machine updates, can not upgrade this package anymore. The upgrade is only applied when omitting the scope parameter completely, which fundamentally breaks such workflows.
Expected behavior
scope: machineshould be included in the manifest, since the package installs machine-wide stuff and asks for elevation.Environment
Screenshots and Logs
Note: This problem does also exists for Microsoft.DotNet.DesktopRuntime.8 + Microsoft.DotNet.DesktopRuntime.9 and has been confirmed as a bug there.