Compatibility is about the whole task
For Windows and Mac apps that will not install, open or complete a required function on the intended setup. The goal is a supported practical route, not making every old app run at any cost. Preserve important data and the only working device while checking.
Step 1 of 8
In this guide
Record the exact app, platform and failure
Record the exact app, platform and failure
Record the app’s full name, edition and version, the OS version and the computer’s processor/platform. On Windows, Settings, System, About shows system type; on Mac, About This Mac identifies the chip or processor and macOS version. Do not assume two computers are equivalent because both say Windows or Mac.
Note whether installation fails, the app will not open, one plug-in is unavailable, an old file will not open or an attached device lacks a feature. Keep the exact error and when it began, such as after an OS update or move to another computer. These need different checks.
Keep the original app, installer/purchase records and important data intact. If this is managed work equipment, involve the responsible administrator before changing the environment. Do not guess an unsupported download based on a similar product name.
Keep the exact version/platform/error together so compatibility can be checked rather than guessed.
Next: Match the app’s published system requirementsMatch the app’s published system requirements
Match the app’s published system requirements
Open the genuine publisher’s support page for the exact version. Compare supported OS releases, processor architecture, memory, storage, graphics and required connected devices. Minimum requirements and a tested supported configuration are different; meeting a memory figure alone does not establish compatibility.
For a Windows ARM-based computer, check the app and any driver-dependent functions specifically. Microsoft explains ARM app and driver limits: application emulation is not a replacement for a compatible hardware or low-level driver. Do not force an x64 driver onto ARM or assume every app that opens supports every feature.
Check whether the publisher provides a current supported build for your system and whether your entitlement covers it. If not, keep the old working setup while you ask about a supported alternative. More storage, a compatibility checkbox or an unofficial installer cannot change an unsupported processor or driver requirement.
Keep the exact supported-versus-unsupported requirement. Do not buy an upgrade or weaken protection from a guess.
Check Mac app architecture and current support
Check Mac app architecture and current support
In Finder, select the app and choose File, Get Info. The Kind field can identify an Intel, Universal or Apple silicon app. Compare that with the Mac’s actual processor and the developer’s current supported version. A separate plug-in or helper can have different requirements from the main app.
Apple’s current Rosetta guidance describes supported Intel apps on Apple silicon and the transition away from that support. Do not treat Rosetta as a permanent universal fix. Prefer the developer’s supported Universal/Apple silicon version where available and check any included extensions or updater separately.
Old 32-bit Mac apps do not run on macOS Catalina 10.15 or later. Rosetta for Apple silicon does not make that old 32-bit app supported. Do not downgrade macOS, remove security checks or replace important app files to force it. Preserve the existing data and ask the developer about supported conversion or replacement.
Use the exact app/component architecture and current Apple/developer support limits, not the Mac label alone.
More checks5 detailed checks
Check plug-ins, files and device drivers
Check plug-ins, files and device drivers
List required add-ins, plug-ins, fonts, local databases, licence dongles, scanners, audio interfaces or other devices. Check the publisher’s compatibility statement for each critical component and its exact version. Do not update a central work app before checking an add-in it depends on.
For example, Microsoft documents 32-bit and 64-bit Office/add-in distinctions. A 64-bit Windows computer can still have a workflow whose installed Office architecture matters. Do not switch Office editions blindly; preserve the current installation, data and required components while the supported path is agreed.
Use a harmless copy of a representative file, never the only original, to check the needed format or function. A newer app may change a file or require conversion. A peripheral may need a supported driver rather than another app installer; use the supported driver guide when that is the specific issue.
Keep the whole required workflow in view. A successful launch alone does not validate files, add-ons or devices.
Respond to the specific message without bypassing security
Respond to the specific message without bypassing security
Read and record the actual message: wrong platform, missing component, activation, unsupported version, blocked publisher or workplace policy. Confirm the source is the genuine publisher/store and the package matches the intended product. Do not treat every installation failure as a reason to run as administrator.
For a trusted older Windows desktop app, the current Program Compatibility troubleshooter in Get Help may provide a targeted supported check. Read its proposed changes and test a harmless task. It cannot supply a missing supported driver or make an unsupported platform officially supported.
If security, device management or a publisher warning blocks the package, ask the responsible IT team/developer about the exact warning. Do not turn off endpoint protection, signature checks, Gatekeeper, secure boot or required isolation to make it run. Avoid random DLL downloads, registry fixes or emulation packages from search adverts.
Keep the exact warning and supported finding. Do not confuse bypassing a warning with establishing compatibility.
Plan a supported update or alternative
Plan a supported update or alternative
Confirm the exact supported app/component version, genuine download and legitimate entitlement. Check backups/exports, plug-in settings and any activation limit before uninstalling or deactivating the only working copy. If purchase records are missing, keep the working setup and ask the original publisher or administrator.
Use the installation and configuration guide for an agreed supported change. Change one relevant component at a time where the documented process permits it, and retain original data until the required task is tested.
If the app is discontinued or depends on unsupported hardware/OS, discuss a supported replacement, file conversion or professionally assessed transitional workflow. Do not assume a virtual machine, OS downgrade or old offline computer is automatically safe, licensed or compatible. Agree data migration and ongoing limitations before a business-critical switch.
Keep the original data and working route until the proposed replacement is tested and its limits are understood.
Test the required task with a copy
Test the required task with a copy
Use a non-sensitive copy of a representative document or project. Open it, perform the required harmless action and save to a separate test location. Check the result in the intended app/version without overwriting the original. If conversion is involved, verify the content and required features rather than just the filename.
Test the actual add-in, device or export feature involved, using a simple sample rather than customer records or a live production job. Check relevant accessibility functions still work. Record the app/component/OS combination and whether the original error returns after a normal reopen.
If the intended task now works on a supported setup, stop changing compatibility settings. If only part works, record the limitation and keep the original workflow available where safe. A partial result is not a reason to delete the old files or declare every project compatible.
Keep the tested supported configuration and original files. Unresolved required features need a targeted decision.
Back to the symptom checkerWhen should you get help with compatibility?
When should you get help with compatibility?
Get help when the app is essential, the old computer is the only working copy, the required version is unavailable, a driver/plug-in is unsupported or the next step would weaken security or risk valuable data. Keep product/edition/version, OS/processor, error wording and the specific required feature together.
Our software troubleshooting support can help compare published requirements, preserve the existing setup and assess a practical supported route. The publisher or administrator may need to confirm entitlement, component support and migration options.
Do not send passwords, product keys, MFA codes or entire customer projects as a first report. Use an agreed private channel and the smallest relevant example. We cannot promise every old app will run or make unsupported software supported by changing a setting.
Keep evidence, original data and legitimate access intact while the supported options are assessed.
Book IT support
