Interactive Troubleshooter: Calculator Cannot Open in Built-in Administrator Account

Diagnose and fix the Windows error preventing modern apps from running in the elevated administrator account.

Diagnostic Tool

Recommended Solution

What is the “Calculator Cannot Open” Error?

The “calculator cannot open using the built-in administrator account” error is a security feature in Windows, not a bug. It primarily affects modern applications (Universal Windows Platform or UWP apps) like the Calculator, Photos, Microsoft Store, and Edge. This issue occurs because the built-in Administrator account runs with the highest possible privileges and, for security reasons, is isolated from running these sandboxed UWP apps by default. This preventative measure helps protect the system core from potentially vulnerable applications.

While any user can encounter issues with the calculator, this specific message is almost exclusively seen when logged into the literal, built-in “Administrator” account. A regular user account, even one with administrative privileges, typically does not face this problem unless User Account Control (UAC) has been completely disabled. Understanding this distinction is key to resolving the issue. For more details on UAC, see our guide on UAC settings explained.

The Root Cause: Security Policies Explained

The core of the problem lies in a specific security policy in Windows. There is no complex mathematical formula, but a logical switch that needs to be flipped. The policy in question is:

“User Account Control: Admin Approval Mode for the Built-in Administrator account”

By default, this policy is disabled. When disabled, it prevents the built-in administrator from launching most modern apps, leading to the error. Enabling it allows the system to handle the built-in admin account in a way that is compatible with UWP applications.

Policy States and Their Meaning

Policy State	Meaning	Typical Range of Impact
Disabled (Default)	Prevents modern apps (Calculator, Store, etc.) from running under the built-in Administrator account.	High security, but low compatibility for modern apps in this specific account.
Enabled	Allows the built-in Administrator account to run modern apps by placing it in “Admin Approval Mode”.	Slightly reduced security for this account, but enables full functionality.

Practical Examples

Example 1: System Administrator on a New Server

Inputs: An IT administrator logs into a new Windows Server 2022 machine for the first time using the default built-in Administrator account. They try to open the Calculator to perform a quick calculation.

Result: They receive the message “This app can’t open using the Built-in Administrator account.” To fix this, they must open the Local Security Policy editor, navigate to the policy mentioned above, and set it to ‘Enabled’, then restart the machine.

Example 2: Power User Disables UAC

Inputs: A Windows 10 power user has an account with admin rights. Annoyed by UAC prompts, they find a registry tweak to disable UAC completely. Later, they find that not only the Calculator but also the Photos app and Microsoft Store will not launch.

Result: Although they are not using the *built-in* admin account, completely disabling UAC creates a similar security context that blocks modern apps. The solution is to re-enable UAC to at least the lowest notification level. If you need to do this, check out our guide on how to safely adjust UAC settings.

How to Use This Interactive Troubleshooter

Our tool simplifies diagnosing the “calculator cannot open using the built-in administrator account” error. Follow these steps for an accurate recommendation:

1. Select Your Windows Version: Choose between Windows 10, 11, or Server, as the interface for settings can differ slightly.
2. Specify the Account Type: This is the most important step. Be honest about whether you are in the special, built-in “Administrator” account or just a regular user account with admin rights.
3. Indicate UAC Status: Let the tool know if you have User Account Control (UAC) enabled or disabled. If you are unsure, select “I don’t know,” and the tool will provide steps to check.
4. Review the Result: The troubleshooter will provide a tailored solution based on your inputs, often pointing directly to the policy or setting that needs to be changed.

Key Factors That Affect This Issue

• Account Type: The single biggest factor. The error is designed specifically for the built-in superuser account.
• User Account Control (UAC) Settings: Disabling UAC entirely can replicate this issue for all admin accounts on the system.
• Local Security Policy / Group Policy: This is where the root setting is configured. In a corporate environment, this might be controlled by a domain-wide Group Policy.
• Application Type: This error only affects modern UWP apps. Traditional desktop applications (like Notepad, or third-party software) are not affected. You can learn more about running apps with admin rights.
• Windows Edition: Windows Home editions do not have the Local Security Policy editor (secpol.msc), requiring a registry edit to achieve the same fix.
• System File Corruption: In rare cases, if the issue persists after policy changes, it might indicate deeper system file problems that require tools like SFC or DISM. See our guide on fixing UWP apps not starting for advanced steps.

Frequently Asked Questions (FAQ)

Why does this error only happen for the built-in administrator?

For security, this account operates outside the standard UAC “Admin Approval Mode” by default. This mode is required for modern apps to run. The fix essentially enables this mode for that specific account.

Is it safe to enable “Admin Approval Mode” for the built-in administrator?

It is generally safe and is the recommended solution from Microsoft to enable this functionality. However, the most secure practice is to not use the built-in administrator account for daily tasks. Create a separate user account with admin rights instead.

I have Windows 10 Home and can’t find ‘secpol.msc’. How do I fix it?

Windows Home users must use the Registry Editor (`regedit`). Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`, create a new DWORD value named `FilterAdministratorToken`, and set its value to `1`.

What’s the difference between the built-in administrator and my admin account?

The built-in administrator is a “superuser” account with unrestricted access. A user account in the ‘Administrators’ group operates with standard user privileges until it needs to perform an admin task, at which point a UAC prompt appears to elevate its privileges temporarily.

I enabled the policy, but the calculator still won’t open. What now?

First, ensure you have restarted your computer. If it still fails, the app itself might be corrupted. Try resetting the Calculator app by going to Settings > Apps > Apps & features, finding Calculator, selecting ‘Advanced options’, and clicking ‘Reset’.

Can I just run the calculator “as administrator”?

No. For UWP apps, the “Run as administrator” context menu option does not bypass this specific security policy. The problem is not a lack of permissions but a conflict in security models.

Why did Microsoft design it this way?

It’s a “secure-by-default” approach. Since the built-in administrator is so powerful, limiting its ability to run sandboxed, consumer-focused apps reduces the potential attack surface on a critical system account.

Does changing the UAC slider to “Never Notify” fix this?

No, it often makes it worse by causing the same issue for *all* administrator accounts, not just the built-in one. It is not the recommended solution.

Related Tools and Internal Resources