A renamed file still will be found.
Of course there may be more causes for side effects on other systems. The fact is that internet transmissions will decrease substantially without Steinberg Runtime Access.
Thanks. That removed my 20 seconds delay when closing the last open window in order to return to the hub.
Not usually. LoadLibrary(L"somepath....") will fail if the file name is different, and COM activation requires the path to the library to be registered.
It’s really only with broadly-scanned items in known locations, like VSTs, that renaming still allows a file to be found.
Pete
Microsoft
I was referring exclusively to my experience with the file discussed here, not dynamic link libraries in general.
The file here is a DLL, so not sure what you’re saying. The same rules apply to it.
Pete
Microsoft
1 Like
Renaming does the trick. Changed the suffix to .dl_
1 Like
Or Steinberg could notice this thread and do something about this new issue with Cubase 15!
1 Like
Thank you all for pointing out this potential issue.
Since the Steinberg Runtime you noticed is part of the Steinberg Activation Manager, which is my field of work, I wanted to say a few words regarding it. As you assumed, it provides the content for the tutorial section from the internet to Cubase. For this, it transmits information about your Cubase version and license, so that we can provide the correct content, e. g. Pro shows other entries than Elements.
The process is designed to be asynchronous, so if the internet cannot be reached, it shouldn’t delay Cubase. But as it is with software, it might not always behave as we wanted it to, so we will look into it.
If a few of you who are affected by the slow hub could message me the diagnostic report from Steinberg Activation Manager, this would help with the analysis. Thanks.
6 Likes
Hi Merlin, thanks for chiming in.
I also found out that also seems that Cubase ignores the system’s proxy settings (at least on Windows 11). Imho, this is also not good behaviour. It also means that I need a more complicated setup for doing a mitm proxy 
.
I would in general suggest that if the user disables “show web content”, there should be no connections whatsoever to any Steinberg Server. In these days, lots of users grow weary of all companies “phoning” home (rightfully so imho), especially without at least doing a full disclosure of what is transmitted. But it should be a user’s choice, unless it is explicitly needed, of course, like in the Download or Activation manager).
Edit: Nevermind. I got mitmproxy to work. It seems like Cubase mainly does two things, even if the hub is disabled.
- get a fresh JWT
- get some customer data (although nothing was returned
- get the latest version info for Cubase
Not too bad, but unless I misunderstand something, Steinberg correlates (or can correlate) user account with the times they start Cubase. 
Hello Merlin,
So, I’ve never done this before, but I went into the Steinberg Activation Manager and apparently created the file. I’m attaching it here — let me know if everything looks correct on your end. Thanks a lot.
As for my own issue (I’m actually the one who opened the thread), I’m on macOS, so it has nothing to do with the Steinberg Runtime problem. For me, the issue is just that the hub takes a long time to re-sort and reorganize the recent projects every time it opens, which makes it really slow. That’s the problem I’m facing.
https://www.swisstransfer.com/d/4b1932b2-b8ea-4632-9f5f-18ad3432c3d7
Thanks for sharing.
As you already assumed, I don’t see an indication for trouble with the runtime component. The times to fetch the data seem legit.
@all It would be helpful if someone who experienced an improvement by renaming / deleting the runtime dll could share their diagnostics report.
1 Like
I can understand the scanning process after opening the hub, but why the hub itself sometimes takes up to 48 seconds to appear—both when opening and closing—seems completely unacceptable to me.
I tried this:
Renamed steinberg-runtime-access.dll to .dl
Switch off “Show web Content”
Neither of these helped.
Here’s the actual behavior:
The hub takes 26-50 seconds to become visible every time.
The scan (VST stuff) takes 10 seconds, followed by another xx seconds until the hub appears.
The problem is, it’s the same when closing a project. Closing itself is really quick, but then there’s a forced xx-second pause.
A small note: It’s completely silent during this time, but my NAS makes noises just before the hub appears.
One could say it’s related to scanning the paths, which includes the NAS. That’s certainly true. But then why is there 26 seconds of silence? This process should start immediately after closing the song. The noises themselves only last 1-2 seconds.
This wasn’t the case with version 14, even though the setup and paths were exactly the same.
p.s.
after closing the hub while scanning, the hub crashed and and upon restarting, a decision window appears asking whether you want to start in safe mode.
Just as a data point, the runtime component is still active here as I haven’t touched it.
After closing a project the hub takes about 2 seconds to reappear - a bit longer that Cubase 14 but nothing excessive.
Windows 11 25H2 latest.
I have the internet feed disabled.
Maybee, i found something.
I came from C13.5 to 14 to 15 now.
In the preferences of C14 there was a setting for HiDPI under General. I unchecked it, because plugin windows/GUI were to tiny. Everything fine then.
Now i installed C15 and plugin windows /GUI were tiny again. Then i checked the HiDPI option and it was deactivated like i did for C14.
Solution was: activating HiDPI, close Cubase 15, deactivating HiDPI again, close Cubase 15. And now it works again.
So maybee there is a little bug in handling preference settings? Read C14 but dont applied to C15 correct? Or some mismatch between the versions?
Maybee it`s just this HiDPI option, maybee there is an bug in overall preference handling when coming from Cubase 14 and have it still installed. Then this could also affect the behavior of the Hub.
latest Win10
There is an bug: Cubase 15 reads c14 preferenes instead to set new when you have c14 installed.
Problem solved with Cubase 15.0.6! No more “runtime” module present, the Hub now opens and closes without any delay. Many thanks to Steinberg for the quick solution 
Another problem still exists in Cubase AI 15 Hub: Projects cannot be opened from templates and user locations; only the “Recent” section works.