Hi all,
my M4 pro macbook was installed with Cubase Pro 15 (k'ed by imdumb), however on 31JULY, the Steinberg Library Manager happened to have error (-1) saying unable to install the privileged helper and then I as a last resort installed the latest version of Steinberg Library Manager from Steinberg website.

Since then the Cubase doesn't work even I uninstalled everything related to Cubase and Steinberg from the machine (a very deep uninstallation by removing any file with "Steinberg/activation manager/cubase etc), the original k'ed version no longer works in the machine anymore.

An alert of "no license" keeps showing up even it successfully patches the Cubase installer (following all the installation sequence from the k'ed installer .dmg)

Any advice will be appreciated. Many thanks

 

15 working fine. everything updated, all content working.

That is using the Steinberg updated patcher from iamdumb. Everything else just downloaded directly from their Download Manager app.
Everything blocked in Little Snitch, and some generic host entries to block as much as possible before it hits Little Snitch even. I have Little Snitch on Alert Mode anyway.

When you install anything new from the Download Manager, you just run the patcher again. Just make sure you are using the newest updated patcher.

If you are doing a "deep clean" first, I would suggest using Find Any File to do so.

 

Thank you Clone for your quick response. I have been using and installing Cubase 15 from the k'd by iamdumb, however when installing the Cubase 15 (before patching by the Iamdumb patcher), at the very last moment of the installation bar, when it triggers to the Steinberg Library Manager with the attached error shown, and then I keep installing the patch (successfully installed) but when loading up the Cubase 15, it said there is no license in this device.

I wonder if my device (i.e. my M4 pro) is being blocked by Steinberg? Or If I have Little Snitch, what URL should I block firstly before Loading Cubase ?

Any advice is much appreciated. Thanks again.

 

the last update of the patcher was from July. I do not remember downloading anything from SB, but their Download Manager app. Cubase installs all of those applications when you install it, My "authorization" app does not load, but my Library Manager and Download Manager do work. Authorizations are handled by the patcher anyway. You probably want to get rid of the applications and use the newest Download Manager to dl Cubase Pro 15. Then whatever other plugins, apps, and content. Then run the patcher, so it does everything all at once. But you can re-run it whenever. I just suggest that as it may be cleaner way to do things.

In Little Snitch, do manage rules, add a rule blocking outbound connections, choose an SB application, set it to deny for any server, and accept the rule. Repeat for each one of their applications. You can then add a rule to block any application, servers, pick domain steinberg.net, steinberg.de, and any others you may see in your LS "recently denied" you come across. Check to make sure you have not created any allow rules, just in case.

I use dr.buho as my cleaner program, it's similar to clean my mac and whatever others. After that I use Find Any File to search for anything it has missed and delete whatever it finds that applies.

The patcher is working fine, so I very much think the problem is on your end. If somehow you were "blocked", from a clean state and only using their download manager app, you'd know right then. It wouldn't let you download anything.

 

Please correct me if I get you wrong - I need to directly download the Cubase Pro 15 and Library Manager via SB Download Manager app and then run the patch after install everything ?
At the same time you also block the outbound connection for SB application and also inbound connection from steinberg.net & steinberg.de ?
Thanks again Clone.

 

Excuse my possibly useless suggestion, but you have to reboot after install/patching.

 

the idea of little snitch is that you block everything until you need to open something. (ignore if it does not apply to you)

 

So far I use little snitch to block steinberg.net and download all the stuff from SB website. After installing the library manager, media bay and Cubase 15, I also applied the patch by iamdumb (I guess it is not from July but by June 2026) and when I load up Cubase 15, it says no license found in my device unfortunately (Given I already disconnect w/ internet). So I am still unable to install Cubase 15 since I had installed the official Steinberg Download Assistant 3 days ago (also deep cleaning already). Even I have already done a deep cleaning removing everything related to Steinberg /Cubase, the installation is still unsuccessful.

Before that I have been using Cubase 15 since early June 2026. Now I kind of loss the Cubase 15 to use.

 

You should be removing the remnants of the patcher, not just the SB locations. Remove: iamdumb's SteinbergPatcher.plist and iamdumb's SteinbergPatcher.bom from this location: /private/var/db/receipts/ Or just search for SteinbergPatcher.plist using FAF or Finder.

I'm not sure you even have to. The patcher should overwrite old files with new ones. It's working perfect, and no-one else has mentioned having your problem. The only requests for a new update are for the Steinberg Classics they just released, and as of now, it won't work on those. Yet.

check your PM.

 

Thank you Clone for your reply and advice.

I had tried the July patcher after removing all the remnants of the previous patcher by FAF, but still unsuccessful unfortunately.
I really wonder if any hidden or corrupted files created from the official Steinberg Download Assistant (SDA) which I downloaded and installed on 03AUG for updating the Library Manager.

Since then the "no license found on the device" appears whenever I load up Cubase 15.
I even tried 2 alternatives - (A) use all latest Library Manager, Media Bay and Cubase 15 installer from official website and (B) just use the files provided from iamdumb's Cubase 15.0.30.dmg + the july patcher, none of them work unfortunately. All the way I also use Little Snitch to block Steinberg.net as well. I really have no clue what stops Library Manager installation. The same error alter appears during the installation of Cubase 15. The installer will trigger the Library Manager and the error code alter appears 3 times during the installation process even it said the installation is successful at the end.

I wonder if I really need to re-install the entire OS to get rid of the unknown corrupted files so that I can use Cubase 15 + HALion + Groove Agent again. Such a disappointing last resort if it needs to be.

Thank you Clone.

 

Nope, you should not have to reinstall MacOS. I think I actually broke it in the same way you have it once, because I do remember being a little puzzled by it and thinking the same thing as you. But I was putting all content files into an external drive and symbolic linking it, which I got rid of my relative symlinks and redid them later. It was frustrating, but I did not go to any extraordinary lengths to fix it.

When I did fix it, I remember just removing everything, cleaaning up, reinstalling everything directly to the default locations with download app and that was it. What I am 100% certain of is that I did not reinstall MacOS.

I would try doing the whole thing with all DAW applications and plugin host software like Bluecat's Patchwork not running. Check your Activity Monitor just so you do not allow any plugins out to the internet. Make sure you do not have any host entries blocking. Disable Little Snitch. Stay online the entire time you are installing C15 and all plugins/content. When you finish, re-enable Little Snitch. I would even do a reboot after running the patcher as someone suggested, although you really do not need to.

Did you happen to update to MacOS Tahoe? On macOS Tahoe, some pre-Tahoe built installers won't complete successfully unless /Users is unhidden (sudo chflags nohidden /Users).

Issue this: sudo chflags nohidden /Users <- to unhide /Users/
then issue: killall Finder <- just to restart the Finder.

That little Tahoe solution for older installers I came up with because Tahoe installs were driving me nuts.

 

Last edited: Aug 6, 2026 at 5:21 AM

Thanks a lot Clone for your insights and advice again. Much appreciated it indeed.

My device is a MBP M4 Pro in Sequoia 15.7.7. All the content files for CB15, HALion, Groove Agent etc. are being kept in the external ssd with symlinks. That's my practice to keep them in an external ssd with symlinks for connection & use.

In these 2 days, I used various cleaner apps + FAF to remove everything related to Steinberg/Cubase. So I believe there should be no more files related unless there is hidden/unknown tracking files which is not labeled with steinberg or Cubase or HALion etc.

The "Steinberg Library Manager privileged helper has wrong version" error (shown in above post) has been triggered 3 times during the very last moment of the CB15 installation process.

Before the CB15 installation process, no error is shown during the Steinberg Library Manager & Media Bay installations process.

Also no error shown during the patcher installation. So it is weird that this error is triggered by the CB 15 installer.

I also tested that the Library Manager can be normally opened after the patcher running. It is just that CB15 cannot be loaded up even after a successful patching process + reboot.

After reading your last post, will you suggest me to re-use the steinberg download assistant to download the Library Manager + Media Bay + Cubase 15 directly from Steinberg, and install them (stay online) + patching them with July Patcher ?

My confusion is how to get rid of the error being triggered by the Cubase 15 installer.

Sorry for this long messgae.

Thank you Clone .

 

I asked GPT about that specific error. I do not remember having to when I had this happen, but it was a while ago so who knows? Buho would probably fix it, but you would have to not just remove it, but look in its leftovers, startup login daemons, etc. categories in that program. (it's awesome). I might have even run KnockKnock from Objective-See to find any persistence mechanisms: https://objective-see.org/products/knockknock.html

here you go anyway, since there are a few tips you haven't already tried:

Spoiler

Yeah, that message is usually not actually saying the installed Library Manager app is old. The wording is misleading. The (-1,-1) part generally means the privileged helper tool (the background service that runs with admin privileges) is missing, corrupted, disabled, or a different version than the Library Manager app expects. A lot of people hit it even after installing the newest Library Manager.

On macOS, I would check these things:

1. Check Steinberg background items
   • System Settings → General → Login Items
   • Look under Allow in the Background
   • Make sure Steinberg items are enabled (especially anything resembling Steinberg Helper, Steinberg Library Manager Helper, or Steinberg Media Technologies).
   • Reboot after enabling. Several users reported that the helper being disabled was the actual cause.
2. Remove the orphaned helper and reinstall Library Manager
   
   The app can be new while the helper left behind in /Library/PrivilegedHelperTools is old or broken.
   
   Check:
   
   
   ls -la /Library/PrivilegedHelperTools | grep -i steinberg
   
   Also check:
   
   
   ls -la /Library/LaunchDaemons | grep -i steinberg
   
   If there are old Steinberg helper files from previous Cubase versions, remove them and reinstall Library Manager.
   
   
3. Reinstall with admin privileges
   • Delete Steinberg Library Manager from Applications.
   • Restart.
   • Install the current Library Manager again.
   • Enter the admin password when prompted.
   • Restart again.
4. Check Disk Utility First Aid
   
   This sounds strange, but there are reports of permission problems on the system volume causing the helper install to fail.

Given the wording, I would not waste time downloading Library Manager repeatedly. If the person already has the newest version, the likely problem is the helper registration, not the Library Manager package itself.

If this is on macOS Tahoe, I would especially suspect the Login Items / launch daemon side because Tahoe tightened a lot of background service behavior. The exact fix path may be slightly different than older macOS versions.

 

Last edited: Aug 6, 2026 at 8:47 AM

The installer times out by itself after a while then closes the installer app. You apply the latest patch, done! Are you sure that you don’t interrupt the install process?

 

Hi Clone,

After couple of tests, I finally can remove the error by following the suggestion from chatGPT' - enabling the "allow in the background" for the steinberg's helper + reboot. The Library Manager can normally register the existing libraries stored in the external ssd. So it works fine.

However, it is still unable to load up C15. That's really frustrating. I used BuhoCleaner + FAF + knockknock.app to remove all the steinberg/cubase related files (including those hidden system files as well). But the result is disappointing.

I tried both July and previous Patcher, but still unsuccessful. I also tested 2 scenarios - loading up with internet and loading up w/o internet but the result is still the same.

I really don't know what else I could try. Asking AI about k'd software installation doesn't work, AI rejects to answer.

Thanks a lot again.

 

Hi Hot Rats - The C15 installer runs smoothly even it triggered the error before and with the help from Clone, the error is now fixed during the C15 installation process. I installed the Library Manager, then Media Bay, then reboot to ensure all Steinberg helper is enabled, then install C15 w/o error and the install Patch + reboot.

Doing the above mentioned, no more steinberg privileged helper error but C15 is still unable to load up. So disappointing.

Thanks

 

it is absolutely amazing that neon, 3 lines of code, made 30 years ago, always free, plus i own about 10 legit licenses for cubase VST, now has a technical copy protection and people have problems using it.