Disable UAC for a specific program (Windows 10)

Question 1

On Windows 8.1, the following registry change allowed a user with Administrator privileges to launch a particular application without the User Access Control popup warning about changes being made to the computer:

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\path\\to\\app\MyApp.exe"="RunAsInvoker"

For example, to open Registry Editor or merge .reg files with the UAC prompt:

"C:\\Windows\\regedit.exe"="RunAsInvoker"

Can't get this to work on Windows 10 - the UAC prompt happens regardless. Is this possible on Windows 10?

Question 2

Use the Windows Task Scheduler to bypass the UAC prompt.

Instructions:

Open the Start Menu (or press the Windows Start key) and type "Task Scheduler". Press enter to open the Task Scheduler.
In Task Scheduler, right-click "Task Scheduler Library" and select "New Folder", and name it whatever you would like, perhaps something like "UAC Skipper".
Select the newly created folder, and right-click "Create Task" (not "Create Basic Task").
Name the task something descriptive, for example "My-App".
Enable the "Run with highest privileges" checkbox.
Under the "Configure for" dropdown menu, select "Windows 10" (Or whatever the present OS is).
Navigate to the "Actions" tab and click "New".
In the "Action" dropdown menu, select "Start a program".
Click Browse and locate your desired application .exe file.
Click the "Conditions" tab and deselect "Start the task only if the computer is on AC power."
On the desktop, right-click and select New > Shortcut.
In the text box, paste:

C:\Windows\System32\schtasks.exe /RUN /TN "Your-Task-Scheduler-Folder\Your-Task-Name"

This creates a link to your program that will automatically skip the prompt asking for permission to make changes to your computer.

Original source: Disabling UAC for a Specific App

Final note: This answer is based on an existing one which I found to be confusing and difficult to follow. Originally submitted as an edit, but that was rejected with the suggestion this should be posted as it's own answer.