UAD Plug-Ins

Welcome to UA Support
How can we help?

Error Messages Appear When Loading a UAD Native Plug-in in My DAW

If you encounter an error message when loading a native UADx plug-in into your DAW application, click on the error message below to see the appropriate troubleshooting steps.

No Connection to UA Connect

If you are using iLok cloud for UADx licenses and the computer is not connected to the internet, the plug-in will display this message. 


This issue can be resolved by connecting your computer to the internet, opening UA Connect, and restarting your DAW.

Not Logged In

If you are using iLok Cloud for UADx licenses and your computer is not connected to the internet, and were previously logged out of UA Connect due to internet connectivity issues, the plug-in will display this message.


This issue can be resolved by connecting your computer to the internet, closing your DAW, and logging out of then back in to UA Connect.

Activate License

This message is displayed when the UADx plug-in is not properly licensed via iLok License Manager. This can occur if your iLok Cloud session is closed or your iLok USB is disconnected from your computer. 


This issue can be resolved by opening your cloud session in iLok License Manager, and making sure you are not using a “Guest Cloud,” and/or simply closing and opening the cloud session. More information on this topic can be found in this article.

Furthermore, if you have licenses on an iLok USB, make sure that the iLok is plugged into your computer and that all your UADx licenses are on that specific iLok USB.

Note: It is best practice to close your DAW completely before troubleshooting issues related to iLok USB, iLok Cloud, and UA Connect.

Plug-in Not Licensed


This message could be caused by a disconnect between iLok License Manager and UA Connect. We recommend you try closing and re-opening the Cloud session as per the steps in this article.

Additionally, when this happens on Windows, the cause could be that the plug-ins .dll files were moved from their default install location. Move the files back to their default install location or reinstall the plug-ins via UA Connect to solve this issue.

Note: The default install locations are listed in this article.

Connect Sample Content Drive (Windows only)


This issue is usually caused by installing the VST3 UADx plug-ins into a folder named with a special character.

To resolve the issue, move the affected plug-in(s) back into the default VST3 folder in the following path:

  • C:\Program Files\Common Files\VST3

Alternatively, you can remove the special character from the folder name, or reinstall the affected plug-in(s) in the default location mentioned above by following the steps in this article.

GUI Load Failed


If this happens in Ableton Live, you can follow the Ableton Live-specific instructions in this article.

If you are experiencing this issue with any other DAW, we recommend you attempt a full uninstallation/reinstallation of the plug-in by following the steps below:

Windows Runtime Update Required (Windows only)


This message is displayed when Webview2 needs to be updated or installed on your computer. To update Webview2, follow the steps below:

  1. Navigate to the Control Panel > Programs > Uninstall a program.
  2. Find Microsoft Edge Webview2 Runtime on the list and double-click it.

3. A new window will appear and prompt you to repair Webview2. Proceed by clicking the Repair button.

If you need to install Webview2 from scratch, follow these steps:

  1. Navigate to WebView2 - Microsoft Edge Developer 
  2. Scroll to the bottom to download the Evergreen Bootstrapper and let it run.

Tick Size Not Supported


This message appears if you are using an unsupported buffer size in your DAW, such as 48. Switch to a supported buffer size such as 32, 64, 128, 256, 512, etc.

DAW Restart Required


This typically indicates that there was an issue locating the plug-in content or license – therefore requiring a restart of your DAW application.

If restarting your DAW does not resolve this issue, we recommend reinstalling the plug-in in its default folder by following the directions for your operating system below:


Have more questions? Submit a request