Could elevation work on windows 10 with self-contained WASDK?

[roxk]

Quoting from this discussion:

actually WinUI 3 in packaged apps also does NOT support elevation. It's an OS-level issue, COM/WinRT doesn't allow per-user class registrations to be activated from an elevated process. Inbox APIs work when elevated, but WinAppSDK isn't inbox. We've fixed that in the OS in the next release.

And according to 1.1-preview1's discussion, it seems it is decided that WASDK 1.1 will not support elevation on windows 10.

I noticed that terminal is able to support elevation by using SxS manifest. Couldn't WASDK at least support elevation on windows 10 for self-contained deployment? Self-contained WASDK already needs SxS for RegFreeWinRT anyways.

I have high hope for WASDK and I'm afraid the down-level/polyfill promises failing one after another would hurt its reputation. Hope this can start some discussion on potential solutions that can bring elevation support to windows 10.

---

Is there any plan to bring the fixes for WinRT/COM activation from elevated process (which is already in windows 11) to future windows 10 update, e.g. 22H1/22H2? This would allow packaged app to have elevation support in windows 10 as well.

[roxk]

Sorry for self-pushing, but the thing that I was afraid of is showing up already: see this tweet complaining about how WASDK broke the down-level poly-fill promise. Is there any plan regarding elevation support on windows 10? Even just SxS like how terminal achieved elevation with custom WinRT component? This is currently biting power toys apparently.

@DrusTheAxe Not sure if it's appropriate to ping directly but here I'm pinging, as IMO this is very urgent (affecting power toy) and any kind of reply is appreciated. Thanks!

[AdamBraden]

Elevated support for COM & WinRT has a lot of implementation nuances when it comes to enabling downlevel to RS5, and to support MSIX packaged apps, unpackaged apps, and self-contained apps. The SxS manifest is only a partial solution. The support in 1.1 is to reconcile that across all scenarios.

However there is a detail we couldn't solve in the WinAppSDK and that requires an OS servicing update. Those OS updates are available for download at these links. They will be part of the next patch Tuesday and thus be broadly available for your customers soon:

• Windows 11 - April 25, 2022—KB5012643 (OS Build 22000.652) Preview

• Windows 10 - April 25, 2022—KB5011831 (OS Builds 19042.1682, 19043.1682, and 19044.1682) Preview

• Note that the OS fix for RS5 is still pending and will come in a future update.