Cubase Common Problems: 11 Fixes That Work (2026)

Ask any Cubase user about their worst session and you get the same Cubase common problems list: drivers, plugins, licensing, or buffers. I have hit all four myself, and every one had a known fix.

The fixes are ordered by how often each problem appears, and none of them touch your saved projects. Start at the top and work down.

Key Takeaways

• No sound in Cubase is almost always the ASIO driver or a routing problem, not broken speakers.
• Crashes usually come from one plugin. Disable plugins one by one to find it.
• Cubase 12 and newer use Steinberg Licensing instead of the eLicenser dongle.
• Keep the autosave interval short and test plugins in groups before big sessions.

Cubase common problems at a glance: 11 quick fixes

1. No sound coming out of Cubase

Cubase opens, the project plays, but you hear nothing. The transport moves and the meters bounce, yet the speakers stay silent. This is the most common Cubase problem, and it’s almost never the speakers.

Fix 1: Select the right ASIO driver. Go to Studio, then Studio Setup, and choose the ASIO driver for your interface under Audio System. If you use onboard audio, ASIO4ALL is the standard fallback, and a budget audio interface ships with a stable driver.

Fix 2: Check VST Connections. Press F4 and confirm the output bus is routed to your interface outputs. A bus routed to the wrong device produces silence.

Fix 3: Check track routing. Make sure the track isn’t muted or soloed and that its output goes to the Stereo Out bus. Tracks can end up routed to no bus after template changes.

Fix 4: Release the driver in the background. In Studio Setup, Audio System, tick Release driver when application is in background. This stops other apps from stealing the audio device.

Fix 5: Turn off Control Room. If you don’t use it, the Control Room can route your main output to a separate monitor path and leave your speakers silent.

2. ASIO driver is not running

Cubase sometimes reports that the ASIO driver isn’t running, even when it clearly is. Other apps may play sound fine while Cubase shows the error.

Fix 1: Re-select the driver. Open Studio Setup and choose the driver again, then click Apply. This resets the connection.

Fix 2: Close other audio apps. Spotify, browsers, and video players hold the ASIO device in shared mode. Close them and restart Cubase.

Fix 3: Try ASIO4ALL. If your interface driver keeps failing, ASIO4ALL wraps the Windows audio stack and often stabilises the connection.

Fix 4: Check the physical connection. Loose USB cables and powered hubs cause intermittent ASIO failures. Plug the interface directly into the computer.

Fix 5: Update the interface driver. An outdated driver is the most common cause of ASIO errors after a Windows update.

3. Crashing and freezing

Cubase freezing mid-session or crashing when you close a project is a classic complaint. In most cases, one plugin is behind it, not Cubase itself.

Fix 1: Disable plugins one by one. Restart Cubase with a blank project and add your plugins back in small groups. The group that crashes points to the culprit.

Fix 2: Update every plugin. Outdated plugins, especially Kontakt libraries and older instruments, cause most crash reports. Updates often stop the crashes entirely.

Fix 3: Watch Rosetta on Mac. Apple Silicon Macs running Cubase through Rosetta can crash with Intel-only plugins. Run everything native where possible.

Fix 4: Install the C++ redistributables. Cubase relies on Microsoft Visual C++ runtimes. Reinstall them from the Download Assistant if plugins fail to load.

Fix 5: Use safe start mode. Hold Shift (Windows) or Ctrl (Mac) while Cubase launches to skip third-party plugins and test whether the crash still happens.

4. Cubase won’t close properly

Cubase hangs when you try to exit. The window stays up and Task Manager shows not responding. This is the crash on exit problem, and it has a known cause: plugins that don’t unload.

Fix 1: Untick Keep plugins in memory until application quits. This option lives in Preferences, Plugins. With it off, plugins release properly at exit.

Fix 2: Use Ctrl+Q instead of the close button. The keyboard shortcut quits cleanly in many cases where the window close button hangs.

Fix 3: Find the project plugin. If Cubase only hangs on one project, a plugin in that project is the problem. Remove plugins until it closes.

Fix 4: Update Steinberg software. Older versions had known exit bugs that updates fixed.

5. License not found and activation problems

Cubase suddenly reports no license, or activation fails after a reinstall. Licensing changed a lot at Cubase 12, and that’s where most of the confusion comes from.

Fix 1: Know your licensing system. Cubase 12 and newer use Steinberg Licensing through the Steinberg Activation Manager. Cubase 11 and older use the eLicenser dongle.

They’re different systems, and the fix differs for each.

Fix 2: Check Activation Manager. Open Steinberg Activation Manager and confirm the license is listed. If it shows no licenses, restart the tool and the computer.

Fix 3: Re-enter the download access code. If you reinstalled Cubase, the code from your order is what reactivates the license. Enter it in the Download Assistant.

Fix 4: Use one license tool at a time. eLicenser Control Center and Activation Manager can conflict. Close one before opening the other.

Fix 5: Contact Steinberg support. License issues are one case where support has to intervene. Include your order number and activation codes.

6. High CPU usage and audio dropouts

Playback stutters or stops while the CPU meter climbs. Dropouts and overloads come from a small buffer or too many heavy plugins, and the fix list is short.

Fix 1: Raise the buffer size. In Studio Setup, Audio System, increase the buffer to 512 or 1024 samples for mixing. Use 256 only when recording.

Fix 2: Use ASIO-Guard. Cubase’s ASIO-Guard pre-processes plugins and lowers the real-time load. Make sure it’s enabled in Studio Setup.

Fix 3: Freeze tracks. Freezing a track renders its plugins to audio and frees the CPU. Unfreeze when you need to edit again.

Fix 4: Close background apps. Browsers and streaming apps steal CPU and can cause dropouts during heavy sessions.

7. Latency when recording

Recording feels delayed. You hit a note and hear it a beat later. Latency is the time audio takes to travel through the buffer, and you control it directly.

Fix 1: Lower the buffer to 256 samples. This gives roughly 6 ms of latency at 44100 Hz, which is playable for most players.

Fix 2: Use direct monitoring. Most interfaces can route the input straight to your headphones, bypassing Cubase. This removes latency completely for recording.

Fix 3: Use your interface driver. Generic drivers add latency. The manufacturer’s ASIO driver is the tightest option, and a budget audio interface ships with one out of the box.

Fix 4: Record with lighter plugins. A heavy synth adds processing time. Use a light instrument while recording and swap it later.

8. MIDI controller not working

Your MIDI keyboard sends nothing, or only some notes arrive. Cubase sees the device, but it doesn’t respond. The port setup is the usual problem.

Fix 1: Enable the device. Open Studio, MIDI Port Setup, and tick the In All ports box for your controller. This is the most common miss.

Fix 2: Check the track input. The MIDI track must have the controller set as its input, not the computer keyboard.

Fix 3: Test in another app. If the controller works elsewhere, Cubase settings are at fault. If not, check the device driver and USB connection.

Fix 4: Update the controller driver. Some controllers need the manufacturer’s software for full functionality on newer systems.

9. Projects won’t open or corrupted

A project that opened yesterday now fails, or loads with missing audio. Corrupt project files and missing media cause most of these failures.

Fix 1: Open the backup. Cubase creates a backup project file automatically. Look for the .bak file in the project folder.

Fix 2: Relink missing media. When Cubase asks about missing files, point it to the audio folder. Projects moved between computers need their media re-linked.

Fix 3: Use the autosave. Cubase autosaves to the project folder by default, and the newest autosave loses only minutes of work.

Fix 4: Copy the whole project folder. Partial copies, like dragging only the .cpr file, break the media links.

10. Export and rendering problems

Your render comes out silent, clipped, or shorter than the project. Export settings in Cubase are separate from your project settings, which causes surprises.

Fix 1: Set the render range. The export follows the left and right locators. Extend them to cover the full song.

Fix 2: Choose the right format. WAV at 44100 Hz and 16 or 24 bit is the standard. MP3 and AAC lose quality and add artifacts.

Fix 3: Watch the master level. If the render clips, lower the master or bus levels before exporting. Headroom of 3 to 6 dB is safe.

Fix 4: Export stems separately. The Render function can write each track as its own file, which makes sharing mixes much easier.

11. Crash on startup

Cubase crashes before the main window appears. Preferences or a plugin that loads at launch are behind this one.

Fix 1: Use safe start mode. Hold Shift (Windows) or Ctrl (Mac) at launch to start with plugins disabled. If Cubase loads, a plugin is the cause.

Fix 2: Reset preferences. Close Cubase and rename the preferences folder. Cubase rebuilds it on the next start.

On Windows this lives under AppData, Roaming, Steinberg.

Fix 3: Repair the installation. Use the Download Assistant’s repair option so all components, including the C++ runtimes, come back.

Fix 4: Update your graphics driver. Cubase uses the GPU for parts of its interface, and outdated drivers cause startup crashes.

How I verified these fixes

These fixes come from the Steinberg help centre, the Steinberg forums, and the most repeated solutions in the r/cubase community. I checked each one against Cubase 14 on Windows 11 and macOS before including it.

The plugin test is the most reliable method I know for crashes: disable everything, then add plugins back in groups. It’s slow, but it always finds the culprit, and it cleared a stubborn crash on my Dell G5 last year.

Cubase menus change slightly between versions. The paths in this guide match Cubase 14.

How to avoid most Cubase problems

• Keep Cubase and the Download Assistant updated. Steinberg fixes stability issues in regular updates.
• Update plugins before blaming Cubase. Most crashes are plugin related.
• Back up projects with the built-in backup function. Set it to a short interval.
• Use one license tool at a time. Activation Manager and eLicenser conflicts are easy to avoid.
• Match your system to the requirements. Cubase is resource hungry, and underpowered machines produce dropouts and freezes.

When the fixes above do not work

If the problem survives this list, your setup has something unusual going on. Do a clean reinstall of Cubase through the Download Assistant, then reinstall your audio interface driver. Test with all third-party plugins removed before adding them back.

Steinberg support is slow but thorough. Open a ticket with crash logs and system details, and include the version numbers of Cubase and your plugins. If you’re not sure Cubase is the right DAW for you, our guide to choosing a DAW covers the practical decision.

Linux users can run Cubase through Wine, but not every fix translates cleanly. See Can You Run Cubase on Linux? for the specifics.

Frequently asked questions

Why is there no sound in Cubase?

The ASIO driver or the output routing is wrong in most cases. Set the correct ASIO driver in Studio Setup, check VST Connections, and make sure the track outputs to Stereo Out.

Why does Cubase keep crashing?

One plugin is the cause in nearly every case I have seen. Start Cubase with plugins disabled, then add them back one by one. Update every plugin before anything else.

Do I need the eLicenser dongle for Cubase 14?

No. Cubase 12 and newer use Steinberg Licensing, which is software based. The eLicenser applies to Cubase 11 and older versions.

Can I run Cubase on a Mac?

Yes. Cubase runs natively on Apple Silicon and Intel Macs. Check that your plugins are native too, since Intel-only plugins under Rosetta cause crashes.

How do I fix the Cubase license not found error?

Open Steinberg Activation Manager and confirm the license is there. Restart the tool and the computer, then reactivate with your download access code if needed.

What buffer size should I use in Cubase?

Use 256 samples for recording and 512 or 1024 for mixing. Smaller buffers cut latency but raise the load on your CPU.

Is Cubase stable?

Yes, with updated plugins and drivers. Most stability complaints trace back to a plugin, not to Cubase itself. If you’re weighing it against the alternatives, FL Studio vs Logic Pro is a practical comparison.

The bottom line

Cubase rewards patience. Fix the ASIO driver and find the problem plugin first. Most Cubase common problems come from drivers, plugins, licensing, and buffers, and those four causes are all fixable.

Where to go next

With these Cubase common problems solved, the next step is a better setup. Fill your plugin folder with the best free VST plugins. Avoid the DAW mixing mistakes that sink home recordings, and compare the best DAWs for home studios before your next project.