How to Fix "This App Can't Be Activated by the Built in Administrator"

If Windows had a sense of humor, this error message would be its version of a prank. You click an app, expecting it to open like a civilized piece of software, and instead Windows throws out: "This app can't be activated by the Built-in Administrator". Helpful? Barely. Annoying? Absolutely. Mysterious? Only until you know what is really going on behind the curtain.

This error usually appears when you are signed in with the hidden built-in Administrator account, or when User Account Control settings and related policies are configured in a way that blocks modern Windows apps from launching correctly. In plain English, Windows is saying, “You are too powerful for this app, and I do not trust your vibe.”

The good news is that this problem is usually fixable without a full reinstall, dramatic keyboard pounding, or making eye contact with your router in disappointment. In this guide, you will learn why the error happens, how to fix it step by step, and how to prevent it from coming back. Whether the app in question is Microsoft Store, Settings, Photos, or another built-in Windows app, these fixes can help.

What Causes the "This App Can't Be Activated by the Built in Administrator" Error?

This issue is closely tied to User Account Control, often called UAC. UAC is the Windows feature that acts like a cautious hall monitor. It separates regular activity from elevated administrative actions so apps do not run with unlimited privileges all the time.

The built-in Administrator account is different from a normal user account that also has administrator rights. A regular admin account usually runs with filtered permissions until elevation is needed. The hidden built-in Administrator account, however, can behave differently depending on your system policies. Some Windows apps, especially newer built-in apps, expect a split-token or approval-based environment. If they do not get it, they refuse to launch and hand you this wonderfully awkward message.

That means the problem is not usually the app itself. The app is just the messenger. The real issue is the account type, the UAC configuration, or both.

Before You Start: Do These Two Quick Checks

1. Restart the PC First

Yes, the classic advice is still alive. If you already changed UAC or policy settings and nothing happened, restart the computer before assuming the fix failed. This issue often needs a full reboot before Windows applies the new behavior.

2. Check Which Account You Are Using

If you are signed in as the hidden built-in Administrator account, that is the most likely trigger. If you are using a normal administrator account, then the error may come from a misconfigured UAC setting, a damaged profile, or a related Windows component problem.

To check, open Settings > Accounts and look at your account details. If your device belongs to a school, business, or managed environment, company policy may also be involved, so keep that in mind before changing settings.

Fix 1: Use a Different Administrator Account

This is the cleanest fix and often the smartest one. Instead of forcing the built-in Administrator account to behave like a regular admin, switch to a standard local or Microsoft account with administrator privileges. Windows generally plays much more nicely with that setup.

How to do it

1. Open Settings.
2. Go to Accounts.
3. Select Other users or Family & other users.
4. Choose Add account.
5. Create a new local or Microsoft account.
6. After the account is created, change its account type to Administrator.
7. Sign out of the built-in Administrator account and sign in to the new admin account.

If the app opens normally after that, you have found the culprit. In many cases, this is the best long-term solution because it is safer and better aligned with how Windows expects modern apps to run.

Fix 2: Enable Admin Approval Mode for the Built-in Administrator Account

If you must keep using the built-in Administrator account, the next fix is to enable Admin Approval Mode for it. This tells Windows to treat that account in a more controlled, UAC-aware way, which can allow blocked apps to launch properly.

Method A: Use Local Security Policy

This is the easier route when the Local Security Policy tool is available on your PC.

1. Press Windows + R.
2. Type secpol.msc and press Enter.
3. Go to Local Policies > Security Options.
4. Find User Account Control: Admin Approval Mode for the Built-in Administrator account.
5. Double-click it and set it to Enabled.
6. Click Apply, then OK.
7. Restart your computer.

After rebooting, try opening the app again. For many users, this is the headline fix.

Method B: Use the Registry

If you cannot access Local Security Policy, you can make the equivalent change in the Registry. Take a backup or create a restore point first, because the Registry is not a place for casual optimism.

1. Press Windows + R.
2. Type regedit and press Enter.
3. Navigate to:
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
4. Look for a DWORD named FilterAdministratorToken.
5. If it does not exist, create a new DWORD (32-bit) Value and name it FilterAdministratorToken.
6. Set its value to 1.
7. Restart the computer.

That Registry value corresponds to enabling Admin Approval Mode for the built-in Administrator account. No reboot, no victory lap. Restart first.

Fix 3: Make Sure UAC Is Not Turned Off

Some users disable UAC because they are tired of prompts popping up like overly enthusiastic toast notifications. Unfortunately, turning it off can break app activation behavior for certain Windows apps.

If UAC is disabled or effectively reduced in a way that interferes with Windows app security, this error may appear.

How to check UAC

1. Open Control Panel.
2. Go to System and Security.
3. Select Change User Account Control settings.
4. Move the slider to a level above Never notify.
5. Click OK.
6. Restart the PC.

You do not need to choose the most dramatic, top-level setting unless your environment requires it. The important part is avoiding a fully disabled UAC configuration when modern apps depend on it.

Fix 4: Check the EnableLUA Registry Setting

Another important UAC-related setting is EnableLUA. If it is set incorrectly, UAC behavior may be disabled at the system level, and Windows apps can start acting like they were hired without proper onboarding.

How to verify it

1. Open Registry Editor.
2. Navigate to:
   HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
3. Find EnableLUA.
4. Make sure the value is set to 1.
5. Restart the computer.

If EnableLUA is set to 0, Windows is effectively told to stop using standard UAC behavior. That can trigger exactly the kind of activation error you are trying to escape.

Fix 5: Run System File Checks if the Problem Persists

If the account and UAC settings look correct but the error keeps showing up, damaged system files may be part of the mess. This is especially worth checking if Settings flashes, Store apps crash immediately, or other built-in tools behave strangely.

Run SFC and DISM

1. Open Command Prompt as administrator.
2. Run this command:
   sfc /scannow
3. After it finishes, run:
   DISM /Online /Cleanup-Image /RestoreHealth
4. Restart the computer when both scans finish.

These tools can repair corrupted Windows system files and component-store issues that may be interfering with app launches. They are not magic, but they are often annoyingly effective.

Fix 6: Test the App in a Fresh Profile

Sometimes the problem is not global. It is just your user profile having a minor identity crisis. If a new administrator account can open the same app without trouble, the old profile may be damaged or misconfigured.

Testing in a fresh profile helps answer one important question: is this a Windows policy issue, or is it your account specifically? If the new account works, move your important files, keep the new account, and retire the old one like a sitcom character who ran out of plot.

Common Mistakes to Avoid

Do not disable UAC completely unless you truly understand the consequences

It might seem like a shortcut, but it often creates more problems than it solves.

Do not forget to reboot

This error loves to trick people into thinking a change failed when Windows simply has not applied it yet.

Do not use the built-in Administrator account for everyday work if you can avoid it

That account is powerful, but it is not the most user-friendly option for modern Windows behavior. A regular administrator account is usually safer and more compatible.

Do not edit the Registry carelessly

One typo in the wrong place can turn a mild annoyance into a larger support adventure. Back up first.

Which Fix Works Best?

If you want the short answer, here it is:

• Best long-term fix: Use a different administrator account.
• Best direct fix for the built-in Administrator account: Enable Admin Approval Mode.
• Best supporting fix: Make sure UAC is not turned off and EnableLUA is set to 1.
• Best cleanup move: Run SFC and DISM if the issue still feels haunted.

In most real-world situations, the combination of enabling Admin Approval Mode, confirming UAC is active, and rebooting solves the problem.

Real-World Experiences With This Error

One reason this issue frustrates so many people is that it often appears at the worst possible moment. A home user signs into an old recovery account, tries to open Settings, and suddenly Windows acts like the user is both too privileged and not privileged enough. It feels ridiculous, but it is surprisingly common in repair scenarios.

A typical example involves someone reviving an older laptop. They enable the hidden Administrator account during troubleshooting because it sounds important and powerful. Fair enough. Then they try to launch Microsoft Store, Photos, or another built-in app, and the error appears. At that point, it looks like Windows has locked the door from the inside. In reality, the account is simply not configured the way those apps expect.

Another common experience happens in small office environments. A tech sets up a machine quickly using the built-in Administrator account, intending to create proper user accounts later. Then an employee needs to use a modern Windows app, and the machine refuses. Everyone assumes the app is broken, the installation is corrupt, or Microsoft just woke up grumpy. The fix turns out to be much simpler: enable Admin Approval Mode or stop using the hidden Administrator account for daily work.

There are also cases where users make the problem worse by turning off UAC. The logic sounds reasonable at first. Fewer prompts should mean fewer restrictions, right? But Windows is not always that straightforward. UAC is tied into how modern apps are launched and protected. When it is fully disabled, the system can become less compatible with the very apps people are trying to open. That leads to the classic cycle of frustration: one tweak creates another error, which inspires three more tweaks, which then require an evening of googling and a suspicious amount of coffee.

Support forums are full of stories where the final step was embarrassingly simple: restart the PC. A user changes the policy, edits the Registry, stares at the app icon, clicks again, and still gets the same message. Ten minutes later, after a reboot, the app opens as if nothing happened. This is one of those Windows problems where impatience can make a working fix look broken.

Perhaps the most useful lesson from real experiences is this: the hidden built-in Administrator account is best treated like a tool, not a lifestyle. It is useful for recovery, repair, and special troubleshooting situations. It is not ideal as your regular everyday sign-in. Users who switch to a standard admin account usually end up with fewer weird app issues, fewer security headaches, and a much lower chance of having Windows lecture them in cryptic pop-up form.

So if this error has been haunting your machine, do not panic. You are not dealing with a rare disaster. You are dealing with a very Windows-style disagreement between permissions, policies, and modern apps. Annoying, yes. Fixable, also yes.

Final Thoughts

The error "This app can't be activated by the Built in Administrator" looks dramatic, but the fix is usually practical. The issue almost always comes down to how Windows handles the hidden Administrator account and UAC. Once you enable the right approval mode, confirm UAC is active, or move to a normal administrator account, the problem often disappears.

If you want the smoothest Windows experience, the safest strategy is simple: reserve the built-in Administrator account for special troubleshooting tasks, and use a separate admin account for normal work. That way, your apps can launch normally, your security posture stays healthier, and Windows gets one less reason to be theatrical.