UpdateTask doesn't run when app/package is updated from UWP/desktopBridge to WindowsAppSdk

Describe the bug

I have a UWP/DesktopBridge app (in Microsoft Store) that I am migrating to use WindowsAppSDK Desktop.
When the UWP app is installed (e.g. v1.2.47) on my system and I then deploy the WindowsAppSDK version (e.g. v2.1.0) I don't see the windows.updateTask process (defined in the manifest) being executed.

If I then later do an update of the newly deployed package, e.g. from v2.1.0 to v2.1.1, the UpdateTask does get executed.

The problem is that I want to execute some update code that is related with the migration to WindowsAppSDK and I wan't this to happen in the background.

The update code is required since the 'old' UWP version is using a inproc timer background task which should keep on running when the package is updated. In WindowsAppSDK Desktop the timer background task must be OOP. After the update the background processes apparently have to be re-registered and I want this to happen without user intervention.

Steps to reproduce the bug

Create UWP app and deploy.
Create WindowsAppSDK app with the same package ID's, a UpdateTask and a different version number, and deploy.

Expected behavior

UpdateTask should run.

Screenshots

No response

NuGet package version

1.1.5

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

Visual Studio 2022

Additional context

No response

Start by reproducing the packaged MSIX migration from the UWP/DesktopBridge version to the WindowsAppSDK Desktop version on Windows 11 22H2, using the manifest-defined UpdateTask. Compare that migration with a later package update and verify the task's execution. Done means UpdateTask runs during the migration so background processes can be re-registered without user intervention.