Fix: Fixed an issue where arguments weren’t passed when running shortcuts as admin

[yaira2]

Resolved / Related Issues

To prevent extra work, all changes to the Files codebase must link to an approved issue marked as Ready to build. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.

• Closes Bug: Shortcut set to run as Admin doesn't work if there are arguments #15595

Steps used to test these changes

Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.

1. Followed the repro steps outlined in issue Bug: Shortcut set to run as Admin doesn't work if there are arguments #15595.
2. Verified that arguments are correctly passed in both scenarios: when the shortcut is configured to run as an administrator and when it is not.

[yaira2]

In the long run, we should modify HandleApplicationLaunch to handle this correctly. It the meantime, I think this is a good workaround to avoid a refactor.

[0x5bfa]

In the long run, we should modify HandleApplicationLaunch to handle this correctly. It the meantime, I think this is a good workaround to avoid a refactor.

Could you add a NOTE comment saying this, so I (or someone) can notice?

[gave92]

I'd probably go with the refactor route, it's not that bad, see here:
https://github.com/gave92/files-uwp/tree/rev_adminargs

If you prefer the current solution, make sure to remove "process.WaitForExit();" and to wrap in a try-catch in case user says no to UAC, like:
cfb1af0

[yaira2]

I'd probably go with the refactor route, it's not that bad, see here: https://github.com/gave92/files-uwp/tree/rev_adminargs

If you prefer the current solution, make sure to remove "process.WaitForExit();" and to wrap in a try-catch in case user says no to UAC, like: cfb1af0

Your way is fine with me, can you open a PR?