Windows App Troubleshooter: Built-in Administrator Can’t Use Calculator
The error “this app can’t be opened using the Built-in Administrator account” is a common security feature in Windows. Modern apps, like the Calculator, are designed to run with standard user privileges, but the built-in Administrator account runs everything with elevated rights by default. This creates a conflict. Our troubleshooter will “calculate” the correct fix for your specific situation.
Interactive Solution Finder
Solution Success Rate
What is the ‘Built-in Administrator Can’t Use Calculator’ Error?
The “built in administrator cant use calculator” issue is a security measure, not a bug. In Windows, the built-in Administrator account is a special, high-privilege account. For security, Microsoft decided that this account should not run modern Universal Windows Platform (UWP) apps like the Calculator, Microsoft Edge, and Photos by default. This is because UWP apps are designed to run in a secure, sandboxed environment with limited permissions, a concept that clashes with the full, unrestricted power of the built-in Administrator. When you see this error, it means the security settings on your system are preventing these sandboxed apps from launching under the all-powerful administrator token.
The ‘Formula’ Behind the Fix
There is no mathematical formula, but there is a core logical principle: for a modern app to run, the user account must operate under User Account Control (UAC) in what’s called “Admin Approval Mode”. This mode creates two access tokens for an administrator: a standard user token for most tasks, and an elevated token that is only used when approved via a UAC prompt. The built-in Administrator account, by default, does not use this mode. The “fix” is to enable it.
The primary policy to change is: User Account Control: Admin Approval Mode for the Built-in Administrator account.
| Variable | Meaning | Unit / State | Typical Range |
|---|---|---|---|
| UAC Level | The sensitivity of User Account Control prompts. | State (Enabled/Disabled) | Slider from ‘Never Notify’ (Disabled) to ‘Always Notify’ (Enabled) |
| Admin Approval Mode | A security policy forcing the built-in admin to use UAC. | Policy (Enabled/Disabled) | Enabled, Disabled |
| App Type | The type of application being launched. | Type (Modern/Win32) | Calculator (Modern), Notepad (Win32) |
Practical Examples
Example 1: UAC is Disabled
A system administrator logs into the built-in Administrator account and discovers they can’t open the Calculator. They previously disabled User Account Control (UAC) by moving the slider to “Never Notify” to avoid prompts.
- Inputs: Windows 10, UAC Disabled, Policy Unknown.
- Diagnosis: UAC is disabled, preventing modern apps from running in their required sandboxed mode.
- Result: The troubleshooter advises enabling UAC by moving the slider up and restarting the PC. This is often the simplest fix for the **built in administrator cant use calculator** problem.
Example 2: Policy is Disabled on a Server
On a Windows Server 2019 machine, a user is using the enabled built-in Administrator account for maintenance. UAC is enabled, but they still cannot open modern apps.
- Inputs: Windows Server 2019, UAC Enabled, Policy Disabled.
- Diagnosis: The specific Group Policy for enabling Admin Approval Mode on the built-in account is turned off.
- Result: The troubleshooter provides the exact steps to open Local Security Policy (secpol.msc), navigate to ‘Security Options’, and enable “User Account Control: Admin Approval Mode for the Built-in Administrator account”. A restart is required. You can find more details on this in our guide to advanced security policies.
How to Use This Troubleshooter
Using this solution finder is a straightforward process designed to quickly diagnose why the **built in administrator cant use calculator**.
- Select Your OS: Start by choosing your correct Windows version from the first dropdown. The underlying policies can differ slightly.
- Specify UAC Status: In the second field, indicate whether you have User Account Control (UAC) enabled or disabled. If you’re unsure, assume it’s enabled unless you’ve explicitly turned it off. Our article on understanding user account control has more information.
- Policy Status: If you have previously tried to fix this and know the state of the “Admin Approval Mode” policy, select it. Otherwise, leave it as “I don’t know”.
- Interpret the Results: The tool will provide a direct, step-by-step solution. It will also offer a diagnosis, explaining the root cause based on your inputs. A restart is almost always required after applying the fix.
Key Factors That Affect Modern Apps for the Administrator
Several settings control the execution of modern apps for privileged accounts. Understanding them can help you solve the **built in administrator cant use calculator** error and prevent it from recurring.
- User Account Control (UAC): The master switch. If UAC is fully disabled, no user can run modern apps. It must be enabled.
- Admin Approval Mode Policy: This is the most crucial policy. It specifically forces the built-in Administrator to operate under the protection of UAC, which is disabled for that account by default.
- Registry Settings: The policy above corresponds to a registry key, usually `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken`. Manually changing this can be an alternative to using the policy editor. For guidance, see our article on editing the Windows registry safely.
- Windows Edition: Home editions of Windows do not include the Local Security Policy editor (secpol.msc), requiring a registry edit to fix the issue.
- Corrupted System Files: In rare cases, corrupted system files can prevent apps from launching. Running `sfc /scannow` in an elevated command prompt can help. Consider reading our system file checker guide.
- Corrupted User Profile: If the problem persists and is isolated to one account, the user profile itself might be corrupted. Creating a new admin account can resolve this.
Frequently Asked Questions (FAQ)
- 1. Why can’t the built-in administrator run modern apps by default?
- It’s a security feature. Modern (UWP) apps run in a low-privilege sandbox, while the built-in admin runs with maximum privilege. This conflict is resolved by preventing the apps from launching.
- 2. Is it safe to enable Admin Approval Mode for the administrator?
- Yes, it is the recommended and more secure configuration. It makes the built-in administrator behave like any other admin account, requiring UAC confirmation for elevated tasks.
- 3. What’s the difference between this and “Run all administrators in Admin Approval Mode”?
- The “Run all administrators…” policy applies to ALL members of the Administrators group. The “Admin Approval Mode for the Built-in Administrator account” policy applies ONLY to the specific, default ‘Administrator’ account (SID S-1-5-…-500).
- 4. Will editing the registry fix this calculator issue?
- Yes, enabling the `FilterAdministratorToken` registry value to `1` has the same effect as enabling the security policy. This is the required method for Windows Home editions.
- 5. Will this fix also allow other apps like Photos and Microsoft Edge to work?
- Yes. The issue is not specific to the Calculator. It affects all modern UWP apps, and the fix will resolve the problem for all of them simultaneously.
- 6. Can I just use a different administrator account?
- Yes. The recommended practice is to disable the built-in Administrator account and use a separate, personal account that is a member of the Administrators group. This type of account works with UAC and modern apps by default. Our guide on creating a new admin account can help.
- 7. Does the UAC slider level matter?
- As long as the slider is not on the bottom setting (“Never Notify”), UAC is considered enabled and the fix should work. The second-from-top level is the recommended default.
- 8. Is a restart always necessary?
- Yes. Changes to UAC policies and registry settings that control core security tokens are only applied after a full system reboot.