Skip to content

Fixing Cubase Plug-in Loading Errors After Migration to an M2 Mac running OSX Tahoe 26

  • by

About Paul Andrews + Audio Support

Cubase Expert, Founder, Audio Support

Cubase is one of the most powerful digital audio workstations available, but even the best software can behave unpredictably when hardware and settings don’t align. At Audio Support, I specialise in helping creators fix those frustrating problems that halt creativity – from random audio dropouts to Cubase freezing mid-recording. Through one-to-one remote sessions, I connect directly to your Mac or PC, diagnose the cause, and guide you through a practical fix.

Many Cubase users contact me after spending hours in forums or waiting on Steinberg’s support to get back to them. Steinberg’s team are great with system and licensing questions, but they don’t sit inside a real project with you, listening to your mix stutter while you try to hit record. That’s where I come in.

During a remote session, we screen-share using secure software such as AnyDesk or Zoom. I can see your Cubase preferences, audio interface settings and plug-in chain in real time. Together we troubleshoot the entire signal path – hardware, software, and workflow – until everything runs smoothly again.

Neil, a professional composer, contacted Audio Support because Cubase 12 would not load any of his existing projects on his new MacBook M2 running macOS Tahoe.
He had recently migrated his setup from a 2019 Intel-based Mac using Migration Assistant, hoping for a smooth transition.
Instead, Cubase froze at launch or crashed mid-load whenever he opened an existing session.

Immediately, several red flags stood out:

  • Cubase 12 was an Intel-era version, running under Rosetta on Apple Silicon, rather than natively.
  • macOS Tahoe (2025) was far newer than both Cubase 12 and several of his plug-ins.
  • His plug-in library was a mix of legacy and updated versions, copied over via Migration Assistant — a method that often breaks authorisations and file paths.

Together, these factors explained the inconsistent behaviour and project loading failures.

When opening a project, Cubase displayed the names of tracks being initialised on its splash screen before freezing. Watching closely, I noticed it consistently stopped while attempting to load the Arturia JUN-6 V plug-in.
That pointed to an incompatible or corrupted plug-in file.

I guided Neil through starting Cubase in Safe Mode — achieved by holding Shift + Option + Command while launching — which opens the DAW with all third-party plug-ins temporarily disabled.
Once in Safe Mode, we could open his project successfully, delete the problematic JUN-6 instance, and save the session under a new name.

After relaunching Cubase normally, the project opened and played back audio.
Several plug-ins still worked, but many older ones failed to load — confirming that multiple plug-ins installed from the Intel Mac were incompatible on Apple Silicon.

In the short term, disabling specific plug-ins allowed Neil to recover his projects and continue working.
For a reliable long-term fix, I recommended:

  1. Updating to Cubase 14, which runs natively on Apple Silicon.
  2. Re-installing all plug-ins from their latest installers rather than copying them via Migration Assistant.
  3. Maintaining consistent plug-in versions aligned with Cubase 14 and macOS Tahoe.

This rebuild would ensure full compatibility and let his M2 Mac use its processing power efficiently.

During the session, Neil also mentioned trouble activating HALion Sonic.
Checking his My Steinberg account showed that his Absolute 5 HALion library licence was still tied to a Soft eLicenser on his old Mac.
Because Steinberg has retired its eLicenser servers, the licence could not be re-downloaded automatically.

I helped Neil draft a support request to Steinberg, providing the correct system IDs and explaining the transfer situation clearly — ensuring a fast manual resolution.

This case underlines how Migration Assistant can create invisible compatibility problems for audio software.
When moving from an Intel-based Mac to Apple Silicon, direct copying often brings across outdated binaries, hidden preference files, and invalid plug-in authorisations.

The correct approach is a clean install: reinstall Cubase and plug-ins from fresh, current installers optimised for Apple Silicon.
While that takes time, it prevents ongoing crashes and missing plug-ins — and maximises system performance.

Neil’s situation also highlights the importance of version alignment.
He was running 2025 macOS on 2022 hardware with a 2019-era Cubase build — a mix almost guaranteed to trigger instability.
Once he understood why, and saw his projects loading again, he was relieved to have a clear roadmap forward.
He later left Audio Support a positive review on Google for the clarity and care of the session.

As music production technology evolves, transitions between macOS generations and CPU architectures can easily disrupt creative workflows.
At Audio Support, I help clients navigate those changes — identifying the causes of Cubase crashes, plug-in errors, and project loading issues, and providing both short-term workarounds and long-term stability plans.

No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

I usually reply to enquiries within a few hours during UK weekday daytime.

Once you make an enquiry, I’ll read it personally and reply with initial advice or a link to book a remote session if needed.

For booked sessions, you’ll receive a secure AnyDesk link and we’ll talk via WhatsApp or voice chat. Sessions last up to an hour — long enough to diagnose the cause and apply a practical fix.

How soon can you help me?

Usually within 1–2 days. Use the booking system below to find the next available slot.

How do remote sessions work?

We connect via AnyDesk for secure screen sharing and talk via WhatsApp or Google Meet. I guide you live.

What does it cost?

£90 per hour for remote troubleshooting (approx. $110 / €120). Paid securely via SimplyBook.

What if the problem isn’t fixed in one session?

You’ll get a clear plan: next steps, parts to order (if any), and an estimate for follow-up.