What won't be included

[hfiref0x]

1. Everything based on user manipulations with program UI, shell dialogs, e.g. OpenDialog, SaveDialog from elevated application. This is not UAC bypass as it require massive user interactions with UI and target applications have High Integrity preventing GUI hacking. Consider everything like this as just a trash for social media hype. Example Module request - msdt.exe UAC bypass #28. The only exception to this is Forshaw method 55 as it provides an original way to circumvent UIPI and do the automation with minimum UI interactions.

2. "UAC bypasses" involving manual writing to HKEY_LOCAL_MACHINE. You either force this your own or this is exploit that needs to be patched.

3. UAC bypasses based on switching one DLL name to another while core method stay the same.
   E.g. https://github.com/Cn33liz/TpmInitUACAnniversaryBypass. The exception can only be made if the previous target is no longer work or this is used in ITW malware (e.g. various sysprep dll combinations, Pitou method).

4. Copy-paste "UAC bypasses" - that having no purpose except show off in twitter/any other social media, is when author takes something already known (not even his origin) and reinvents the wheel for public post, e.g. UAC bypass with Direct call to RAiLaunchAdminProcess and mmc #55

5. Everything patched by MS Bulletin as part of exploit patch with exception if it was previously used in malware. E.g. Sandworm method.

6. Methods that only work on Windows Server. This obviously do not make any sense.