MediaBay becomes unusable after latest HALion installation — VST Sound content shows blocked icons

Cubase
1

MediaBay becomes unusable after latest HALion installation — VST Sound content shows blocked icons

Cubase Pro 15.0.30 – Windows 10

I would like to report a serious MediaBay issue that is currently blocking my workflow.

Cubase MediaBay was working normally with Cubase 15.0.21. I then updated to Cubase 15.0.30, and everything continued to work perfectly.

The problem appeared later, immediately after installing the latest version of HALion.

Current situation

  • Steinberg libraries are correctly installed.

  • Steinberg Library Manager shows the libraries correctly.

  • The same libraries work normally inside HALion and Groove Agent.

  • HALion is now working correctly, after resolving its own library issue.

  • Steinberg MediaBay Server is installed and running correctly when Cubase is open.

  • MediaBay can see the VST Sound folders and files.

  • However, inside Cubase MediaBay, the content shows a blocked icon :prohibited:.

  • No waveform is displayed.

  • The content cannot be previewed or used normally.

  • Recreating the MediaBay database did not solve the problem.

  • Renaming the relevant MediaBay/ContentManager files and allowing Cubase to recreate them also did not solve it.

  • There is no Windows “Unblock” option on the VST Sound files.

This strongly suggests that the VST Sound libraries themselves are not the problem. The same content works correctly in HALion/Groove Agent, while MediaBay alone cannot access it properly.

A bigger MediaBay workflow problem

Beyond this specific bug, I believe MediaBay’s overall workflow needs serious reconsideration.

MediaBay relies heavily on database indexing and scanning. In practical production work, this can become extremely frustrating.

Professional users often already have carefully organized personal sample libraries:

KICK / SNARE / CLAP / HI-HAT / PERCUSSION / TOM / CYMBALS / BASS / GUITAR / VOCAL / LOOPS, etc.

If I add a new WAV, loop, or kit to one of these folders, I simply want to:

Open the folder → see the file → preview it → drag it into the project.

I should not have to perform another scan every time I add a few samples.

The database/metadata system can be useful for users who need advanced tagging and categorization, but basic file browsing should not depend on it.

Why this is serious

This is not just an inconvenience. When MediaBay stops working correctly, it stops my production workflow.

I don’t need Cubase to analyze or categorize files that I have already organized myself. I need it to access my content quickly, reliably, and predictably.

I would strongly encourage Steinberg to consider a direct File Browser mode in MediaBay that:

  • Detects newly added files automatically.

  • Does not require a full scan for every new sample.

  • Allows direct browsing of the Windows file structure.

  • Provides immediate preview without mandatory database indexing.

  • Keeps advanced metadata/tagging as an optional feature.

  • Remains reliable after updates to other Steinberg products such as HALion.

Cubase is an extremely powerful DAW. I believe its content browser should also offer a simple mode for users who do not want database-driven sample management.

I would appreciate it if the MediaBay development team could investigate this specific VST Sound/blocked-content issue and also consider improving the overall MediaBay workflow.

Please let me know if you need logs, diagnostic files, or any additional information from my system.

2

Blocked icons or warning symbols associated with VST sound content in the Steinberg MediaBay usually indicate licensing issues, licenses that have not been activated in the Steinberg Licensing system, or missing or corrupted library registrations in the Steinberg Library Manager.