Fixes / Windows · Checked September 30, 2026

Windows "This app can't run on your PC": causes and fixes

Short answer

"This app can't run on your PC" means Windows refused to start the program because the file wasn't built for your Windows version or processor, or the file is damaged. The most common cause is a 64-bit, x64 or ARM64 build on a PC it doesn't match, or an incomplete download. Check Settings > System > About > System type, then download the matching version from the publisher.

What this message means

Windows shows this message before the program starts. It checks the header of the .exe file to see which processor type and Windows version it was built for. If the file is for a different architecture (for example a 64-bit app on 32-bit Windows, or an ARM64-only app on an Intel or AMD PC), Windows won't load it. It also won't load a file that is empty, truncated or corrupted, because it can't read the header at all. If you see the message when opening a built-in tool such as Notepad or Command Prompt, the usual cause is damaged system files or malware, not compatibility.

Common causes

Cause	How to tell
The app is built for a different processor type (32-bit vs 64-bit, or x64 vs ARM64)	Settings > System > About > System type shows something like "32-bit operating system, x64-based processor" or "ARM-based processor", and the file you downloaded is labelled x64, 64-bit, amd64 or arm64 in its name or on the download page.
The download is incomplete, empty or corrupted	Right-click the file and choose Properties: the Size is 0 bytes or much smaller than the size listed on the download page, or the download was interrupted or finished suspiciously fast.
Windows system files are damaged, breaking built-in apps	The message appears when opening Windows' own tools such as Notepad, Command Prompt, Task Manager or Registry Editor, often several of them, after a failed update, crash or malware cleanup.
The app only supports an older version of Windows	The program is old (for example made for Windows XP or 7) and the publisher's site doesn't list Windows 10 or 11 as supported.
Malware replaced or corrupted the program file	Several unrelated programs or shortcuts suddenly show the message at once, or the file's Properties show an unexpected size, date or publisher.

How to fix it

1. Check your system type and download the matching version

Windows 10 and Windows 11

Open Start > Settings > System > About.
Under Device specifications, read System type. It will say 32-bit or 64-bit operating system, and x64-based or ARM-based processor.
Go to the software publisher's official download page and pick the build that matches: x86 or 32-bit for 32-bit Windows, x64 or 64-bit for 64-bit Intel/AMD PCs, ARM64 (or x64/x86 if no ARM build exists) for ARM-based PCs.
Delete the old installer, run the new one and try again.
If the publisher only offers a 64-bit build and you run 32-bit Windows 10, the app can't run on that installation. Moving to 64-bit Windows requires a clean install.

2. Re-download the file and check its size

Right-click the .exe file and select Properties.
Compare Size with the size shown on the publisher's download page. A 0 KB or much smaller file is broken.
Delete the file and download it again from the official site, ideally with a different browser or network.
If a USB stick or cloud sync copied the file, copy it again or download it straight to the PC.
Run the new copy.

3. Use the right app on an ARM-based PC (Snapdragon, Copilot+ PC)

Windows 11 on Arm runs x86 and x64 apps through emulation. Windows 10 on Arm runs only x86 (32-bit) apps, not x64.

Confirm System type says ARM-based processor in Settings > System > About.
Look for an ARM64 download on the publisher's site first. It will run fastest.
If there is no ARM64 build, use the x64 build on Windows 11, or the x86 (32-bit) build on Windows 10 on Arm.
Drivers, antivirus kernel components and some anti-cheat games can't be emulated. For those, check the publisher's site for ARM support, as no setting on your PC will make them run.

4. Repair Windows system files with DISM and SFC

Use this when built-in Windows apps (Notepad, Command Prompt, Task Manager) show the error

Select Start, type cmd, right-click Command Prompt and choose Run as administrator. If Command Prompt itself fails, right-click Start and choose Terminal (Admin) (Windows 11) or Windows PowerShell (Admin) (Windows 10).
Run: DISM.exe /Online /Cleanup-image /Restorehealth and wait until it reaches 100%.
Run: sfc /scannow and wait for it to finish.
Restart the PC and try the app again.
For Notepad specifically, you can also go to Settings > Apps > Optional features (Windows 11: Settings > System > Optional features), uninstall Notepad, restart, then use Add a feature (Windows 11: View features) to reinstall it.

5. Scan for malware

Open Start > Settings > Privacy & security > Windows Security (Windows 10: Update & Security > Windows Security).
Select Virus & threat protection > Scan options.
Choose Microsoft Defender Offline scan and select Scan now. The PC will restart and scan before Windows loads.
After cleanup, run the DISM and SFC fix above to restore any damaged system files.

6. Try compatibility mode for older 32-bit or 64-bit programs

Only helps with old Windows version checks. It cannot fix a processor-type mismatch.

Right-click the program's .exe file (not a shortcut from the web) and select Properties.
Open the Compatibility tab.
Tick Run this program in compatibility mode for and pick the Windows version the app was made for, such as Windows 7.
Click Apply, then OK, and open the program.
If it still fails, click Run compatibility troubleshooter on the same tab and follow its suggestions.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the right build still won't start, contact the software publisher with your exact System type (from Settings > System > About) and Windows version (press Windows key + R, type winver, press Enter). They can confirm whether your processor and Windows edition are supported. If Windows' own apps keep failing after DISM and SFC, go to Settings > System > Recovery and use Reset this PC with Keep my files, or post the DISM and SFC results on Microsoft Q&A. On a work or school PC, ask your IT department, as they may control which apps can run.

Questions people ask

Why does "This app can't run on your PC" appear when I open Notepad or Command Prompt?

Built-in Windows tools only show this when their files are damaged, missing or replaced, usually after a failed update or malware. Running DISM /Online /Cleanup-image /Restorehealth, then sfc /scannow from an administrator prompt usually fixes it.

Can I run a 64-bit app on 32-bit Windows?

No. A 32-bit Windows installation can't run 64-bit programs, and no setting changes that. You need a 32-bit version of the app, or you need to reinstall Windows as 64-bit (Windows 11 is 64-bit only), which requires a clean install.

Will compatibility mode fix this error?

Only if the app was blocked because it targets an older Windows version. Compatibility mode can't make a 64-bit or ARM64-only app run on hardware or Windows it wasn't built for.

Is this the same as the S mode message?

No. In S mode, Windows says the app isn't an option in S mode and points you to the Microsoft Store. You can leave S mode for free under Settings > System > Activation (Windows 10: Update & Security > Activation), but the switch is one-way.

Does running the app as administrator help?

Rarely. Administrator rights don't change which processor or Windows version a file was built for, so if the file is the wrong build or damaged, the error stays.

Sources

Related errors