When items require elevated privileges, shims will raise UAC prompts.
Runs the target executable where it is, which means all dependencies and other things used are all in the original location.
Provides an exe file that calls a target executable.
These are the benefits of creating a shim: This also allows applications and tools to be on the "PATH" without cluttering up the PATH environment variable. We like to call this "batch redirection that works". It can also work to simply call the actual binary when it shims GUI applications. It's a form of redirection, where you create a "shim" that redirects input to the actual binary process and shares the output. Shimming is like symlinking, but it works much better.