The error message “This app can’t be activated by the built-in administrator” typically occurs in Windows when trying to open certain apps with the built-in Administrator account, which has higher privileges than standard user accounts. This issue arises because certain Windows Store apps, such as Mail or Edge, require running in a standard environment, which the built-in Administrator account does not provide. To resolve this, users need to either disable the built-in administrator account, create a new administrator account with normal privileges, or modify system settings to allow apps to run under the built-in administrator account. Below are several methods and approaches to fixing this issue.
Create a New Local Administrator Account
The most effective solution is to create a new local administrator account and use it instead of the built-in administrator account. This account will have the necessary privileges to run apps without triggering the error. To do this, go to Settings > Accounts > Family & other users and add a new user. Assign administrative rights to this new user by selecting "Administrator" in the account type. Once created, log out from the built-in administrator and log in with this new account. This method ensures that all apps will run without restrictions and without triggering the activation error.
Disable Built-in Administrator via Command Prompt
Another method to resolve this issue is to disable the built-in administrator account altogether, as it is not generally necessary for daily use. To do this, open the Command Prompt as an administrator and type the command: net user administrator /active:no. This will deactivate the built-in administrator account, forcing you to use a standard account that is not affected by this issue. After disabling the account, reboot your computer and log in with another user account. By using a regular administrator account, you eliminate the error message while still maintaining full system control.
Enable User Account Control (UAC) for Built-in Administrator
If you prefer to keep using the built-in administrator account but still want to activate apps, enabling User Account Control (UAC) might help. UAC is designed to prevent unauthorized changes to the system, but it can also allow apps to function correctly. To enable UAC for the built-in administrator, open the Local Group Policy Editor (type gpedit.msc in the search bar), navigate to Security Settings > Local Policies > Security Options, and find the setting User Account Control: Admin Approval Mode for the Built-in Administrator account. Enable this option, then reboot the computer. This step allows apps to be launched from the built-in administrator without errors.
Adjust Local Security Policy
The local security policy can be adjusted to allow apps to run under the built-in administrator account. To do this, open the Local Security Policy editor by typing secpol.msc in the Start menu search bar. Navigate to Local Policies > Security Options, and locate User Account Control: Run all administrators in Admin Approval Mode. Set this policy to "Enabled." This will apply additional security to the built-in administrator account, making it more compatible with modern apps that require user-level execution privileges. After applying the setting, reboot your computer for changes to take effect.
Use Windows PowerShell to Manage the Administrator Account
Windows PowerShell provides a powerful tool for managing user accounts and permissions. To resolve the activation error, you can use PowerShell to disable or modify the built-in administrator account. Open PowerShell as an administrator and run the command Disable-LocalUser -Name "Administrator". This disables the built-in administrator account. If you want to keep it active but modify its settings, you can use Set-LocalUser -Name "Administrator" -AccountNeverExpires $true to adjust account policies, allowing you more flexibility in how apps are activated under this account.
Enable Activation for Specific Apps via Group Policy Editor
If the issue is isolated to specific apps, you can use the Group Policy Editor to allow them to run for the built-in administrator. Open the Group Policy Editor (gpedit.msc) and navigate to Computer Configuration > Administrative Templates > Windows Components > App Package Deployment. Look for the setting Allow deployment operations in special profiles and enable it. This policy change allows Windows Store apps and other similar programs to run in special profiles, like the built-in administrator, without restrictions. After enabling this setting, try launching the affected apps again to see if the error is resolved.
Use Compatibility Mode for Affected Apps
In some cases, you can resolve the issue by running the app in compatibility mode. Right-click on the app’s icon and select Properties. Under the Compatibility tab, check the box that says "Run this program in compatibility mode for" and choose an earlier version of Windows. This can sometimes bypass the restrictions associated with the built-in administrator account. Compatibility mode tricks the system into thinking the app is running under a standard user profile, which can prevent the error from occurring. This method is particularly useful for older or legacy apps that might conflict with modern Windows security policies.
Modify the Registry for Enhanced Privileges
For users comfortable with advanced settings, modifying the Windows Registry can offer a solution. Press Windows + R, type regedit, and navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > Policies > System. Look for the key called EnableLUA and set its value to 1 if it’s currently set to 0. This enables User Account Control across all profiles, including the built-in administrator, and allows apps to activate without issue. Always back up your registry before making any changes to avoid accidental system damage.
Reinstall or Reset Problematic Apps
If the issue persists with a specific app, it may be necessary to reinstall or reset the app. Open Settings > Apps > Apps & Features, locate the problematic app, and select either Reset or Uninstall. Reinstalling or resetting an app clears any corrupted settings or files that may be causing the activation issue. Once reinstalled, launch the app to see if the error still appears. This method is particularly effective when the problem is isolated to just one or two apps and is not related to the system-wide administrator settings.
Check for Windows Updates
Keeping Windows up to date is essential for ensuring compatibility with apps and system settings. Sometimes, bugs or security updates can resolve the “This app can’t be activated by the built-in administrator” error. Go to Settings > Update & Security > Windows Update and check for available updates. Install any updates that are available, then restart your computer. In many cases, Microsoft releases patches that fix known compatibility issues, so regularly updating your system can prevent errors from occurring in the first place. Keeping your operating system and apps updated is a preventive measure that minimizes activation errors and enhances overall system performance.