Set winui app auto start will occure the explorer shell error

[hoshiizumiya]

Describe the bug

I use the Task Scheduler to manage the winui app to start as a admin or not. But I always meet the error when it is not "Run with highest privileges", which is used shell to start the winui app.
The most situation:

rare situation:

Tip: You can't just use the winui app exe path the same as the normal exe path under without admin, but you can with the admin.

Steps to reproduce the bug

The creation logic: https://github.com/SnapHutaoRemasteringProject/Snap.Hutao.Remastered.Native/blob/master/src/Snap.Hutao.Remastered.Native/HutaoNative.cpp#L35-L753
The app call:
https://github.com/SnapHutaoRemasteringProject/Snap.Hutao.Remastered/blob/main/src/Snap.Hutao.Remastered/Snap.Hutao.Remastered/ViewModel/Setting/SettingViewModel.cs

Expected behavior

No response

Screenshots

No response

NuGet package version

1.8.260317003

Packaging type

Packaged (MSIX)

Windows version

Insider Build (xxxxx)

IDE

No response

Additional context

What should I do?

[hoshiizumiya]

There is also a problem that how to delete it when uninstall.
Or should I use https://learn.microsoft.com/en-us/uwp/api/windows.applicationmodel.startuptask instead?
I want to know why it occure the explorer error.

[DrusTheAxe]

There is also a problem that how to delete it when uninstall. Or should I use https://learn.microsoft.com/en-us/uwp/api/windows.applicationmodel.startuptask instead? I want to know why it occure the explorer error.

windows.startupTask is recommended. Windows automatically launches them in packages registered to the user at logon, Windows knows how to clean up on uninstall and the user can control if a startup task should/not run @ logon via the contention Apps > Startup page in Settings.

By comparison, Scheduled Tasks aren't created by MSIX Deployment when you package is registered for a user, any you create at runtime aren't known to MSIX Deployment so they're not cleaned up at uninstall, and there's no convenient end-user control via Settings (the Task Scheduler GUI works, but I wouldn't call it convenient for end users).

P.S. If windows.startupTask doesn't quite scratch your itch and you really do need Scheduled Tasks please share your feedback on a possible future enhancement here => Proposal: MSIX manifested Scheduled Tasks #6415