desktop:ExecutionAlias declared in Package.appxmanifest not working on Windows Server 2019

[HO-COOH]

Describe the bug

A few users of my app reported that they cannot launch my app on their Windows Server. After some digging, I found on normal Windows 10/11, if the app declares an desktop:ExecutionAlias, it will create an entry in %localappdata%\Microsoft\WindowsApps\. But the folder is empty on Windows Server (2019 17763, to be specific).

I am not sure whether this issue happens to all Windows Server version. But on 17763, I write a demo to test that and it's 100% reproducible.

Steps to reproduce the bug

1. Create a new WinUI3 C++ project, packaged
2. Add this under the Application node in Package.appxmanifest

        <Extensions>
            <uap3:Extension Category="windows.appExecutionAlias" Executable="_22_ExecutionAliasNotFound_WinUI.exe" EntryPoint="Windows.FullTrustApplication">
                <uap3:AppExecutionAlias>
                    <desktop:ExecutionAlias Alias="winuiBugTest.exe"/>
                </uap3:AppExecutionAlias>
            </uap3:Extension>
        </Extensions>

3. Build a msix package, deploy on Windows Server. Run winuiBugTest.exe, and it will report the file is not found.

Expected behavior

The app should run

Screenshots

NuGet package version

Windows App SDK 1.6.3: 1.6.241114003

Packaging type

Packaged (MSIX)

Windows version

No response

IDE

Visual Studio 2022

Additional context

Using uap5 also does not work. And I don't even know what are the differences

            <uap5:Extension Category="windows.appExecutionAlias" Executable="_22_ExecutionAliasNotFound_WinUI.exe" EntryPoint="Windows.FullTrustApplication">
                <uap5:AppExecutionAlias>
                    <uap5:ExecutionAlias Alias="winuiBugTest.exe"/>
                </uap5:AppExecutionAlias>
            </uap5:Extension>

repro