Repository navigation
Cannot register AppNotification callback without installing Runtime package for Self-Contained Unpackaged app #6071
Description
Describe the bug
AppNotificationManager.Default.NotificationInvoked += NotificationInvoked;
AppNotificationManager.Default.Register();Register() throws an Exception:
System.Runtime.InteropServices.COMException: 'The specified module could not be found.
Unable to load resource dll. Microsoft.WindowsAppRuntime.Insights.Resource.dll'
in Self-Contained app.
Steps to reproduce the bug
- Create Unpackaged Self-Contained App with Microsoft.WindowsAppSDK.WinUI installed only. Don't use metapackage.
- Execute AppNotification callback registration on startup
Expected behavior
Callback registration success without installing Runtime package for Self-Contained app.
Screenshots
No response
NuGet package version
Windows App SDK 1.8.6
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.26100.7705" />
<PackageReference Include="Microsoft.WindowsAppSDK.WinUI" Version="1.8.260224000" />Packaging type
Unpackaged
Windows version
Windows 11 version 24H2 (26100, June 2025 Update)
IDE
Visual Studio 2026
(please update Bug template here in GitHub, add VS 2026 there to the droptown selector)
Additional context
If I install Microsoft.WindowsAppSDK.Runtime package, then it works as expected but as far as I know, that package is not required for Self-Contained apps.
Reacted by kc-nr, torum, Herve Eruam, Maya Rose, Dominic Maas, s-inage and Elijah Lopez
Activity
DominicMaas commentedon May 22, 2026
Still hitting this in 2.1
fix: lay out Insights.Resource.dll for self-contained notifications
feat: Devices app chips, close/terminate, undo, and card options (#44)
fix: native toasts work again on installed builds (ship missing Insig…
ci: disable semantic-release issue/PR commenting
fix: codexコマンド未検出とトースト通知警告文言の誤りを修正する (#178)
elibroftw commentedon Jul 21, 2026
Still hitting this in 2.3.1
elibroftw commentedon Jul 22, 2026
For some reason I can simply catch the exception when unpackaged to let the app not crash, and I still end up seeing notifications. Thankfully the app is packaged with external location in the installer. I just wanted to do some light testing.
Windows App SDK vorerst auf 1.8 statt 2.3.1 — in 2.x sind die Toasts …
Sicherheits-Release v1.4.0: WebView-Token-Gating, verifizierter Insta…
dancing-groot commentedon Aug 26, 2026
Confirm still broken on version 2.4.0
build: ship the Windows App SDK Insights resource dll in every self-c…
build: ship the Windows App SDK Insights resource dll in every self-c…
build: ship the Windows App SDK Insights resource dll in every self-c…
torum commentedon Sep 17, 2026
WinAppSDK 2.5.1
Still broken.
aepot commentedon Sep 18, 2026
torum I guess 2.5.1 doesn't include this fix at all. No mention in release notes.
GenerAhl commentedon Sep 18, 2026
This still reproduces on 2.5.1 with a minimal self-contained repro, even though #6725 is in the v2.5.1 tag. Details and repro are in #6774.
manodasanW commentedon Sep 18, 2026
Fix isn't the release branch yet, it will be soon. I will look into the issue with the tags.
Use Windows App SDK v1.8.26 instead of v2.5.1 due to the long standin…
chore(deps): update dependency microsoft.windowsappsdk to 2.6.4 (#25)
Update Windows App SDK to 2.6.4 (#30)