How to Fix “This App Can’t Run on Your PC”
There are few things more annoying than double-clicking a program you just downloaded, only to be greeted by a stubborn error message. Depending on your specific situation, Windows might throw one of these three variations at you:
“This app can’t run on your PC.” (The classic error. It usually tells you to check with the software publisher.)
“This app can’t open… while User Account Control is turned off.” (A security setting issue.)
“This app has been blocked for your protection.” (Windows doesn’t trust the file and needs an Admin override.)
Before you dive into the deep technical fixes, look at the error message closely. If it mentions User Account Control (UAC), you simply need to go to your control panel and turn UAC back on. If it says it’s blocked, you usually just need to right-click the file and “Run as Administrator.”
But assuming you’ve already tried those basics and you are still staring at the “This app can’t run” box, let’s go through the solutions that actually work.
1. Force It with Compatibility Mode
Windows 10 and 11 are great, but they don’t always play nice with older software. The first thing you should try is tricking the app into thinking it’s running on an old PC.
Right-click the application’s icon (the
.exefile) and select Properties.Head over to the Compatibility tab.
Don’t ignore the “Run compatibility troubleshooter” button at the top. It’s actually smarter than people give it credit for. It scans the file and automatically suggests settings (like Windows 8 mode) that might fix the glitch.
If the troubleshooter fails, do it manually:
Check the box for “Run this program in compatibility mode for” and select Windows 7 or Windows 8.
If the app is really old (like a game from the 90s), look at the Settings section below. You might need to check “Reduced color mode” or “Run in 640 x 480 screen resolution” to get it to launch.
2. The Software Might Be Abandonware
If you are trying to run a niche tool or an old game, there is a chance the developer simply stopped updating it. Windows 10 and 11 architecture changes over time, and an app that worked three years ago might break after a recent Windows Update.
Check the source: Go to the developer’s website. They may have released a “Version 2.0” specifically for Windows 10/11.
Find an archived version: If the new version is broken, sometimes the older one works better. Sites like OldVersion.com are lifesavers for finding previous builds of popular software.
Virtual Machines: If you absolutely must run a program designed for Windows XP and nothing else works, your best bet is to install a free tool like VMware Player or VirtualBox. You can install an old copy of Windows inside that program and run your app there.
3. The 32-bit vs. 64-bit Mismatch
This is the most common technical reason for the error.
64-bit Windows can run almost anything (both 32-bit and 64-bit apps).
32-bit Windows is strictly limited. It generally cannot run 64-bit software.
If you have a 32-bit operating system and you downloaded an installer labeled “x64,” it will never open. You need to go back and find the “x86” (32-bit) version.
Also, watch out for ancient 16-bit apps. Windows 64-bit has dropped support for 16-bit applications entirely. If you really need to run a 16-bit DOS program, you’ll need an emulator like DOSBox, not just compatibility mode.
To check what you are running, go to Start > Settings > System > About and look at “System type.”
4. Enable Developer Mode (Sideloading)
Sometimes Windows blocks an app simply because it didn’t come from the Microsoft Store or it’s an unverified package. You can tell Windows to loosen its tie a bit by enabling Developer Mode.
Go to Start > Settings > Update & Security.
Select For developers from the left-hand menu.
Toggle on Developer Mode.
Windows will ask for confirmation (Click “Yes”) and you will likely need to restart your computer.
A Note on Bad Advice
If you search for this error online, you will find endless articles telling you to do generic “maintenance” tasks.
To save you time: Cleaning your Registry, clearing your browser cache, or running sfc /scannow (System File Checker) rarely fixes this specific error. These are usually copy-paste solutions for system performance, not for specific application compatibility. Stick to the architecture checks (32 vs 64-bit) and compatibility modes listed above—that is where the real solution usually hides.