Addictive Drums 2 Could Not Find Bus Layouts Top Page
C:\Users\Public\Documents\XLN Audio\Addictive Drums 2\Presets\Bus Layouts
While Addictive Drums 2 is a Windows and macOS native plugin, it is a favorite for Linux users who run it through compatibility layers like . The "Bus Layouts" error typically appears when the XLN Online Installer
Follow these steps in order to resolve the issue effectively. 1. Re-run the XLN Online Installer (Most Common Fix)
The error may be tied to project settings. Try creating a new empty project and inserting AD2 there—if it works, the issue is project-specific. You can also try resetting Cubase's plugin cache. addictive drums 2 could not find bus layouts top
This should resolve the “could not find bus layouts” error in 99% of cases.
If you see the files but AD2 still complains, the path might be corrupted in the registry (Windows) or in AD2’s config file.
Once you have cleaned the duplicates and repaired the installation, ensure your DAW is looking in the right place. Re-run the XLN Online Installer (Most Common Fix)
Keep a backup copy of your AD2 library folder and the original installer files. If an error occurs, you can quickly revert to a known-good configuration without re-downloading large libraries.
: Run the XLN Online Installer again to place a single, fresh version of the plugin in your preferred VST folder. 3. Update DAW VST Paths
Try deleting the configuration files in Documents/XLN Audio/Addictive Drums 2/ (specifically the settings files, not the audio samples) and let the program regenerate them on relaunch. 4. Summary Table of Solutions Potential Cause Corrupted Installation Run XLN Online Installer and choose Repair. Library Moved Use "Change Content Folder" in AD2 settings. Multiple Versions Remove old .dll / .component files from DAW. Missing XML File Reinstall AD2 to restore BusLayouts.xml . This should resolve the “could not find bus
: Users discovered a bizarre workaround: the installer would fail when run normally but would "miraculously" work if launched through
(a gaming-focused manager for Linux). This is because Lutris automatically configures specific DLLs and environments that the standard XLN installer requires but doesn't explicitly name. Case Sensitivity
The XLN Audio support team often suggests that the quickest fix is to run the . Open the XLN Online Installer . Click on the Addictive Drums 2 product. Select the "Repair" or "Reinstall" option if available.
The correct sequence for a fresh installation is: (1) move the AD2 folder to the desired location, (2) run AD2_Library_Placer.exe , (3) only then run setup.exe . If you skipped the library placer step during initial installation, running it now will fix the bus layouts error.
Run the XLN Online Installer periodically to check for updates. This ensures that any known bugs, including BusLayouts-related issues, are automatically patched.
17 Comments
It could be so simple. Always ask your wife first.
Has been working fine for me for almost 25 years now. ;)
one ntfs partition on usb key in uefi boot (with or without SecureBoot) isn’t fully supported. use fat32, rufus make it.
Thank you! After watching countless videos and reading many how to articles I stumbled on yours. I simply changed the 3.0 setting to auto from enabled and my operating system loaded right away.
Where is said 3.0 setting?
Thank you. Nearly blew my brains out thinking I couldn’t boot from USB anymore
You saved me, this is very valuable information. Thank you!!
I was having the same problem on windows 10, and I believe it was because of how I’d formatted my USB stick. Originally I had just created a partition as FAT and was able to load many different ISOs onto the device. Then I made a mistake and had to re-format(?) the whole device, which included re-making the file/partition table. Originally I just chose the default “Scheme”, “GUID Partition Map”. From this point on I was having trouble. I had a hunch that it might require the “Master Boot Record” scheme, so I erased the whole USB stick again with that setting. Then when I ran unetbootin again it worked without issue.
I was having the issue of my USB stick not being detected by BIOS, i solved it by using the latest version of Rufus 3.13 instead of using the old one 3.8 version.
Thank you so much. It really was USB 3…
USB2 flash drive made no difference for me.
My problem was the USB 3.0
Just plugged him in a 2.0 input and it worked. Thank you so much!
For older laptops with both 3.0 and 2.0 USB, try putting the 3.0 USB stick into the 2.0.
Switching from USB 3 to 2 saved my sanity. Thanks!
I switched ports and this made it work – I was using a 3.2 usb and apparently the side port on my laptop wasn’t working
Thanks, my old computer can only find usb drive from cold boot, and it is a usb 3 in usb 2 port, or you have to plug it into usb port when computer is booting right after memory checking; otherwise the computer won’t find this usb3 drive.
Great post, Helge! I tried all the steps you mentioned and finally got my USB drive to show up in the BIOS. Your clear instructions made the process so much easier. Thanks for sharing!
Thank you for this informative post, Helge! I was struggling with my USB drive not appearing in the BIOS, and your troubleshooting steps helped me pinpoint the issue. It’s good to know about the USB formatting and BIOS settings—I’ll definitely keep those in mind for future setups. Appreciate your insights!