Hi @Tom Apperson ,
I went through the published documentation for the APIs you mentioned, and none of them covers the full window from verification to first-image mapping. Below are the answers to each of your questions.
1. Can a supported API bind activation to exact PackageFullName A and Application ID?
No such API is documented. IApplicationActivationManager::ActivateApplication accepts only an AUMID, arguments, and activation options. It has no PackageFullName parameter. AppListEntry.LaunchAsync takes no parameters and launches the app as if the user selected its app list entry. An AUMID is built from the package family name and the Application ID, and it is documented as independent of package version and architecture. It therefore can't identify package A specifically. None of these pages documents which image is mapped first.
2. Is there a supported lock, lease, or reference that keeps version selection stable?
No documented mechanism provides this guarantee. FindPackageForUser returns information about package A, but its documentation describes no lock on registration. The dynamic dependency API is the closest documented reference mechanism, but it doesn't fit this scenario:
Its criteria are package family, minimum version, and architecture. The page states that a specific package can't be specified and that the highest matching version is selected.
On Windows 11, a main package can be targeted only if it opts in with uap15:DependencyTarget.
AddPackageDependency adds the resolved package to the calling process's package graph so that process can use its content and activate its types. Older versions are serviced side by side while the reference is held. Nothing documents this reference controlling a separate AUMID activation.
Because no such mechanism is documented, there are no lifetime rules to cite for it.
3. If B replaces A before AUMID activation, is the result A, B, failure, or unspecified?
The reviewed documentation doesn't specify this. The activation APIs never receive A's identity, and no document defines an atomic interval from verification through activation selection and first-image mapping. The outcome should be treated as unspecified by the published contracts. Don't rely on any particular result.
4. Explicit statement
Based on the documentation reviewed, no published Microsoft documentation establishes a supported guarantee that only the executable from exact package A will be the first private image mapped after verification.
Public documentation can't provide an authoritative determination from the Windows/MSIX activation team. If your design depends on one, please contact https://developer.microsoft.com/en-us/windows/support to request a formal determination.
Hope this clarifies the documented boundaries. If you found this helpful, you can refer to this guidance to confirm it and help others with similar questions.
Thank you.