Suitable: If you need to diagnose MAXQDA 26.4 on macOS 27, keep your project and error evidence safe, then check installation, permissions, the MAXQDA user folder, and a project copy in that order.
Not suitable: If the goal is to prove that every research workflow works simply because the system is listed as supported; published support does not guarantee a particular device, account, or project will work without faults.
This guide is for graduate and doctoral researchers whose installation will not launch and whose research progress depends on a working setup.
It also covers qualitative researchers who can open the app but cannot load a project, and university support staff who need a reversible, evidence-based diagnosis.
Last updated October 2, 2026; version and support details checked against MAXQDA system requirements, MAXQDA release notes, and its troubleshooting documentation.
00Check the published support boundary first
MAXQDA’s current system requirements list MAXQDA 26.0 or later as supported on macOS 27, and list Apple Silicon desktop and laptop processors as supported. The release notes show that MAXQDA 26.4 was updated on August 19, 2026. These are the documented compatibility and release facts; they do not establish that a specific installation, permission state, license, or research project has been tested successfully. See the official system requirements and release notes.
Before changing anything, identify what is actually failing. “MAXQDA does not work” can describe an app that does not start, an activation issue, or a project that fails after the app opens. These point to different parts of the setup, so treating them as one problem can lead to unnecessary reinstalls or risky changes to project files.
| What you see | First area to investigate | Safe way to narrow it down |
|---|---|---|
| Clicking the app icon produces a macOS warning | Installation source or macOS security prompt | Record the warning exactly; check the installation source and follow Apple’s instructions for opening a Mac app safely. |
| The app appears to do nothing or closes during startup | App installation, permissions, or the MAXQDA user folder | Check the installed version and follow MAXQDA’s startup guidance before changing stored data. |
| MAXQDA opens, but one project will not load | Project file, version conversion, or linked media | Test a copy, preserve the original, and record whether other projects open. |
| A folder access message appears | Access to a required MAXQDA folder | Keep the full message and consult MAXQDA’s instructions for the specific access error. |
If the app shows a security alert, do not disable Gatekeeper or bypass a university device policy to make the warning disappear. Apple’s guidance for opening apps safely on a Mac provides the supported context for handling security prompts. If the Mac is managed by your institution, ask its administrator before changing an access setting.
01Preserve evidence before changing the installation
A useful diagnosis should be repeatable. Before reinstalling, resetting preferences, or moving project data, write down the macOS version, MAXQDA version, Mac processor type, installation source, and the exact action that triggered the failure. Attach a screenshot or copy the full error message if available. Record whether the failure occurs at startup, activation, project opening, or a later task.
Then protect the research material. Confirm that the project file has a separate, accessible backup, and check whether the project uses external media stored outside the project file. A project copy on the same device is not a safe backup if the device or storage is unavailable. Keep an unchanged original and use a clearly named working copy for tests.
| Diagnostic route | Best fit | What it can establish | Main limitation |
|---|---|---|---|
| Check the existing Mac and app | The current installation is available and you can record its exact state | Whether the failure can be reproduced on that setup and at what stage | A successful launch does not confirm that every project or linked media item works. |
| Ask campus IT to check the managed Mac | A warning, access restriction, or policy may be involved | Whether device management or account permissions affect access | Administrator approval may be needed before settings can be changed. |
| Reproduce with a sanitized project copy on another Mac | No suitable Mac is available locally, or you need a separate test environment | Whether the same action fails in a second environment | A successful reproduction or launch is not project acceptance; it does not prove the original files, media, or workflow are complete. |
Choose the route that answers the next diagnostic question. Do not change several variables at once: if a reinstall, a permission change, and a project conversion all happen together, the result cannot show which change mattered.
02Check the first launch and any system prompt
If clicking the icon produces a warning, save its exact wording before dismissing it. Confirm where the app came from and whether the installed version matches the version being investigated. Compare the app and macOS versions with MAXQDA’s published requirements rather than relying on an older troubleshooting note or a colleague’s different Mac.
If there is no visible warning, follow MAXQDA’s troubleshooting steps for an app that no longer starts. Its guidance identifies system version, permissions, and the user folder as areas to check. Follow the applicable steps as written, and keep a record of what you checked and what happened after each change.
Keep the system protection in place. A warning is evidence to investigate, not a reason to weaken macOS security. If the app or device is subject to university policy, ask the responsible administrator before approving access or changing a managed setting.
Separate an application-start failure from activation trouble. If MAXQDA opens but reports an activation problem, document that message and the account or license context for the relevant support team. Reinstalling the app will not, by itself, establish that an account or license issue has been resolved.
03Inspect permissions and the MAXQDA user folder
When an error refers to folders required by MAXQDA, preserve the full message and note when it appears. MAXQDA provides a specific support article for user-folder access errors. Use that article to identify the folder and follow its instructions; do not infer that the project itself is damaged just because the app cannot access a required location.
Check whether the application has the file access it needs under the current macOS account. A setting that works for one account may not apply to another, and a university-managed Mac may restrict changes. If permission controls are locked or a policy message appears, stop and contact campus IT rather than trying to work around the restriction.
The MAXQDA user folder is different from a project file. Its absence, incomplete contents, or access restrictions may affect startup or other app operations, but deleting it without a backup can remove useful application data and make the original fault harder to diagnose. MAXQDA’s startup and folder-error guidance should determine what to inspect and how to recover; do not substitute a generic “reset the app” procedure.
Use this short check before any repair:
- [ ] Copy the exact folder or permission error into your incident notes.
- [ ] Confirm which macOS account is running MAXQDA.
- [ ] Check whether the Mac is managed by the university or laboratory.
- [ ] Locate the user-folder instructions that match the observed error.
- [ ] Back up relevant existing folder contents before a support-directed repair.
- [ ] Record the result of each change separately.
04Use the FAQ to resolve the common support questions
Is MAXQDA 26.4 supported on macOS 27?
MAXQDA’s published requirements list MAXQDA 26.0 or later as supported on macOS 27 and list Apple Silicon desktop and laptop processors as supported. The release notes identify MAXQDA 26.4 as an update dated August 19, 2026. That answers the published support question, not whether a particular project, permission setup, or device will work without issues. Check the current official pages before making a migration decision.
What should you do if clicking the app icon has no effect?
First distinguish a silent failure from a security alert, activation prompt, or brief launch followed by a close. Record what happens and confirm the macOS and MAXQDA versions. Then use MAXQDA’s startup troubleshooting guidance to inspect the installation, permissions, and user folder. Keep security protections enabled, and ask a university administrator before changing settings on a managed Mac.
Can a missing MAXQDA user folder prevent the app from working?
An inaccessible or incomplete required folder can be relevant to a startup or folder-access error, but the error alone does not prove why the folder is unavailable. Preserve the message, identify the folder using MAXQDA’s support instructions, and back up existing contents before following a repair procedure. Avoid deleting or replacing the folder based on a guess, especially on a managed university device.
How can you separate an older-project issue from an app issue?
Test the app with a separate copy of the project and record whether another project opens. Check whether the affected file comes from an older MAXQDA version and whether it references external media. MAXQDA explains how to open projects from older versions; retain the original file before conversion and compare results using the copy.
05Test the project without risking the original
If the app launches but a project does not, stop using the original as a test file. Make a separate copy and record where it is stored. MAXQDA’s guidance on where to save a project file can help you choose a suitable location for the test. Keep any external audio, video, image, or other referenced material available in the expected location.
Use a controlled comparison:
- Open the copied project and note whether the failure occurs before or after any conversion prompt.
- If an older project is involved, follow MAXQDA’s instructions for opening projects from older versions. Keep the original untouched.
- If the error refers to external media, check the recorded paths and whether those files are available to the account opening the copy.
- If another project opens, record that difference. It narrows the investigation but does not prove that every other project is healthy.
- If the copied project still fails, save the exact message and the step that triggers it before contacting support.
Do not treat a successful app launch as proof that the research data is ready for use. Project acceptance also depends on the project file, any version conversion, external media, and the workflow the researcher needs. Record these separately so a support specialist can distinguish an application issue from a project-specific one.
06Decide whether to continue, pause, or reproduce elsewhere
Continue using the setup only when the app starts, the relevant project copy opens, and the research workflow needed for the immediate task has been checked. If the app remains unable to start, a required folder is inaccessible, or a project copy fails, pause migration and assemble the evidence before contacting MAXQDA support or university IT.
A useful support packet contains the recorded software and system versions, the exact warning or error, the installation source, the checks already performed, and whether the failure affects the app, one project, or linked media. Include a sanitized project copy only if your institution’s data rules allow it. Remove participant identifiers and confidential material before sharing research files; when in doubt, ask the university’s data-protection or research-support staff first.
If the laboratory has no usable Mac, a remote Mac can help reproduce a startup issue using a sanitized copy, without treating that test as approval to migrate the real research archive. Confirm that the remote environment meets the requirements of your institution and project, and keep sensitive data out unless the relevant policies permit it. NUKCLOUD’s remote Mac options may be worth reviewing when a temporary Mac test environment is needed; an existing campus Mac or a locally owned Mac may be a better fit for ongoing work or workflows that depend on physical equipment.
For a broader view of available environments, review NUKCLOUD’s Mac environment options before choosing a test route. The decision should follow the evidence: continue if the required app and project-copy checks pass, pause if the cause remains unclear, and use a separate environment only when it can answer a specific unresolved question.