Troubleshooter for “calculator cant be used with built in administrator account” Error

This interactive tool helps you diagnose and solve the Windows error that prevents modern apps like the Calculator from running on the built-in Administrator account.

Diagnostic Troubleshooter

What is the “calculator cant be used with built in administrator account” error?

This error is a security feature, not a bug, in modern Windows operating systems like Windows 10 and 11. It occurs when a user is logged directly into the special, built-in “Administrator” account and tries to open a Universal Windows Platform (UWP) app, such as the Calculator, Photos, Microsoft Store, or Edge. These modern apps are designed to run with standard user privileges in a sandboxed environment to protect the system. The built-in Administrator account, by default, runs everything with the highest level of privilege and has User Account Control (UAC) disabled for it, which conflicts with the security model of UWP apps.

The core misunderstanding is the difference between the account named “Administrator” and a user account that is a member of the “Administrators” group. Day-to-day work, even for IT professionals, should be done from a user-created administrator account, not the built-in one.

The Logical “Formula” Behind the Error

The error doesn’t stem from a mathematical formula but a logical check performed by Windows. The conditions that trigger the block are:

Logical conditions leading to the app block

Variable	Meaning	State Causing Error
User Token	The type of account currently logged in	Built-in Administrator (Security ID S-1-5-…-500)
App Type	The architecture of the application being launched	Universal Windows Platform (UWP) App
UAC Policy	“Admin Approval Mode for the Built-in Administrator account”	Disabled (Default state)

When all three conditions are met, the operating system prevents the UWP app from launching to mitigate the security risk of a sandboxed app potentially escaping its container with the highest possible system privileges.

Practical Examples

Example 1: The Accidental Administrator

A user enables the built-in Administrator account on their Windows 11 PC for a task and forgets to sign out. Later, they try to open the Calculator to do a quick sum. The Calculator app icon is clicked, but nothing happens, or the error message “This app can’t be opened using the Built-in Administrator account” appears.

• Inputs: Logged in as “Administrator”, trying to open “Calculator.exe”.
• Result: The app fails to launch.
• Solution: The user should sign out of the Administrator account and sign into their regular user account (which should have admin privileges). For best security, the built-in Administrator account should then be disabled. Find out more about user account types.

Example 2: The IT Professional on a New Server

An IT admin is setting up a new Windows Server 2022 machine. They are logged in with the default built-in Administrator account. They attempt to open a modern settings panel, which is a UWP app, and find it won’t launch.

• Inputs: Logged in as “Administrator” on Windows Server.
• Result: UWP-based server management tools or settings panels fail to open.
• Solution: The best practice is to immediately create a new, named user account, add it to the Administrators group, sign out of the built-in account, and sign in with the new one. The built-in account can then be disabled or have its password secured, following company policy. Learn about server security best practices.

How to Use This Troubleshooter for the “calculator cant be used with built in administrator account” Issue

Our diagnostic tool simplifies resolving this issue by asking targeted questions to identify the root cause.

1. Select Your Account Type: This is the most important step. Be honest about whether you’re using the account literally named “Administrator” or your own personal admin account.
2. Choose Your Windows Version: This helps tailor the advice, although the core principle is the same across modern Windows versions.
3. Specify UAC Status: Indicate whether you are seeing User Account Control prompts. This helps determine if UAC settings have been altered from their defaults.
4. Click “Diagnose Problem”: The tool will analyze your inputs and provide a primary solution and a detailed explanation, which you can see in our troubleshooting guides.
5. Interpret the Results: The result will clearly state the recommended course of action, which usually involves using a different account or, in rare cases, changing a security policy.

Key Factors That Affect This Behavior

• Account Type: The primary factor. The issue is almost exclusively linked to the built-in “Administrator” account.
• User Account Control (UAC) Settings: If UAC is completely disabled system-wide, it can cause issues with many parts of the OS, not just UWP apps.
• Local Security Policy / Group Policy: The “Admin Approval Mode for the Built-in Administrator account” policy directly controls this behavior. An administrator can change this setting, but it carries security implications. Read more on configuring security policies.
• Application Architecture: The error only affects modern UWP apps. Traditional Win32/.NET desktop applications (like Notepad or older versions of Microsoft Office) will still run without issue.
• Windows Edition: Windows Home editions lack the Local Security Policy editor (secpol.msc), so fixing the issue by modifying the policy requires direct registry editing.
• Registry State: The aforementioned security policy corresponds to a specific registry key. If this key becomes corrupted or is changed by software, it can alter the behavior.

Frequently Asked Questions (FAQ)

1. Why does Windows have this restriction?

It’s a “secure-by-default” design choice. It prevents potentially vulnerable apps from running with the highest, non-virtualized administrative token, reducing the potential damage from malware or exploits.

2. Can I disable this and force the calculator to open?

Yes, it is technically possible by enabling the “User Account Control: Admin Approval Mode for the Built-in Administrator account” security policy. However, this is strongly discouraged. The recommended fix is always to use a separate, user-created administrator account for your daily tasks.

3. What is the difference between “Administrator” and my account in the “Administrators” group?

The built-in Administrator account is a special, high-privilege account with a fixed Security Identifier (SID). A user account in the Administrators group runs with standard privileges by default and must request elevation (triggering a UAC prompt) to perform administrative tasks. This provides a crucial layer of security.

4. How do I create a new administrator account?

You can go to Settings > Accounts > Family & other users > “Add someone else to this PC”. Follow the prompts to create a new local account, and once created, you can change its account type to “Administrator”.

5. I’m seeing this error for Photos and the Microsoft Store too. Is it the same problem?

Yes. The error “calculator cant be used with built in administrator account” applies to almost all modern UWP apps, not just the Calculator.

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

While safer than leaving it disabled, it’s still not the recommended practice. It makes the built-in account behave more like a regular admin account, but the standard security advice is to disable the built-in account entirely and use a named admin account that can be audited and managed. Explore our advanced UAC settings guide for more details.

7. Why is this a problem now? I never had this issue on Windows 7.

Windows 7 had very few UWP-style apps. This architecture became the standard for inbox apps starting with Windows 8 and continuing into Windows 10 and 11, which is why the behavior is prominent on modern systems.

8. My account is an administrator, but I still can’t open some programs without “Run as administrator”. Why?

This is a different, though related, concept. Some older applications or poorly designed programs require full administrative rights to function, even for simple tasks. This is different from the UWP restriction, which is a blanket block regardless of the app’s needs. Check out how to resolve run as administrator issues.