"This App Can't Run on Your PC" — What It Actually Means
Short answer
The message is generic and covers four separate causes. Check the file first: right-click it, choose Properties, and if a Security: This file came from another computer notice appears at the bottom, tick Unblock and try again. If that is not it, the usual causes are a 16-bit or wrong-architecture program, a SmartScreen or policy block, or a corrupt download.
On this page
The wording is unhelpful on purpose. Windows uses the same dialog for at least four unrelated failures, and the second line is the only part that varies meaningfully — “To find a version for your PC, check with the software publisher” points at architecture, while a mention of your administrator or of app recommendation settings points at policy.
Working out which one you have takes about a minute and saves downloading the wrong thing three times.
Which of the four is yours
| What you see or know | Cause | Fix |
|---|---|---|
| Properties shows an Unblock checkbox | Downloaded file blocked by Windows | Unblock it |
| Old software, pre-Windows XP era | 16-bit, cannot run on 64-bit Windows | Architecture |
| Message mentions your administrator | Policy or S mode block | Policy and S mode |
| Installer worked before, fails now | Corrupt download or damaged system files | Corrupt file |
The blocked download
Windows tags every file downloaded from the internet with a marker recording that it came from elsewhere. Some files, particularly those extracted from a downloaded ZIP, inherit that marker in a way that stops them executing at all.
Right-click the file → Properties. At the bottom of the General tab, a Security line reads along the lines of the file having come from another computer and possibly being blocked. Tick Unblock, click OK, and run it again.
Do this only for software you obtained from a source you trust, such as the developer’s own website. The marker exists for a reason, and unblocking a file from an unknown source removes a genuine safety check.
If the software arrived as a ZIP, unblock the ZIP before extracting. Extracting first propagates the marker to every file inside, and unblocking them one at a time is miserable.
The architecture mismatch
Three distinct versions of this.
16-bit software. Programs from Windows 3.x and the mid-1990s are 16-bit, and 64-bit Windows removed the subsystem that ran them. There is no setting, no compatibility mode and no update that changes this. The only routes are a virtual machine running 32-bit Windows or an older OS, or DOSBox for DOS-era software. This is a genuine hard limit, not a configuration problem.
32-bit Windows, 64-bit program. Less common now, but a machine running 32-bit Windows cannot run a 64-bit application at all. Check at Settings → System → About under System type. A 32-bit installation on 64-bit capable hardware can only be changed by a clean install, not an upgrade.
Windows on Arm. Arm-based PCs including Copilot+ devices emulate x86 and x64 applications, and the emulation is good but not universal. Software with kernel drivers — some antivirus products, VPN clients, anti-cheat systems and hardware utilities — needs a native Arm build and fails without one. Check the System type field for an Arm-based processor, then look for an Arm64 download on the publisher’s site.
For ordinary 32-bit desktop software on 64-bit Windows, there is no problem at all. WoW64 handles it transparently, and most Windows software is still shipped 32-bit.
Policy and S mode
S mode restricts installation to apps from the Microsoft Store. It ships on some consumer laptops and surprises people who did not know they bought one.
Check at Settings → System → About — the edition name includes S mode if you are in it. Switching out is free, via Settings → System → Activation, where a Microsoft Store link handles it in about a minute.
It is one-way. Once out of S mode, there is no supported route back without reinstalling Windows. That is usually fine, and it is worth knowing before you click.
Work or school machines can block unapproved software through AppLocker, Windows Defender Application Control or Intune policy. The message typically names your administrator. Nothing you do locally will override it, by design, and asking IT is the only route.
SmartScreen is a separate, softer block. It warns about files it has not seen frequently enough to trust, which catches a lot of legitimate niche software. Its dialog offers More info → Run anyway. Use that only when you downloaded the file from the publisher’s own site and checked the address bar.
Corrupt downloads and damaged system files
An installer that worked before and fails now is usually damaged rather than incompatible.
Re-download it, from the publisher directly rather than an aggregator. A download interrupted partway produces a file that looks complete and is not. If the publisher provides a checksum, comparing it is conclusive:
certutil -hashfile "path\to\file.exe" SHA256
Compare the result against the published value.
Check the system itself if multiple unrelated applications start failing. That points at Windows rather than at any one program. In Terminal (Admin):
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Allow 10–30 minutes and restart afterwards.
Try compatibility mode for older but genuinely 32-bit software. Right-click the file → Properties → Compatibility tab → tick Run this program in compatibility mode for and choose an older Windows version. The Troubleshoot compatibility button on the same tab runs a guided version which is usually quicker.
Compatibility mode changes the version Windows reports and adjusts some behaviours. It cannot make a 16-bit or wrong-architecture program run, so if the file is one of those, this is not the answer.
When the software is simply too old
Some things are not fixable in place, and it is worth recognising them early:
- 16-bit software on 64-bit Windows.
- Software depending on a removed Windows component, such as older versions requiring the legacy print driver model Microsoft has deprecated.
- Software needing a driver that was never signed for recent Windows versions. Driver signature enforcement exists specifically to prevent this and disabling it permanently is a poor trade.
A virtual machine is the honest answer for all three. Windows 11 Pro includes Hyper-V, and VirtualBox is free on any edition. Running an old Windows version inside a VM keeps the legacy software working without compromising the host, and it isolates an operating system that no longer receives security updates.
What does not help
- Running as administrator for an architecture or S mode problem. It changes privilege, not capability.
- Disabling Windows Defender to get past the message. If SmartScreen is the block, its own Run anyway option is both narrower and safer.
- “Fix all errors” utilities. They do not address any of the four causes.
- Reinstalling Windows. Unless system file corruption is confirmed, it is an expensive test of a weak hypothesis.
- Downloading the installer from a different aggregator site. A faster way to acquire something you did not want than to fix a genuine incompatibility.
Realistic expectations
The unblock checkbox and the S mode switch together account for a large share of cases, and both take under two minutes.
Architecture mismatches are not fixable; they are identifiable. Once you know the software is 16-bit or needs a native Arm build that does not exist, the decision is between a virtual machine and a replacement application, and more searching will not produce a third option.
If several unrelated applications began failing on the same day, stop chasing them individually and repair the system files first. That pattern is almost always Windows rather than the software, and choosing between System Restore and a reset covers what to do if the repair does not hold.