Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Installer has x86, x64 and Arm64 versions | Choose the version matching System type |
| PC is in Windows 11 S mode | Use Store version or evaluate leaving S mode |
| Very old app or driver | Find a supported release or isolated legacy environment |
| Download has no valid signature | Download again from the official publisher |
Diagnose app compatibility error before making major changes
Record the exact 'This app can't run on your PC' message and identify the app's architecture, publisher, and source. Check whether Windows is x64, ARM64, or another architecture.
Download the correct installer directly from the publisher and confirm Windows edition, architecture, and required runtime. Avoid repacked or modified installers.
Try a known-compatible version of the same app or another signed app from the same publisher. If only one build is blocked, architecture or packaging is more likely than Windows corruption.
This message is usually better explained by compatibility, signing, policy, or architecture than crash logs. Check SmartScreen, S mode, App Control, and organization policy where relevant.
If replacing an older app build, back up its settings and project files first. Do not disable security protections globally to force an unknown executable to run.
Match the app to the PC architecture
Open Settings > System > About and record System type and Windows specifications. Download the publisher's x64, Arm64 or other build that matches the PC. x86 applications often run on x64 Windows, but drivers and shell extensions have stricter architecture requirements.
Confirm the app supports Windows 11 and the installed release. An installer for Windows on another processor, macOS, Linux or a mobile platform cannot be repaired through compatibility mode.
1Verification checkpoint
- Install or launch the architecture-correct build.
- Confirm the original compatibility message is gone.
- If not, note any new SmartScreen or policy message.
Check S mode, source and file integrity
Check Activation for S mode. S mode permits Microsoft Store apps and leaving it is one-way. Prefer an official Store edition when available. Do not leave S mode for an unknown executable.
Download the file again over a stable connection from the publisher. In Properties, inspect Digital Signatures and any Unblock option shown for a trusted file. A missing or invalid signature is a reason to verify the source, not to disable SmartScreen.
2Verification checkpoint
- Check the app publisher and signature.
- Confirm the file came from the expected source.
- Do not bypass an unknown or unsigned file.
Use compatibility options only for suitable legacy apps
For an older ordinary desktop program, run Windows' compatibility troubleshooter or test a publisher-supported compatibility setting. Compatibility mode cannot make an incompatible driver, 16-bit program or different CPU architecture work.
Look for a maintained replacement, web edition or virtualized legacy environment when the publisher ended support. Avoid patched executables offered by third parties; they can remove security checks and introduce malware.
3Verification checkpoint
- Restart and launch again.
- Confirm the app still runs under normal security settings.
- Stop once compatibility is proven.
Verify the repair and stop at the right point
Launch the compatible build from the same account, then restart Windows and launch it again. Confirm no security policy was permanently weakened.
Once the correct build runs, stop changing compatibility or security settings. The cleanest fix is usually the right app package, not a system-wide bypass.
If many known-good signed apps are blocked across accounts, investigate policy, App Control, Windows S mode, or system integrity before attempting a repair install.
Technical order checked against Microsoft Windows S mode guidance. Menus, policies and app options can vary by Windows edition, device management and publisher.
Frequently asked questions
How do I know whether my PC is x64 or Arm64?
Open Settings > System > About and read System type. Download the matching build from the publisher.
Can compatibility mode fix every old program?
No. It cannot solve a wrong processor architecture, obsolete driver model or 16-bit executable on 64-bit Windows.
Is leaving S mode reversible?
No. Microsoft describes switching out of S mode as a one-way change.