UWP URI Protocol Activation (Scheme URL)

Describe the bug
I can't seem to be able to launch QuickView from my own custom file manager as described here when using the Windows Store installation.

To Reproduce
Steps to reproduce the behavior:

1. Use Windows Store Installation
2. Open CMD
3. Try start QuickLook.exe (or with any prams)
4. See Error The system cannot find the file QuickLook.exe
5. Try cd "C:\Program Files\WindowsApps\21090PaddyXu.QuickLook_3.6.4.0_neutral__egxr34yet59cg\Package" (where the executable is stored)
6. See Access Denied Error (thanks UWP)
7. Try start "C:\Program Files\WindowsApps\21090PaddyXu.QuickLook_3.6.4.0_neutral__egxr34yet59cg\Package\QuickLook.exe"
8. CMD can't find anything and falls back to opening a new command line

Running as admin doesn't seem to help either.

Expected behavior
I don't know how easy it is to include UWP features/code: a possible solution for this is to create a URI activation 'hook': then it could be launched with something like quicklook://"C:\Users\andrew\Desktop\panels.log". You might have to encode/decode that: not sure if it likes \.

See this article for more information on handling a uri activation.

I think that solution might be a bit clunky: It seem to be the solution taken by all other UWP apps including Microsoft's own. I am not super familiar with the code of your app. It really depends if you are adding any extra UWP code already. In fact it might be easier to create a similar uri 'hook' from your 'traditional' app on install/started or whatever.

Alternatively I could bundle QuickLook with my file manager: but this brings about many issues like licensing/updates/any settings that might be introduced in the future etc.

Thanks,
Andrew Mitchell

Desktop:

• OS Version: Windows 10 Pro 10.0.17134
• QuickLook Version: 3.6.4

Start by reproducing the CMD launch failure with the Windows Store installation, then read the linked Integration and Development wiki page and Microsoft's URI activation article. Identify the Store package's activation entry point and determine how a quicklook:// URI should carry the requested file path. Done means a custom file manager can launch QuickLook through that URI and open the specified file.