-
Notifications
You must be signed in to change notification settings - Fork 423
Description
Describe the bug
On a fresh virtual machine, if we use the WindowsAppSDKRuntime.exe --quiet (run as SYSTEM account / elevated)
After installing the installer, when we run
Get-AppxPackage -AllUsers | Where-Object Name -like "WindowsAppRuntime" | Select Name, Version, SignatureKind, PackageUserInformation
I can see
Name Version
Microsoft.WindowsAppRuntime.1.8 8000.770.947.0
for x86 and x64 packages
Windows App Runtime isn’t just one MSIX; it has multiple packages (Framework/Main/Singleton/DDLM)
When installing uses this installer, the Singleton.msix does not actually get provisoned.
"For unpackaged apps, WinAppSDK loads its runtime via framework MSIX packages / dynamic dependencies — those components must exist on the machine. Microsoft explicitly notes that PushNotificationManager depends on an additional Singleton package, and that this affects “self-contained” apps."
Our application is using PushNotificationManager under the Singleton package, and when we use the WindowsAppSDKRuntime.exe --quiet our code returns "Class not found"
When I do a dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:"...\Microsoft.WindowsAppRuntime.Singleton.1.8.msix" /SkipLicense then restart our software the error goes away.
Why is this important?
The installer when running WindowsAppSDKRuntime.exe --quiet should install required framework/dlls and should provision all 4 msix packages for ALL users on the machine
Steps to reproduce the bug
- Download WindowsAppSDKRuntime.exe
- Install using WindowsAppSDKRuntime.exe --quiet
- It doesn't not fully provision all 4 msix packages for all users under the hood
Actual behavior
No response
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
No response