AAE 35 error usually points to drive naming or access problems in Pro Tools, and you can fix it by tidying disk names, permissions, and settings.
What AAE Error 35 Means In Pro Tools
When AAE Error 35 appears, Pro Tools is telling you that it cannot talk to a drive or folder in a safe way. The software expects every disk and session name to follow strict rules, and this message shows up when those rules are broken.
On macOS systems the code often relates to two specific issues. One is duplicate drive names, where two internal or external disks share the same label. The other is the use of characters that the operating system does not allow in drive, folder, or file names. In both cases Pro Tools can no longer resolve paths cleanly, so it stops playback or blocks the session from opening to avoid data loss.
In newer versions, users also run into this error when the operating system does not grant full access to audio locations. If the app does not have permission to read and write on the session disk, it can show the same message even though your naming looks fine. That is why the best fix plan checks both disk naming and access rights.
AAE 35 also sits in a small family of disk related AAE codes that behave in similar ways during everyday work. Codes such as AAE 2 or older DAE 35 messages tend to show up when two drives share a label, while this one leans more toward bad characters or paths that have become hard for the engine to follow on large multitrack sessions.
AAE 35 Error Fix Steps For Pro Tools Sessions
Before you change settings, note when AAE Error 35 shows up. Some users see it while launching the app, others while opening a single project, and some only when pressing play. That context helps you decide whether the problem sits with Pro Tools itself, one specific session, or a particular drive.
Run through these short checks first. They cover the quick wins that clear the error for many engineers and producers without a full reinstall.
- Restart Pro Tools And The Computer Close all sessions, quit the app, reboot the system, then try the same project again.
- Test With A Fresh Session On The System Drive Create a new blank session on your internal system disk to see whether the code appears only with one external drive or project.
- Disconnect Unused External Drives Unmount any backup or sample disks that are not needed for the current work and test again.
- Note Any Recent Changes Think about new plug-ins, a macOS update, or a new interface driver that you installed shortly before the error began.
While you run these checks, keep notes about which step changes the behaviour of the error. If a reboot alone clears the message, the cause was likely a temporary glitch in the operating system. If the code only drops away when you disconnect a certain drive, you already have a strong hint about which device needs more attention during late night editing sessions too.
If the message still pops up after these checks, move on to drive naming and permissions, as that is where this error usually starts.
Check Drive Names And Illegal Characters
Most AAE 35 reports trace back to drive labels and file names that Pro Tools cannot parse cleanly. The engine expects every storage device and project path to have a unique, simple name. When macOS sees two disks with the same title, or a title that includes restricted symbols, the audio engine can fail in the middle of playback or while loading a session.
Check each attached drive in Finder or File Explorer and make sure none of them share the same label. On macOS, open a Finder window, select each drive in the sidebar, and rename any duplicates with clear titles such as Audio_Projects_1 and Audio_Projects_2. Keep the names short and avoid symbols that are known to cause issues.
Pro Tools documentation and forum posts warn against a set of restricted characters in drive, folder, and file names. These symbols can break paths and should never appear in audio session names or media folders.
| Restricted Character | Where It Causes Trouble | Safe Replacement |
|---|---|---|
| * | ” : < > ? / \\ | Drive labels, session names, audio file names | Underscore, dash, or plain letters and numbers |
| Extra spaces at start or end | Folder names inside the session directory | Trim spaces and keep a single space between words |
| Overly long names | Nested folders on external drives | Short, clear names under thirty characters |
After you tidy these names, eject and reconnect external drives, then restart Pro Tools. Open the same project again and watch for the error. If it no longer appears, you have confirmed that the disk naming rules were the root of the problem.
If you rely heavily on removable media, treat those drives as part of your studio, not as casual storage. Cheap thumb drives or older spinning disks tend to drop connection briefly under load, which can push the audio engine into this error state. Use sturdy cables, powered hubs, and drives that are rated for long recording sessions, often in busy mix or tracking days.
Confirm Permissions, Playback Engine, And Disk Access
Even with clean disk names, this code can show up when the application does not have full permission to read and write on your audio drive. This often happens on macOS after a major system update or a new user account, where the app needs explicit approval before it can touch external storage.
- Grant Full Disk Access On macOS In System Settings, open the Privacy section, choose Full Disk Access, and make sure Pro Tools is listed and enabled. If it is missing, add it from the Applications folder, then relaunch the app.
- Check Folder Permissions On The Session Disk Locate your session folder, open the info or properties panel, and verify that your user account has read and write access. Apply the same rights to enclosed items so that audio files and fades stay writable.
- Pick The Right Playback Engine While Pro Tools starts, hold the N key on your keyboard to bring up the playback engine chooser. Select your main interface or output device rather than a leftover driver from a disconnected device.
- Test With A Local Copy Of The Session If you store projects on a removable or network drive, copy the full session folder to the internal system disk and open it there. When the error disappears on the local copy, you know the external disk or connection is part of the issue.
On Windows machines the same ideas apply, even though the interface panes look different. Grant the app full control over the session folder, avoid network shares for active recording work, and make sure that security software is not blocking the audio engine from reading or writing media files.
Many editors keep large sample libraries on separate volumes or network storage, which can add a subtle source of risk for this code. When those libraries sleep, spin down, or pause for a network handshake, the audio engine can stall. Keeping active libraries on a fast local drive shortens load times and reduces the chance of path errors mid session during cue work days.
Clean Pro Tools Caches And Problem Plug-Ins
Sometimes the code does not tie directly to a drive, but to a plug-in or cache that fails during launch or playback. Removing damaged preferences and testing your plug-in set can rule out these hidden triggers. This step takes a little more time, yet it often cures stubborn behaviour that survives restarts and simple drive fixes.
Treat this cleaning step as a short lab session rather than guesswork. Change one element at a time and test again so you do not chase ghosts. If the error appears on one machine but not on another with the same session and plug-in set, you have strong evidence that the fault lies with the host system instead of the project on your bench.
- Trash Pro Tools Preferences Safely Use a dedicated helper tool or follow the manual steps from Avid to remove preference files, databases, and waveform caches while leaving sessions and plug-ins in place.
- Move Third Party Plug-Ins Out Temporarily Create a folder on the desktop, move all non stock plug-ins from the plug-ins directory into that folder, then launch the app and test a simple session.
- Add Plug-Ins Back In Small Groups Restore a handful of plug-ins at a time, testing between each batch until the error returns. The last group that you moved back usually contains the troublemaker.
- Update Or Remove The Faulty Plug-In Once you find the plug-in that triggers the message, install the latest version from the vendor or remove it from your main rig and keep it off any new sessions.
If none of the plug-ins trigger the problem, reinstall the Pro Tools application from a fresh installer. Before you do that, export your I/O and playback engine settings so that it is easier to bring the system back to your normal layout once the reinstall is complete.
Prevent Error 35 In Later Sessions
A little care when you set up disks and sessions can stop this code from returning in busy production weeks. The goal is to keep your storage simple, clean, and stable so that the engine always finds exactly the paths it expects.
- Use Clear, Simple Drive Names Label each audio, sample, and backup drive with distinct titles that avoid symbols and stay easy to recognise in dialogs.
- Keep One Active Session Per Drive At A Time When tracking, point Pro Tools to a single, fast audio drive instead of splitting tracks across several disks.
- Run Regular Disk Health Checks Use built in tools such as Disk Utility or chkdsk to scan for errors on your audio drives and fix them before sessions fail.
- Avoid Recording Directly To Cloud Synced Folders Store live sessions on a local disk and only sync completed work to a cloud folder once the job is safely backed up.
- Document Your Working Setup Keep a short note of which interface, driver versions, and plug-in lists work well together so you can return to that setup after system updates.
Good backup habits also soften the impact if this error ever appears during a paying job. Keep at least one clone of your main audio drive and a separate backup of session folders on another physical disk. When something goes wrong, you can bring a clean copy online without touching the broken volume until you have time to inspect it in a calm way.
Once you have cleared the current issue and put these habits in place, this error code should become a rare event. When it does appear again, you will know to check drive names, disk access, and plug-ins first instead of losing hours to guesswork in the middle of a session.