> For the complete documentation index, see [llms.txt](https://docs.youlean.co/youlean-loudness-meter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.youlean.co/youlean-loudness-meter/troubleshooting-and-tips/installation-issues.md).

# Installation Issues

## Windows Installation Issues

{% hint style="danger" %}

* The most common mistake is putting a **plugin in the wrong folder.**
* Make sure that you are installing **64-bit plugins** if you are on the 64-bit platform. 
* **Pro Tools**: Sometimes AAX plugin could not be loaded. This could happen if the plugin signature is broken. Delete the old plugin and install it again to solve the issue. 
* **Ableton Live**: Make sure to enable plugins in the settings. 
  {% endhint %}

***

## macOS Installation Issues

{% hint style="danger" %}

* The most common issue happens if you **overwrite the old plugin** when upgrading. Make sure to delete the old plugins before copying the new ones. 
* Usually **logging off or rebooting** is required after manual installation.
* If the plugin can not be found, or the app cannot be opened, you might need an **older version**. Please [contact us.](https://youlean.co/contact/)
  {% endhint %}

### Fixing Audio Unit Issues

Delete the old plugin and then copy a new one. Log off, or reboot your Mac if the plugin can not be loaded.

If you want to manually validate the Audio Unit, open the **"Terminal"** application and run this command:

```
auval -v aufx urbY gtuY
```

For more advanced troubleshooting methods run these commands in **"Terminal"**:

{% hint style="info" %}
**This is a safe operation**

This will kill AudioComponentRegistrar process. 

It could solve the Audio Unit not showing up problem.

{% code title="Command:" %}

```
killall -9 AudioComponentRegistrar
```

{% endcode %}
{% endhint %}

{% hint style="info" %}
**This is a safe operation**

Delete **com.apple.audio.InfoHelper.plist** file. This could be done using Finder or Terminal via the command below.

It could solve various Audio Unit issues.

{% code title="Command:" %}

```
rm ~/Library/Preferences/com.apple.audio.InfoHelper.plist
```

{% endcode %}
{% endhint %}

{% hint style="warning" %}
**Warning**

Delete **com.apple.audiounits.cache** file. This could be done using Finder or Terminal via the command below.

It will force a full rescan of all Audio Units on your system. 

It could solve various Audio Unit issues.

{% code title="Command:" %}

```
rm ~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache
```

{% endcode %}
{% endhint %}

{% hint style="danger" %}
**Unsafe. Do only as a last resort** 

Delete **com.apple.logic10.plist** file. This could be done using Finder or Terminal via the command below.

It will reset all Logic Pro X settings. 

Most commonly it will solve issues where a plugin is not available in some channel configurations.

{% code title="Command:" %}

```
rm ~/Library/Preferences/com.apple.logic10.plist
```

{% endcode %}
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.youlean.co/youlean-loudness-meter/troubleshooting-and-tips/installation-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.