How to Access Maguuma Without Doing the Story Again

When started, many programs require permission top (shield on the app icon), but actually they don't need the administrator privileges for their normal operation. For example, you can manually grant permissions for your users on the app binder in the ProgramFiles and/or registry keys used past the program. So when starting such a programme under not-admin user account, a UAC prompt will announced and the user volition be required to enter an ambassador password (if User Business relationship Control is enabled on the computer). To featherbed this machinery, many users simple disable UAC or grant admin privileges to a user past calculation a user account to the local grouping "Administrators". Of class, both methods are not safe.

Contents:

• Why some Windows apps not run under standard users and require administrator permissions?
• How to run a program that requires admin privileges under standard user?
• How to Bypass UAC with RunAsInvoker in __COMPAT_LAYER?
• Enable RunAsInvoker Manner in the EXE File Manifest

Why some Windows apps non run under standard users and require administrator permissions?

An app may demand the administrator privileges to modify some files (logs, configs, etc.) in its own folder in the C:\Program Files (x86)\SomeApp. By default, users don't take edit (write and alter) permissions on this directory. In club this program to work normally, the administrator permissions are required. To solve this problem, you have to manually grant the alter and/or write permission for a user (or the built-in Users group) on the app folder at the NTFS file organisation level.

Note. Actually, it is not recommended to shop the changing application information in its own folder under C:\Program Files. Information technology's better to store the app information in the user profile. But information technology is a question of laziness and incompetence of the app developers.

How to run a programme that requires admin privileges under standard user?

Earlier we described how to disable a UAC prompt for the certain app using RunAsInvoker parameter. Notwithstanding, this method is not flexible enough.

Y'all tin also use RunAs with the saved administrator password (in the Windows Credentials Manager) using the /SAVECRED option. It is as well insecure because the user can use the saved ambassador credentials password to run whatever program on this computer.

Allow's consider an easier way to force any program to run without ambassador privileges (without inbound the admin password) and with UAC enabled (Level four, 3 or 2 of the UAC slider).

Let's take the Registry Editor as an case — regedit.exe (it is located in the C:\Windows\ folder). Notice the UAC shield side by side to the app icon. This icon means that elevation of privileges via UAC volition be requested to run this program.

If you lot run regedit.exe, you volition come across a User Account Control window asking for the administrator credentials (Do you want to allow this app to make changes to your device?). If you practise non provide a password and practise not confirm meridian, the app won't start.

Allow'due south try to featherbed the UAC asking for this program. Create the text file run-equally-non-admin.bat containing the post-obit code on your Desktop:

cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start "" %one"

To force the regedit.exe to run without the administrator privileges and to suppress the UAC prompt, uncomplicated drag the EXE file y'all want to start to this BAT file on the desktop.

Then the Registry Editor should first without a UAC prompt and without entering an administrator password. If you open the Task Manager and add the Elevated cavalcade, you lot volition see that there is the regedit.exe process without the elevated status (run with non-admin user permissions).

Try to edit any parameter in the HKEY_LOCAL_MACHINE registry hive. Equally you tin can run into, a user cannot edit the item in this registry fundamental (the user doesn't have write permissions to the system registry keys). But y'all can add or edit registry keys and parameters in your user hive — HKEY_CURRENT_USER.

In the aforementioned style y'all tin run any app using the BAT file. Simply specify the path to the executable file.

run-app-as-non-admin.bat
Set ApplicationPath="C:\Program Files\SomeApp\testapp.exe"
cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start "" %ApplicationPath%"

Y'all can also add together a context menu that allows to run all apps without elevation. To do it, create the RunAsUser.REG file, copy the following lawmaking into it, save and import it into the Windows registry by double clicking on the reg file (you will need ambassador permissions to use this alter).

Windows Registry Editor Version v.00 [HKEY_CLASSES_ROOT\*\shell\forcerunasinvoker] @="Run as user without UAC privilege pinnacle" [HKEY_CLASSES_ROOT\*\crush\forcerunasinvoker\command] @="cmd /min /C \"set __COMPAT_LAYER=RUNASINVOKER && start \"\" \"%1\"\""

After that, to run any application without the administrator privileges, merely select "Run as user without UAC privilege elevation" in the context carte du jour of File Explorer.

Let me remind yous again that using the programme in the RUNASINVOKER mode won't allow you to elevate the plan. The RunAsInvoker suppresses UAC prompt and tells the program that information technology should run with the permissions of the current user, and non ask for pinnacle of privileges. If a program really needs elevated privileges to edit arrangement settings or files, it won't work or volition inquire for admin permissions again.

How to Featherbed UAC with RunAsInvoker in __COMPAT_LAYER?

The environment variable __COMPAT_LAYER allows you lot to set different compatibility levels for the applications (the Compatibility tab in the properties of an EXE file). Using this variable, you tin can specify the compatibility settings to be used when starting a programme. For case, to start an app in Windows 8 compatibility way and 640×480 resolution, set the following:

set __COMPAT_LAYER=Win8RTM 640x480

The __COMPAT_LAYER variable has some options nosotros are interested in. There are the following parameters:

• RunAsInvoker – run an app with the privileges of a parent process without the UAC prompt;
• RunAsHighest – run a plan with the highest-level permission bachelor to the user (the UAC prompt will appear if a user has the administrator privileges);
• RunAsAdmin – run an app as administrator (the UAC prompt appears each time).

It means that the RunAsInvoker parameter doesn't provide the administrator permissions, but just suppresses the UAC prompt.

The following CMD lawmaking enables the RunAsInvoker mode for the current process and runs the specified program without height:

gear up __COMPAT_LAYER=RUNASINVOKER
kickoff "" "C:\Program Files\MyApp\testapp.exe"

Enable RunAsInvoker Fashion in the EXE File Manifest

As we said above, Windows 10 displays a UAC shield icon for programs that require elevation to run. Developers gear up this requirement when compiling the application in the program manifest .

Y'all can edit the manifest of any exe file and disable the requirement to run the program in elevated mode.

To edit the plan manifest, you can use the free Resource Hacker tool. Open up the executable file of the app in Resource Hacker.

In the tree on the left, go to the Manifest section and open the program manifest. Pay attention to the following xml section:

<requestedPrivileges> <requestedExecutionLevel level="requireAdministrator" uiAccess="false"/> </requestedPrivileges>

Information technology is cheers to the requireAdministrator choice that Windows always tries to run this program equally an ambassador.

Modify requireAdministrator to asInvoker and the save changes in exe file.

Note that now the UAC shield has disappeared from the programme icon, and you can run it without asking for administrator password with the current user permissions.

If the executable app file is signed with MS Authenticode (Code Signing certificate), so after modifying the exe file, it may stop working or issue a warning.

In this case, yous can forcefulness the program to apply an external manifest file. Create a manifestly text file appname.exe.manifest (for case, Autologon.exe.manifest) in the directory with the exe file and copy the manifest code from Resource Hacker into it. Alter requireAdministrator to asInvoker. Relieve the manifest file.

To have Windows always try to utilise the external manifest file when launching exe files, enable a special registry parameter:

REG Add together "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v PreferExternalManifest /t REG_DWORD /d one /f

Restart Windows and make certain the program is using an external manifest file that says to run without administrator privileges.

ortizsobjecold1950.blogspot.com

Source: http://woshub.com/run-program-without-admin-password-and-bypass-uac-prompt/

Share this post