Windows runs desktops apps and application files (ex: .bat, .cmd, .exe, .msc, and .msi file types) in user mode by default without elevated administrator rights unless it prompts you withÂ UACÂ to run elevated.
Windows hasÂ standard userÂ andÂ administratorÂ types of user accounts.
Standard UserÂ – Standard user accounts are good for everyday usage, and can be a local account or Microsoft account. Standard user accounts can use most apps and change system settings that do not affect other users. If any action that requires elevated rights is attempted while signed in as a standard user, Windows will display aÂ UACÂ prompt for the password of an administrator for approval. IfÂ UACÂ is set to “Never notify”, then a standard user will automatically be denied the elevated action.
AdministratorÂ – Administrator accounts have complete access to the PC and can make any desired changes. Administrators can be a local account or Microsoft account. If any action that requires elevated rights is attempted while signed in as an administrator, Windows will display aÂ UACÂ prompt for the administrator to confirm (Yes or No) using full administrator rights.
When you useÂ Run as administratorÂ on a desktop app or application file, you are allowing it to run with full administrator access to everything on the computer. This means you are giving it special permissions to access restricted parts of the computer that would otherwise be off-limits. This could be a potential security risk if not a trusted app or application file, but sometimes “Run as administrator” is necessary for a trusted app or application file to run properly if it requires elevated rights for full access.
This tutorial will show you different ways to have a desktop app or application fileÂ Run as administratorÂ with elevated rights in Windows 11.