Cannot install version 1.3: DDLM package not found

[KarelChanivecky]

Describe the bug

Cannot install version 1.3.
The output is as such:

PS C:\Users\User\Downloads> .\WindowsAppRuntimeInstall1.3.exe
Installing license: MSIX_MAINPACKAGE_LICENSE
Install License result : 0x0
Installing license: MSIX_SINGLETONPACKAGE_LICENSE
Install License result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Main.1.3_3000.934.1904.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: Microsoft.WinAppRuntime.DDLM.3000.934.1904.0-x6_3000.934.1904.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x80073cf1 Package was not found.
Deploying package: Microsoft.WinAppRuntime.DDLM.3000.934.1904.0-x8_3000.934.1904.0_x86__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x80073cf1 Package

v1.4 does install properly. Is it possible that there are broken links in the old installer now that 1.4 has been released.

I have tried obtaining installers from:
https://aka.ms/windowsappsdk/1.3/1.3.230724000/windowsappruntimeinstall-x64.exe
and
https://aka.ms/windowsappsdk/1.3/latest/windowsappruntimeinstall-x64.exe

Steps to reproduce the bug

1. Download 1.3 installer from
   https://aka.ms/windowsappsdk/1.3/1.3.230724000/windowsappruntimeinstall-x64.exe
   or
   https://aka.ms/windowsappsdk/1.3/latest/windowsappruntimeinstall-x64.exe
2. Run the installer with admin privileges

RESULT:
Only the following is installed:

Expected behavior

Packages akin to the ones in the screenshot, but with the proper version for 1.3 appear:

Screenshots

No response

NuGet package version

None

Packaging type

No response

Windows version

Windows 10 version 22H2 (19045, 2022 Update)

IDE

No response

Additional context

No response

[DHancock]

Similar to #3602 ?

[KarelChanivecky]

Maybe similar, however, in my case I could not install the package in a freshly configured machine.

[pratikone]

A more accurate way to identify which all windows app runtime packages is by launching powershell in admin mode and running :
Get-AppxPackage -allusers *windowsappruntime*.

Could you do it and print its output here so that we can see what all is installed.

[KarelChanivecky]

Sorry I didn't answer sooner, I seem to have missed the notification....

I am question whether I am schizophrenic, but we just ran into a hitch with another installer and suddenly we can no longer reproduce.

After the first incident I mention, we ended up using the following URL:
https://aka.ms/windowsappsdk/1.4/1.4.230822000/windowsappruntimeinstall-x64.exe

This worked fine for a few months, but last week someone tried installing our app and the GUI wouldn't work with the missing SDK message. We were able to reproduce in our lab. The output of running that installer at first was:

Installing license: MSIX_MAINPACKAGE_LICENSE
Install License result : 0x0
Installing license: MSIX_SINGLETONPACKAGE_LICENSE
Install License result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Main.1.4_4000.964.11.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0

I was following pratikone's suggestion. However, I saw that there was a bunch of runtimes installed, including some for 1.4 which we were using, so I figured I would uninstall as many as I can to have a cleaner baseline to compare. After I try installing the runtime again, now the output was :

Installing license: MSIX_MAINPACKAGE_LICENSE
Install License result : 0x0
Installing license: MSIX_SINGLETONPACKAGE_LICENSE
Install License result : 0x0
Deploying package: Microsoft.WindowsAppRuntime.1.4_4000.964.11.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Deploying package: Microsoft.WindowsAppRuntime.1.4_4000.964.11.0_x86__8wekyb3d8bbwe
Package deployment result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Main.1.4_4000.964.11.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Singleton_4000.964.11.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: Microsoft.WinAppRuntime.DDLM.4000.964.11.0-x6_4000.964.11.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: Microsoft.WinAppRuntime.DDLM.4000.964.11.0-x8_4000.964.11.0_x86__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
All install operations successful.

This is what there was before:

Name : Microsoft.WindowsAppRuntime.CBS
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X64
ResourceId :
Version : 4000.1027.2341.0
PackageFullName : Microsoft.WindowsAppRuntime.CBS_4000.1027.2341.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Windows\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe
IsFramework : True
PackageFamilyName : Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-21-35964174-2226005752-1563118556-1001 [fgt]: Installed, S-1-5-18 [S-1-5-18]: Installed}
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : True
IsPartiallyStaged : False
SignatureKind : System
Status : Ok

Name : Microsoft.WindowsAppRuntime.1.4
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X64
ResourceId :
Version : 4000.1049.117.0
PackageFullName : Microsoft.WindowsAppRuntime.1.4_4000.1049.117.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.4_4000.1049.117.0_x64__8wekyb3d8bbwe
IsFramework : True
PackageFamilyName : Microsoft.WindowsAppRuntime.1.4_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-21-35964174-2226005752-1563118556-1001 [fgt]: Installed}
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
IsPartiallyStaged : False
SignatureKind : Store
Status : Ok

Name : Microsoft.WindowsAppRuntime.1.4
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X86 ResourceId : Version : 4000.1049.117.0 PackageFullName : Microsoft.WindowsAppRuntime.1.4_4000.1049.117.0_x86__8wekyb3d8bbwe InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.4_4000.1049.117.0_x86__8wekyb3d8bbwe IsFramework : True PackageFamilyName : Microsoft.WindowsAppRuntime.1.4_8wekyb3d8bbwe PublisherId : 8wekyb3d8bbwe PackageUserInformation : {S-1-5-21-35964174-2226005752-1563118556-1001 [fgt]: Installed} IsResourcePackage : False IsBundle : False IsDevelopmentMode : False NonRemovable : False IsPartiallyStaged : False SignatureKind : Store
Status : Ok
Name : Microsoft.WindowsAppRuntime.1.3 Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : X64 ResourceId : Version : 3000.934.1904.0
PackageFullName : Microsoft.WindowsAppRuntime.1.3_3000.934.1904.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.3_3000.934.1904.0_x64__8wekyb3d8bbwe
IsFramework : True
PackageFamilyName : Microsoft.WindowsAppRuntime.1.3_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-21-35964174-2226005752-1563118556-1001 [fgt]: Installed}
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
IsPartiallyStaged : False
SignatureKind : Store
Status : Ok

Name : Microsoft.WindowsAppRuntime.1.3
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X86
ResourceId :
Version : 3000.934.1904.0
PackageFullName : Microsoft.WindowsAppRuntime.1.3_3000.934.1904.0_x86__8wekyb3d8bbwe
InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.3_3000.934.1904.0_x86__8wekyb3d8bbwe
IsFramework : True
PackageFamilyName : Microsoft.WindowsAppRuntime.1.3_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-21-35964174-2226005752-1563118556-1001 [fgt]: Installed}
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
IsPartiallyStaged : False
SignatureKind : Store
Status : Ok

I could almost guarantee that the DDLMs were not shown in the "remove/add programs" settings page at the time that the get-appxpackage output above was collected.

After the installer was working again, I wondered if it the issue could have been caused by Microsoft.WindowsAppRuntime.1.4_4000.1049.117.0_x64__8wekyb3d8bbwe being already present, which seems to be a later version. I downloaded both the version we were using, and the latest. Installed the latest, then installed ours and the result was that both were now available.

I would really like to understand how to have this installation done more reliably. Our app is distributed unpackaged. It actually is just a platform specific GUI that we swap into a cross-platform application. We assess if the SDKs are available in the machine, and download and install if necessary. I would appreciate any deployment suggestions if this is not an optimal solution.

[SuinegXY]

@DrusTheAxe
this problem is still exist.
when i install v1.5 first and install v1.4 next,
the ddlm 1.4 is not installed still.

for the result, my unpackaged app can't start,
it notice that
"This application requires the Windows App Runtime"
"Version 1.4"
"(MSIX package version >= 4000.964.11.0)"

if delete the mark WindowsPackageType,
it will return 0x80070491 when call MddBootstrapInitialize

[pratikone]

Thanks for posting an update. We have fixed some of these issues with 1.4.3 onwards so it is understandable some of the issue is gone. There seem to be more remaining and I will be investigating it.
Thanks for posting the output.

Also, my bad. we have different spellings for different packages 😔. Actual package is WindowsAppRuntime. Main and DDLM packages are WinAppRuntime.

Get-AppxPackage -allusers *win*appruntime* will return everything including DDLM entries.

Meanwhile I will try @SuinegXY 's steps.

[SuinegXY]

I tried the V1.4.5, and the problem was still exist,
I installed the V1.5.1 first, and installed the V1.4.5 next.
The V1.4 App can't start

I used the command powershell (get-appxpackage micro*win*appruntime*).packagefullname
The output was

C:\Users\WDAGUtilityAccount>powershell (get-appxpackage micro*win*appruntime*).packagefullname
Microsoft.WindowsAppRuntime.CBS_4000.1027.2341.0_x64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.5_5001.70.1338.0_x64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.5_5001.70.1338.0_x86__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Main.1.5_5001.70.1338.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.5001.70.1338.0-x6_5001.70.1338.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.5001.70.1338.0-x8_5001.70.1338.0_x86__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.4_4000.1136.2333.0_x64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.4_4000.1136.2333.0_x86__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Main.1.4_4000.1136.2333.0_x64__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Singleton_5001.70.1338.0_x64__8wekyb3d8bbwe

[KarelChanivecky]

FYI this also happens when using winget:

[legistek]

So what's the solution? Trying to install this on a Windows Server build server and it won't install.

[DrusTheAxe]

Get-AppxPackage -allusers windowsappruntime

BTW WinAppSDK's package Names vary (quite a bit) so that filter won't catch them all. For future reference this is a better filter

Get-AppxPackage -allusers micro*win*app*run*