Is Windows App SDK AppNotificationManager supported for an unpackaged native host?

Diogo Jorge Dias Pereria 20 Reputation points
2026-09-17T18:44:17.5666667+00:00

Hello,

I am an independent developer from Brazil working on a desktop software project.

The scope of this question is specifically related to a Python 3.14-based, unpackaged Windows process using PyWinRT/WinUI3 projections to access Windows Runtime APIs.

I would like to clarify the officially supported architecture for using Windows App SDK AppNotificationManager in this type of environment.

The scenario is:

  • An unpackaged Windows process runs outside of an MSIX package.

Windows App Runtime is initialized through the Bootstrap API.

The application uses Windows App SDK AppNotificationManager to register and display interactive Windows notifications.

The notification contains user-action buttons.

The application receives the corresponding NotificationInvoked callback and uses the user's action to control an operation in the host process.

The host process is not running as a packaged Windows application.

I have successfully validated the notification registration, notification display, interactive button invocation, and callback path in a development environment.

My question is:

Is this architecture officially supported and recommended for an unpackaged Windows application, or is there a different Microsoft-recommended architecture for using AppNotificationManager with an unpackaged host and receiving interactive notification actions back in that host?

I am particularly interested in understanding:

Whether AppNotificationManager is officially supported in this unpackaged scenario.

Whether the Bootstrap API is the recommended way to initialize the required Windows App Runtime components in this scenario.

Whether NotificationInvoked is the supported mechanism for returning the user's notification action to the unpackaged host process.

Whether there are any important package identity, registration, process lifetime, or deployment requirements that should be considered for production use.

I am intentionally not including proprietary source code or implementation details in this post. I can provide additional non-sensitive technical information if it would help clarify the scenario.

Thank you for your time and guidance.Hello,

Windows development | Windows App SDK
0 comments
Answer accepted by question author

AI answer

2026-09-17T18:44:45.3266667+00:00

Yes. AppNotificationManager is the recommended notifications API for new desktop apps, including unpackaged desktop apps such as Win32, WPF, and WinForms. For new development, Microsoft recommends AppNotificationManager rather than the older ToastNotificationManager, which is the UWP API and is maintenance-only.

For an unpackaged app that uses the Windows App SDK, initializing the Windows App SDK runtime through the bootstrapper is part of the supported deployment model. For apps packaged with external location or unpackaged, access to the Windows App SDK runtime must be initialized by using the Bootstrapper API.

NotificationInvoked is the supported callback mechanism for handling user interaction with app notifications. The documented pattern is to register the NotificationInvoked handler before calling Register(). For unpackaged apps, Register() automatically sets up the COM server registration that allows Windows to launch the app when a notification is clicked, so manual COM activation or AUMID configuration is not required in that model.

Important production considerations for this architecture:

  1. Package identity is not required for local app notifications using AppNotificationManager.
    • Local app notifications work in both packaged and unpackaged apps.
    • This matches the scenario described for interactive local notifications.
  2. Process lifetime matters for activation handling.
    • In the documented console app pattern, the app must remain running to receive activation callbacks when notifications are clicked.
  3. Elevated apps are not supported for app notifications.
    • Notifications for elevated (admin) apps are not currently supported.
  4. Deployment/runtime requirements still apply to unpackaged Windows App SDK apps.
    • The app developer is responsible for deploying the required Windows App SDK runtime packages to end users.
    • Unpackaged apps also need runtime initialization via the Bootstrapper API.
  5. Distinguish local app notifications from push notifications.
    • AppNotificationManager for local app notifications does not require package identity.
    • Push notifications are different: background delivery and COM activation for push require package identity in most production scenarios.

Based on the documented guidance, the architecture described is supported for local app notifications in an unpackaged host, with AppNotificationManager, bootstrapper-based runtime initialization, and NotificationInvoked for user actions. It is also the recommended direction for new desktop app development on Windows App SDK.

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Diogo Jorge Dias Pereria 20 Reputation points
    2026-09-17T19:09:27.95+00:00

    I appreciate the answer and the clarification. Thank you for the guidance.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.