Mac error 10661 usually appears when macOS cannot open an application or file through Launch Services, the system component that decides which app should launch and whether it is allowed to run. The message may look technical, but it often points to a practical problem: the app is incompatible, damaged, incorrectly installed, blocked by security settings, or unable to run on your Mac’s processor architecture.
TLDR: Mac error 10661 is most commonly related to an application that macOS cannot launch because it is incompatible, corrupted, incomplete, or not executable. Start by checking whether the app supports your macOS version and Mac processor, then update or reinstall it from a trusted source. If the app is trusted but still fails, check permissions, remove quarantine restrictions carefully, install Rosetta if needed, or reset Launch Services. Always avoid forcing unknown software to run, because this error can also appear when macOS is protecting you from unsafe or broken apps.
What Is Mac Error 10661?
Mac error 10661, often written as -10661, is associated with macOS Launch Services. Launch Services is responsible for opening apps, matching files with the correct applications, and verifying whether an executable file can actually run.
In plain language, the error means: macOS found something you tried to open, but it cannot launch it properly. This may happen when double-clicking an app, opening a document linked to a specific app, launching software from an external drive, or running an old program after a macOS upgrade.
You may see a message such as:
- “The application cannot be opened.”
- “LSOpenURLsWithRole() failed with error -10661.”
- “You can’t open the application because it may be damaged or incomplete.”
- “The application is not supported on this type of Mac.”
The exact wording can vary depending on your macOS version, the app involved, and whether the problem is caused by compatibility, permissions, security restrictions, or file damage.
Common Causes of Mac Error 10661
Although the error looks obscure, the underlying causes are usually familiar. The most common reasons include the following.
1. The App Is Not Compatible with Your macOS Version
One of the most frequent causes is software incompatibility. Older Mac apps may not work on newer macOS versions. For example, macOS Catalina and later no longer support 32-bit applications. If you try to open a 32-bit app on a modern version of macOS, it may fail with a Launch Services error.
This is also common after upgrading macOS. An app that worked yesterday may stop launching after a system update because its framework, installer, or executable is no longer supported.
2. The App Does Not Match Your Mac’s Processor
Modern Macs may use either Intel processors or Apple silicon chips, such as M1, M2, M3, or newer. Some older apps were built only for Intel Macs, while others may not have been properly updated for Apple silicon.
Many Intel apps can run on Apple silicon through Rosetta 2, Apple’s translation layer. However, if Rosetta is not installed, or if the app uses unsupported components, macOS may refuse to launch it.
3. The Application Is Damaged or Incomplete
Error 10661 can appear when an app bundle is missing important internal files. This may happen if the download was interrupted, the app was copied incorrectly, or files inside the application package were manually changed.
A Mac application may look like a single icon, but it is actually a folder-like bundle containing many internal files. If the main executable inside the bundle is missing or damaged, Launch Services cannot open it.
4. macOS Security Settings Are Blocking It
macOS includes multiple security systems, including Gatekeeper, notarization checks, quarantine flags, and privacy protections. If an app was downloaded from the internet and is unsigned, modified, or suspicious, macOS may block it.
This is an important safety feature. You should not automatically bypass macOS security warnings unless you are certain the app is legitimate and came from a trusted source.
5. File Permissions Are Incorrect
Applications need proper permissions in order to run. If the executable file inside the app bundle is not marked as executable, macOS may fail to launch it. This can happen after copying apps between drives, restoring from backups, using third-party archive tools, or moving files from network storage.
6. Launch Services Database Problems
Sometimes the problem is not the app itself but macOS’s record of which apps open which files. The Launch Services database can become confused, especially after migrations, app removals, or repeated installations of similar software. This is less common than app incompatibility, but it can contribute to error 10661.
How to Fix Mac Error 10661
Start with the safest and simplest fixes before using Terminal commands or changing security settings. The goal is to determine whether the app is incompatible, damaged, blocked, or incorrectly registered.
1. Restart Your Mac
A restart is basic, but it is worth doing first. It clears temporary Launch Services issues, releases stuck processes, and reloads system services.
- Click the Apple menu.
- Select Restart.
- After your Mac starts again, try opening the app.
If the error disappears, it may have been caused by a temporary process or system cache issue.
2. Check Whether the App Is Compatible
Before changing anything else, confirm that the app supports your Mac.
- Check the developer’s website for supported macOS versions.
- Look for separate downloads for Intel and Apple silicon.
- Make sure the app is not an old 32-bit application if you use macOS Catalina or later.
- If the app is discontinued, look for an actively maintained replacement.
To check your macOS version, go to Apple menu > About This Mac. This screen also shows whether your Mac uses Apple silicon or an Intel processor.
3. Update the Application
If the app is outdated, install the latest version. Do not rely only on an old installer you saved years ago. Download the current version directly from the developer or from the Mac App Store.
If the application includes an updater, you can try using it, but if the app will not open at all, the better approach is usually to download a fresh installer.
4. Reinstall the App from a Trusted Source
A clean reinstall can fix damaged or incomplete app bundles.
- Quit the app if it is partially open.
- Move the app from the Applications folder to the Trash.
- Restart your Mac.
- Download a fresh copy from the official source.
- Install it again and try opening it.
Be cautious with apps downloaded from unofficial mirrors, file-sharing sites, or unknown archives. A modified app may fail to launch because it is damaged, unsigned, or unsafe.
5. Install Rosetta 2 on Apple Silicon Macs
If you are using an Apple silicon Mac and the app was built for Intel, macOS may prompt you to install Rosetta automatically. If it does not, you can install it manually through Terminal.
Open Terminal and run:
softwareupdate --install-rosettaFollow the prompts, then try opening the application again. Rosetta is safe and provided by Apple, but it only helps with compatible Intel apps. It will not make very old PowerPC apps or unsupported 32-bit apps work on current macOS versions.
6. Check App Permissions
If the app was copied from another drive or restored from a backup, permission problems may prevent it from launching. First, try moving the app into the main Applications folder rather than running it from Downloads, an external drive, or a network location.
If you are comfortable using Terminal, you can check whether the main executable has permission to run. Control-click the app, choose Show Package Contents, then look inside Contents > MacOS. The file there is usually the app’s executable.
For a trusted app, you may repair execute permission with a command like:
chmod +x /Applications/AppName.app/Contents/MacOS/AppNameReplace AppName with the correct application and executable name. Use this carefully. Do not grant execute permissions to unknown or suspicious files.
7. Review Gatekeeper and Privacy Warnings
If macOS says the app cannot be opened because it is from an unidentified developer, go to System Settings > Privacy & Security. You may see an option to allow the blocked app.
Only approve the app if you trust its source. A reputable developer should provide a signed and notarized version of the software. If the app is unsigned and the developer cannot explain why, consider that a warning sign.
Some advice online recommends removing the quarantine attribute with Terminal. While that can work, it should be treated as an advanced step, not a routine fix. If you are certain the app is safe, the command structure is:
xattr -dr com.apple.quarantine /Applications/AppName.appAgain, replace AppName with the real app name. Do not use this command on software from unverified sources.
8. Reset the Launch Services Database
If error 10661 appears when opening certain file types, or if your Mac is confused about which app should open a document, resetting Launch Services may help.
Open Terminal and run:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain userThen restart your Mac. This rebuilds the database macOS uses to associate files and applications. It will not fix an app that is truly incompatible, but it can resolve broken launch associations.
9. Try Safe Mode
Safe Mode starts macOS with minimal extensions and performs certain system checks. It can help identify whether login items, extensions, or background tools are interfering with app launches.
On Apple silicon Macs, shut down, press and hold the power button until startup options appear, select your disk, hold Shift, and choose Continue in Safe Mode. On Intel Macs, restart and hold Shift during startup.
If the app opens in Safe Mode but not normally, review login items and recently installed utilities.
When the App Simply Cannot Be Fixed
Sometimes Mac error 10661 means the app is too old to run on your current system. This is common with legacy business tools, old games, PowerPC applications, and 32-bit software.
Your options may include:
- Finding a modern version of the same app.
- Using an alternative application that supports the same file format.
- Running an older macOS version on a separate compatible Mac.
- Using virtualization, if licensing and technical requirements allow it.
- Contacting the developer for an updated build.
Avoid downgrading your main Mac or disabling security protections just to run outdated software unless there is a clear professional need and you understand the risks.
How to Prevent Error 10661 in the Future
- Keep apps updated before upgrading macOS.
- Download software only from trusted sources, preferably the developer or Mac App Store.
- Check compatibility notes before moving to a major new macOS release.
- Avoid modifying app bundles unless instructed by the developer.
- Maintain backups with Time Machine or another reliable backup system.
- Keep installers and license information for important professional software.
Final Thoughts
Mac error 10661 is not usually a sign of a failing Mac. It is most often a launch problem involving compatibility, security, permissions, or a damaged application. The best fix is to identify why macOS refuses to open the app rather than forcing it to run.
Begin with updates, compatibility checks, and a clean reinstall. If needed, proceed to Rosetta, permissions, Gatekeeper review, or Launch Services repair. If the software is genuinely outdated, replacing it with a supported version is usually the safest and most reliable long-term solution.
