Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
When an audio plug-in is missing, fails validation, crashes a scan, or loads without audio, start by isolating the fault rather than changing every mixer setting. The usual causes are an incorrect scan path, a mismatched format, an incomplete or blocked installation, licensing or authorization trouble, an outdated plug-in, or an audio-device route that is not carrying signal. Record your DAW and operating-system versions, plug-in format and version, and whether the problem appears in a blank project. Then test one plug-in at a time, use the DAW’s built-in rescan or reset command, and only clear caches after those normal tools fail.
What should I check first when an audio plug-in fails?
Freeze the variables before changing anything. Write down the DAW and version, operating system, plug-in name and version, format (VST2, VST3, Audio Units or AAX), installation location, and whether the fault appears in a new, empty project. This record prevents a routing change, a second plug-in, or a different format from obscuring the original cause.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Close other audio applications that may be holding the interface or a license service.
- Use one format of a plug-in consistently in a project. Ableton specifically advises against inserting several formats of the same plug-in in one Set.
- Test the suspect plug-in by itself in a blank project or Set before changing a finished session.
- Keep the DAW, plug-in, licensing software and audio-interface driver on versions supported by the same operating system.
These checks separate a plug-in problem from a project, scan, license or hardware problem. If the plug-in is not listed at all, begin with installation and scan folders; if it is listed but silent, move to signal and device routing.
Why does my plug-in not appear in the DAW?
A missing entry almost always means the DAW did not scan the folder containing the installed file, scanned a different format, or rejected the plug-in during validation. Confirm the file exists, confirm the format you intend to use, then rescan the correct folder.
#1 Best Overall
- Pro performance with great pre-amps - Achieve a brighter recording thanks to the high performing mic pre-amps of the Scarlett 3rd Gen. A switchable Air mode will add extra clarity to your acoustic instruments when recording with your Solo 3rd Gen
- Get the perfect guitar and vocal take with - With two high-headroom instrument inputs to plug in your guitar or bass so that they shine through. Capture your voice and instruments without any unwanted clipping or distortion thanks to our Gain Halos
- Studio quality recording for your music & podcasts - Achieve pro sounding recordings with Scarlett 3rd Gen’s high-performance converters enabling you to record and mix at up to 24-bit/192kHz. Your recordings will retain all of their sonic qualities
- Low-noise for crystal clear listening - 2 low-noise balanced outputs provide clean audio playback with 3rd Gen. Hear all the nuances of your tracks or music from Spotify, Apple & Amazon Music. Plug-in headphones for private listening in high-fidelity
- Everything in the box: Includes Pro Tools Intro+, Ableton Live Lite, Cubase LE, and Hitmaker Expansion: a suite of essential effects, powerful software instruments, and easy-to-use mastering tools
How do I fix missing plug-ins in Ableton Live?
- Open Live’s plug-in preferences and enable the folder that actually contains the plug-in.
- Do not point the VST2 and VST3 custom-folder settings at the same directory. Keep each format in its own intended location.
- Wait for the normal scan to finish before judging whether the plug-in is absent.
- For a deeper scan, hold Alt on Windows or Option on macOS while clicking Rescan.
- Search the browser under the format you installed. A VST3 installation will not appear in a VST2-only location, and an Audio Unit will not appear in a VST list.
If the file is in the right folder but still missing, reinstall it with Live closed, restart Live, and repeat the deep rescan. Remove obsolete duplicate versions after confirming that existing projects no longer depend on them.
How do I fix missing Audio Units in Logic Pro?
- Open Logic Pro > Settings > Plug-in Manager and search for the plug-in.
- If it is absent from Plug-in Manager, reinstall the Audio Unit and restart Logic.
- If it is listed but unavailable in a project, select it and choose Reset & Rescan Selection.
- When several Audio Units disappear together, use Full Audio Unit Reset in Plug-in Manager, then reopen Logic.
Logic may continue scanning after an update even when the window appears paused. An updated scan can take 10 minutes or more, particularly when an expired demo or a USB license-dongle prompt is waiting for attention.
What should I do when an AAX plug-in is missing in Pro Tools?
Verify that the AAX build was installed, rather than only a VST or Audio Unit build, and restart Pro Tools after installation. If Pro Tools still does not list it, use its plug-in-management and rescan controls before removing cache files. For Pro Tools 2023.12 and later, Arturia documents the AAX cache locations as /Users/Shared/Pro Tools/AAXPluginCache/ on macOS and C:UsersPublicPro ToolsAAXPlugInCache on Windows; use those locations only when ordinary rescan and reset tools have failed.
How do I choose the correct plug-in format?
Formats are separate plug-in builds, not interchangeable labels. A DAW scans only the formats it supports and the folders assigned to those formats.
| Format | Where it is normally used | What a mismatch looks like |
|---|---|---|
| VST2 | DAWs that expose a VST2 scan path | The plug-in is installed but absent when only a VST3 folder is scanned |
| VST3 | DAWs with VST3 support and a VST3 scan path | A VST3 file does not appear in a VST2 browser or custom VST2 folder |
| Audio Units (AU) | Logic Pro and other macOS hosts that scan Audio Units | Logic lists the component as failed or does not list it at all |
| AAX | Pro Tools | A VST or AU installation is present, but Pro Tools has no AAX plug-in to load |
Choose one format for a given Ableton Set instead of alternating VST2 and VST3 instances of the same effect. Consistency reduces duplicate browser entries and prevents a project from depending on two different plug-in binaries.
Rank #2
- The new generation of the songwriter's interface: Plug in your mic and guitar and let Scarlett Solo 4th Gen bring big studio sound to wherever you make music
- Studio-quality sound: With a huge 120dB dynamic range, the newest generation of Scarlett uses the same converters as Focusrite’s flagship interfaces, found in the world's biggest studios
- Find your signature sound: Scarlett 4th Gen's improved Air mode lifts vocals and guitars to the front of the mix, adding musical presence and rich harmonic drive to your recordings
- All you need to record, mix and master your music: Includes industry-leading recording software and a full collection of record-making plugins
- Everything in the box: Includes Pro Tools Intro+, Ableton Live Lite, Cubase LE, and Hitmaker Expansion: a suite of essential effects, powerful software instruments, and easy-to-use mastering tools
What should I do when plug-in validation or authorization fails?
Validation failure means the host could not safely load the plug-in, while authorization failure means the license or its connection was not accepted. Check compatibility and licensing before repeatedly rescanning.
Check compatibility before reinstalling
- Compare the plug-in’s supported operating systems and DAW versions with your installed versions.
- Update the plug-in to a build that supports the current OS and host.
- Remove obsolete or duplicate builds that may be selected instead of the current one.
- Restart the computer after an OS, DAW, plug-in or driver update so background services load cleanly.
Check activation and license connections
Activate the license using the developer’s documented method. If the plug-in uses iLok licensing, update iLok License Manager and confirm that the license is activated to a valid location. A disconnected iLok USB, an invalid activation, or running the installer while the DAW is open can cause a plug-in to be blocklisted. Close the DAW before reinstalling, reconnect the license location, and then run a fresh validation.
Repair a failed Audio Unit validation in Logic
- Open Plug-in Manager and select the failed item.
- Choose Reset & Rescan Selection.
- Reopen the project only after the scan completes.
- If it fails again, consult the plug-in developer’s compatibility notes and update the plug-in before trying another reset.
Do not interpret a failed validation as proof that the plug-in is permanently unusable. A host update, an expired trial, a missing license location, or an installer run with the host open can produce the same visible symptom.
Why does the plug-in load but produce no sound?
First prove that audio reaches the track and leaves the interface. Bypass third-party plug-ins, check the track’s input and output meters, and temporarily use the computer’s built-in input and output. This isolates routing and hardware from the plug-in’s processing.
Run the audio-device isolation test in Logic
- Bypass all third-party Audio Units on the affected channel and bus.
- Disconnect the external audio interface.
- In Logic’s audio settings, select the built-in input and built-in output.
- Play a known-good project or a test signal.
If playback returns with built-in audio, the interface, its driver or its control software needs updating or service. If the signal remains silent, continue with track, bus, mute, solo and monitoring checks before blaming the plug-in.
Rank #3
- PLUG IN AND HEAR SOUND IN SECONDS - USB Type-A connector with a 3.5mm stereo headphone output and a separate 3.5mm mono microphone input. No drivers, no software, no external power - the adapter is USB bus-powered and is recognized as a standard USB audio device.
- WORKS ON WINDOWS, MAC AND LINUX - Driverless on Windows 98SE/ME/2000/XP/Server 2003/Vista/7/8, Linux and Mac OSX, and compliant with the USB Audio Device Class 1.0 specification, so any system that supports class-compliant USB audio will see it. Select it as the sound output and input device after plugging it in.
- TWO JACKS, TWO JOBS - The green jack is stereo OUT for headphones or powered speakers; the pink jack is mono microphone IN for a 3.5mm mic. It does NOT support 4-pole headsets on a single combo plug, it does NOT power passive speakers, and it does NOT add surround sound - it is a stereo 2-channel adapter.
- FOR LAPTOPS AND DESKTOPS THAT NEED AN AUDIO PORT BACK - Adds a headphone and mic port to a laptop, desktop, or mini PC whose onboard jack has failed or was never there. Managed and work-issued computers can block new USB audio devices by policy - check with your IT department before ordering for a company machine.
- SABRENT SUPPORT AND WARRANTY - What is in the box: one USB audio sound adapter. Backed by a 1-year limited warranty, extended to 2 years when you register within 90 days on the manufacturer's website.
Prove the plug-in in a blank project
- Create a new empty project or Set.
- Add one audio or instrument track with a known-good source.
- Insert exactly one instance of the suspected plug-in.
- Watch the input and output meters while changing a clearly audible control, such as a wet/dry mix or gain.
- Compare the result with the plug-in bypassed.
Ableton recommends this isolation test because it changes neither the original project’s routing nor its collection of devices. If the plug-in works in the blank project, inspect the original track’s sends, buses, automation, side-chain source, mute or solo state, and plug-in preset.
Check the common no-sound conditions
- The plug-in is 100 percent wet but receives no input.
- A gate, expander or side-chain processor is closed because its key signal is absent.
- The track or an upstream bus is muted or solo-isolated.
- The plug-in output is routed to a disabled or different hardware output.
- An instrument plug-in is on an audio track with no MIDI or audio source.
- The interface’s monitor control is turned down even though the DAW meters move.
Change one condition at a time and keep the blank-project result as your reference. Do not reinstall a plug-in to fix a mute, an empty instrument track or a disconnected output.
How do I stop the DAW from crashing or hanging while scanning?
A scan crash usually points to one incompatible or damaged plug-in, not the entire plug-in collection. Prevent the host from loading third-party plug-ins, identify the offending file, then update or remove that one build.
- Launch the DAW with third-party Audio Units or plug-in scanning disabled, if the host provides that startup option.
- If the DAW opens, close it and move the suspected plug-in file temporarily outside the scanned folder. Keep a backup rather than deleting it.
- Reopen the DAW and confirm that it reaches the project or browser without hanging.
- Update or reinstall the removed plug-in with the DAW closed.
- Return one format or one plug-in at a time, rescanning after each change.
Ableton notes that outdated plug-ins are very often the cause of crashes and performance issues. Apple also warns that a Logic scan can appear stalled for 10 minutes or more when it is waiting on an expired demo or USB license-dongle alert. Give a legitimate scan time to finish, but intervene when the same file repeatedly causes a crash.
How can I identify the offending plug-in?
Record the last plug-in name shown in the scan log or progress window, then move only that file out of the scan path. If the next scan completes, restore files in small groups until the failure returns. The last file restored is the useful suspect; test it alone after updating its license and compatibility.
Rank #4
- Podcast, Record, Live Stream, This Portable Audio Interface Covers it All - USB sound card for Mac or PC delivers 48kHz audio resolution for pristine recording every time
- Be ready for anything with this versatile M-AUDIO interface - Record guitar, vocals or line input signals with two combo XLR / Line / Instrument Inputs with phantom power
- Everything you Demand from an Audio Interface for Fuss-Free Monitoring - 1/4" headphone output and stereo 1/4" outputs for total monitoring flexibility; USB/Direct switch for zero latency monitoring
- Get the best out of your Microphones - M-Track Duo’s transparent Crystal Preamps guarantee optimal sound from all your microphones including condenser mics
- The MPC Production Experience - Includes MPC Beats Software complete with the essential production tools from Akai Professional
When should I reset plug-in caches?
Use the DAW’s reset and rescan controls first. Cache deletion is a last resort because it can trigger a long full scan and will not repair an incompatible binary or an invalid license.
Logic and Audio Unit cache reset
Start with Plug-in Manager’s Reset & Rescan Selection or Full Audio Unit Reset. Older Logic troubleshooting procedures may require moving AudioUnitCache files out of ~/Library/Caches; Arturia documents this as a force-rescan method. Quit Logic before moving any cache file and keep the files in a temporary folder so they can be restored.
Pro Tools AAX cache reset
For Pro Tools 2023.12 and later, the documented AAX cache folders are /Users/Shared/Pro Tools/AAXPluginCache/ on macOS and C:UsersPublicPro ToolsAAXPlugInCache on Windows. Quit Pro Tools, move the cache contents rather than deleting them, then reopen Pro Tools and allow the complete scan to finish.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesAfter a cache reset, do not launch a large session immediately. Confirm that the plug-in appears, validates and produces audio in a blank project first.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do the troubleshooting steps differ by DAW, system and symptom?
The right fix depends on the host, format, operating system and symptom. Use this matrix to choose the shortest safe path.
Best Value
- The new generation of the artist's interface: Connect your mic to Scarlett's 4th Gen mic pres. Plug in your guitar. Fire up the included software. Start making your first big hit
- Studio-quality sound: With a huge 120dB dynamic range, the newest generation of Scarlett uses the same converters as Focusrite’s flagship interfaces, found in the world's biggest studios
- Never lose a great take: Scarlett 4th Gen's Auto Gain sets the perfect level for your mic or guitar, and Clip Safe prevents clipping, so you can focus on the music
- Find your signature sound: Air mode lifts vocals and guitars to the front of the mix, adding musical presence and rich harmonic drive to your recordings
- With Scarlett 4th Gen, you have all you need to record, mix and master your music: Includes industry-leading recording software and a full collection of record-making plugins
| Situation | First action | Next escalation |
|---|---|---|
| Ableton plug-in missing | Enable the folder containing the installed format; keep VST2 and VST3 paths separate | Hold Alt/Option and click Rescan |
| Logic plug-in absent | Search Plug-in Manager, reinstall and restart Logic | Use Reset & Rescan Selection or Full Audio Unit Reset |
| Logic validation failure | Select the item in Plug-in Manager and reset/rescan it | Check compatibility notes and update the plug-in |
| Pro Tools plug-in missing | Confirm an AAX build is installed | Use Pro Tools rescan tools, then clear the documented AAX cache if needed |
| Plug-in loads with no audio | Bypass third-party devices and verify meters and routing | Switch to built-in input/output and test one instance in a blank project |
| DAW crashes during scan | Disable scanning or launch without third-party plug-ins | Move the suspect file, update or reinstall it, then restore one at a time |
What should I do after the plug-in finally appears?
Save the working configuration before returning to the original session. Note the exact format, plug-in version, scan folder and license location that succeeded. Then open the original project and replace only the failed instance, keeping the old track disabled until you have confirmed playback and automation.
- Save a copy of the project before replacing devices.
- Check that the restored plug-in reports the same preset and sample-rate behavior.
- Play from the start of the session to catch delayed license prompts or automation mismatches.
- Keep one known-good blank project as a future diagnostic test.
If the same plug-in repeatedly fails after a clean installation, current license and supported versions, treat it as a compatibility defect and contact the developer with the DAW version, operating system, format, validation message and crash or scan details.
Recommended Free Tools
Frequently Asked Questions
Can rescanning a plug-in delete my presets or project settings?
A normal rescan checks installed binaries and does not intentionally remove presets. Before a cache reset or reinstall, save a copy of the project and note custom preset locations because a replacement build may use a different preset format or folder.
How can I tell whether a plug-in is actually receiving audio?
Use the plug-in’s input meter, the DAW track meter before the device, and the output meter after it. A moving track meter with a stationary plug-in input points to the device’s side-chain or channel configuration; moving input with no output points to the plug-in’s controls, preset or authorization.
Why does a Logic scan stay on one plug-in for so long?
Logic can take 10 minutes or more after an update, especially when an expired demo or USB license-dongle dialog is waiting. Check for a hidden authorization prompt before force-quitting; if the same item hangs on every scan, update it or move its file out of the Audio Unit scan path.
Should I keep both VST2 and VST3 versions installed?
Keep both only when an older project specifically depends on one format or a host supports only one of them. For a new Ableton Set, choose one format and use it consistently so the project does not switch between separate plug-in binaries.
What information should I send to plug-in support?
Include the DAW and exact version, operating system, plug-in version and format, validation or authorization text, whether a blank project reproduces the fault, and whether built-in audio works after disconnecting the interface. A short scan log or crash report is more useful than a screenshot of the whole session.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
