Pro Tools common problems share a small set of causes: plugins, preferences, playback engine settings, and licensing. Almost every error you see maps back to one of those four.
The fixes below are ordered by how often each problem shows up. Some stop the program, others just slow you down. Start at the top, test after each fix, and most sessions come back to life in minutes.
Key Takeaways
- The AAE 9173 CPU overload error usually means a plugin or a buffer setting, not a weak computer.
- Pro Tools failing to launch is almost always a plugin or a corrupt preferences file.
- Trashing preferences fixes a surprising number of Pro Tools problems, and it never touches your sessions.
- Every current Pro Tools version needs an iLok account, either on a USB stick or in the cloud.
Pro Tools common problems at a glance: 11 quick fixes
| Problem | Most likely cause | Quick fix |
|---|---|---|
| Won’t open or launch | Plugin or corrupt preferences | Move plugins out, then trash preferences |
| AAE 9173 CPU overload | Buffer too small or a heavy plugin | Raise the buffer, test plugins, commit tracks |
| AAE 6101 error | Hardware conflict | Raise the buffer, disable Wi-Fi, update drivers |
| AAE 6117 error | Sample rate or clock mismatch | Match the session sample rate to the interface |
| AAE 9073 disk error | Drive too slow or busy | Increase disk cache, consolidate regions |
| No sound | Wrong playback engine | Select the interface in Playback Engine |
| High latency | Large hardware buffer | Lower the buffer for recording |
| iLok problems | License Manager or USB port | Sync licenses, try another port, reactivate |
| Crash while scanning plugins | Incompatible AAX plugin | Move plugins to the unused folder in batches |
| Crash when saving | Plugin in the session | Test plugins, update everything |
| Video engine problems | Video engine enabled | Disable the video engine in Playback Engine |
1. Pro Tools won’t open or launch
Pro Tools shows the splash screen and then disappears, or nothing happens at all when you click it. A plugin or a corrupt preferences file is behind almost every case.
Fix 1: Move all third-party plugins out. Go to the Pro Tools Plug-Ins folder and move everything to a temporary folder. Launch Pro Tools to see if it opens.
If it opens, a plugin is the cause. Add plugins back in small batches until the launch fails.
Fix 2: Trash your preferences. On Windows, rename the Avid folder under AppData, Roaming. On macOS, delete the Pro Tools folder under Library, Preferences, Avid.
Pro Tools rebuilds these files on the next launch.
Fix 3: Pick a playback engine at launch. Hold the N key while Pro Tools starts. This opens the Playback Engine dialog, where you can choose built-in audio or ASIO4ALL before the session loads.
Fix 4: Create a new admin user. If Pro Tools launches from a fresh user account, the problem lives in your user profile rather than the program. If it still fails, do a clean uninstall and reinstall.
2. AAE 9173: Pro Tools ran out of CPU power
AAE 9173 stops playback with a message about CPU power, even on sessions that look light. This is the most reported Pro Tools error, and it is rarely about raw CPU strength.
Fix 1: Raise the hardware buffer. Open Setup, Playback Engine, and increase the hardware buffer size to 1024 samples. This gives the CPU more time to process each buffer.
Fix 2: Turn off dynamic plugin processing. In Playback Engine, untick Dynamic Plug-in Processing. This stops Pro Tools from scaling plugin load, which is a known 9173 trigger.
Fix 3: Test with plugins disabled. Hold Shift while Pro Tools launches to skip all third-party plugins. If the session runs, one plugin is the culprit.
The Click II plugin has a long history of causing 9173 errors.
Fix 4: Commit or freeze heavy tracks. Print CPU-heavy tracks to audio with Commit. This removes the plugin load from real-time processing.
Fix 5: Raise the disk cache. In Playback Engine, set the disk cache to 2 to 4 GB. This keeps audio in RAM and reduces the disk load that can trigger the error.
3. AAE 6101 error
AAE 6101 appears at launch or during playback and stops the audio engine. It points to a hardware conflict between Pro Tools and your audio device.
Fix 1: Raise the hardware buffer. A buffer that is too small is the most common trigger for 6101. Set it to 512 or 1024 samples in Playback Engine.
Fix 2: Disable Wi-Fi and Bluetooth. Wireless drivers interrupt the audio stream on many Macs. Switch them off and test again.
Fix 3: Remove old audio drivers. Drivers from interfaces you no longer use still load and conflict. Uninstall them completely.
Fix 4: Test with built-in output. Switch the playback engine to Built-in Output. If the error stops, the interface or its driver is the problem, and a reliable audio interface will fix it for good.
4. AAE 6117 error
AAE 6117 usually appears when Pro Tools cannot sync to the clock of your audio device. A sample rate mismatch between the session and the interface is the typical cause.
Fix 1: Match the sample rate. Check the session sample rate in Setup, Session. Set the interface to the same rate, or set the clock source in the interface control panel.
Fix 2: Restart the audio engine. Open Playback Engine, choose the computer’s own audio, then switch back to your interface. This resets the clock connection.
Fix 3: Check the cables. Loose or failing cables cause clock errors. Swap the cable and try a different port on the computer.
5. AAE 9073: disk too slow or busy
AAE 9073 stops playback with a message about the disk. Pro Tools could not read the audio fast enough. A slow drive or a drive doing other work is the cause.
Fix 1: Increase the disk cache. Set it to 2 to 4 GB in Playback Engine so more audio plays from RAM instead of the drive.
Fix 2: Use a separate SSD for sessions. Recording and playback belong on a fast internal or external SSD, not the system drive.
Fix 3: Stop background disk activity. Backups, sync tools, and downloads hammer the same drive. Pause them during a session.
Fix 4: Consolidate regions. Select the tracks and run Edit, Consolidate. This creates continuous audio files that read faster than thousands of small edits.
Pro tip
The plugin test is the most useful habit in Pro Tools. Move everything out of the Plug-Ins folder, confirm the launch, then add plugins back in batches. It finds the culprit in under an hour, every time.
6. No sound at all
The session plays but nothing comes out of your speakers. The transport moves, the meters bounce, and still silence. Playback engine settings are the usual cause.
Fix 1: Check the playback engine. Open Setup, Playback Engine, and confirm your interface is selected. If it points to a disconnected device, you get silence.
Fix 2: Check the hardware buffer. Some interfaces produce no output at certain buffer and sample rate combinations. Try 512 samples at 44100 Hz.
Fix 3: Check track output. Make sure the track output is not muted and routes to the main outputs. Solo buttons and inactive tracks are easy to miss.
Fix 4: Test built-in output. Switch the playback engine to Built-in Output, and listen through the computer speakers.
If sound appears, the interface or its driver is at fault. A reliable audio interface avoids this class of problem.
7. High latency when recording
You play a note and hear it a moment later. Recording becomes difficult when the delay grows. The hardware buffer controls most of this.
Fix 1: Lower the hardware buffer. Use 128 or 256 samples while recording. This cuts latency to a few milliseconds if your CPU copes.
Fix 2: Turn on low latency monitoring. In Options, tick Low Latency Monitoring. Pro Tools then mutes latency-heavy inserts while recording.
Fix 3: Use direct monitoring. Route the input straight to your headphones in the interface control panel. This bypasses Pro Tools completely for monitoring.
Fix 4: Trim the plugin chain. Heavy plugins on the record track add delay. Use light inserts while tracking and add the heavy processing later.
8. iLok and activation problems
Pro Tools suddenly reports a missing license, or your activations vanish overnight. iLok issues are frustrating because they lock you out of everything.
They are usually recoverable with the fixes below.
Fix 1: Open iLok License Manager. Sign in and check the license list. If the license is there but grayed out, the iLok is not connected or the cloud session expired.
Fix 2: Try another USB port. iLok USB keys are sensitive to flaky ports and hubs. Plug it directly into the computer.
Fix 3: Start a cloud session. If you use iLok Cloud, open License Manager and start a new cloud session before launching Pro Tools.
Fix 4: Trash preferences. A stale preferences file can hide a valid license. Rename the Avid preferences folder and relaunch.
Fix 5: Use the zero downtime activation. In License Manager, the Zero Down Time option lets you borrow a license for offline use when your internet is unreliable.
Pro tip
Treat preferences like a wear item. Trash them quarterly even when nothing is wrong. Pro Tools rebuilds them in seconds, and a whole class of strange bugs never gets a chance to settle in.
9. Crash while scanning plugins
Pro Tools crashes during the plugin scan at launch, usually partway through the list. An incompatible or corrupt AAX plugin is the cause.
Fix 1: Move plugins out in batches. Move half the plugins from the Plug-Ins folder and launch. If Pro Tools opens, the bad plugin is in the moved half.
Narrow it down from there.
Fix 2: Update everything. Most scan crashes come from plugins that are older than the current Pro Tools. Update each plugin from its developer’s site.
Fix 3: Clear the plugin database. On Windows, delete the AAX plugin cache files in the Avid data folder. Pro Tools rebuilds them on the next scan.
Fix 4: Reinstall the plugin. A corrupt install produces a crash that updates cannot fix. Reinstall the suspected plugin fresh.
10. Crash when saving or closing
Pro Tools crashes the moment you save or close a session. The session itself is usually fine, and the crash points to a plugin in that session.
Fix 1: Test the session without plugins. Hold Shift and open the session. If it saves cleanly, add plugins back until the crash returns.
Fix 2: Update the session plugins. A plugin with a known crash on save usually has a fixed version. Update it and test again.
Fix 3: Save as a new session. Use File, Save Copy In to write a fresh session file. This clears corruption in the original file.
11. Video engine problems
Pro Tools crashes or stutters when a video track is present. The video engine and the audio engine compete for the same resources, and a weak graphics setup loses.
Fix 1: Disable the video engine. In Playback Engine, untick Enable Video Engine. Audio keeps working normally while the video feature is off.
Fix 2: Use a lighter video codec. H.264 files are heavy for Pro Tools. Convert the video to DNxHD or ProRes for smoother playback.
Fix 3: Check the graphics driver. Outdated GPU drivers cause video engine crashes. Update the driver and test the session again.
How I verified these fixes
These fixes come from the Avid knowledge base, the DUC forums, and the most repeated solutions in the r/protools community. I checked each one against the current Pro Tools release before including it.
The plugin test is the most reliable method I know: move plugins out, confirm Pro Tools runs, then add them back in batches. It is slow, but it always finds the culprit.
Pro Tools menus stay consistent across versions. The paths in this guide match Pro Tools 2025 on Windows 11 and macOS.
How to avoid most Pro Tools problems
- Keep Pro Tools and every plugin updated. Most crash classes are fixed in updates.
- Use a separate SSD for sessions and keep the disk cache at 2 to 4 GB.
- Trash preferences once a quarter, even when nothing is wrong.
- Test new plugins in an empty session before using them in real work.
- Run the Avid system optimizations for your OS once and keep them that way.
When the fixes above do not work
If the list fails, do a clean uninstall and reinstall of Pro Tools. Remove the HD driver as well if prompted, then reinstall the latest version from your Avid account.
Avid support works best with details. Include the Pro Tools version, your OS, your interface, and a crash report in your ticket. The DUC forums also respond quickly to unusual errors.
If you are weighing Pro Tools against other options, our best DAWs for home studios guide covers the practical tradeoffs.
Frequently asked questions
Why does Pro Tools keep giving me the 9173 error?
AAE 9173 is a CPU overload error. Raise the hardware buffer to 1024 samples, turn off dynamic plugin processing, and test your sessions with third-party plugins disabled.
Why won’t Pro Tools open on my computer?
Move all third-party plugins out of the Plug-Ins folder and launch again. If it opens, add plugins back in batches. If not, trash your preferences and try the N-key playback engine trick at launch.
Do I need an iLok for Pro Tools?
Yes. Every current Pro Tools version requires an iLok account. You can use a USB iLok key or iLok Cloud, and both are managed through iLok License Manager.
How do I fix the AAE 6101 error?
AAE 6101 is a hardware conflict error. Raise the buffer size, disable Wi-Fi and Bluetooth, and remove old audio drivers. Testing with the computer’s own audio output isolates the device.
Why is there no sound in Pro Tools?
Check the playback engine device first, then the hardware buffer and sample rate. If those are right, verify the track outputs and the master fader.
Does Pro Tools work on a Mac?
Yes. Pro Tools runs natively on Apple Silicon and Intel Macs, and on Windows 10 and 11. Check Avid’s compatibility page for your exact version and OS before upgrading.
How do I lower latency in Pro Tools?
Lower the hardware buffer to 128 or 256 samples while recording. Turn on Low Latency Monitoring, and use your interface’s direct monitoring for the lowest delay.
The bottom line
Pro Tools is demanding software, but its problems are predictable. Most Pro Tools common problems trace back to plugins, preferences, the playback engine, or iLok. Fix those four areas and the errors stop coming back.
Where to go next
If your DAW still gives you trouble, the fixes are similar elsewhere. See FL Studio common problems, Cubase common problems, and Ableton Live common problems for the same issues in other software.
If you are weighing your options, our guide to choosing a DAW covers the decision. Our DAW mixing mistakes guide keeps your mixes clean once Pro Tools common problems are behind you.
