Hi all,
When I select “close” with only a single project open and active Cubase also closes completely. Additional info: It happens with every project, no plugins used. I have disabled the hub.
The only way to avoid this is to have a second project opened.
There is also no “silent crash” happening, cubase restarts perfectly after this.
Do I miss something?
From the Hub menu, open the Hub, then, in Hub Settings, check this box:
Must be an intended or uninted effect of having the hub disabled. I do like the hub except that closing the hub does not quit cubase (with no project open). So I think the quiting logic is net yet fully as it should be. But your case is worse, since you now have to restart cubase and I have to use shift+Q to quit (or from menu)
Hi Mr. Soundman and thank you for your effort to point me in some direction, but:
I am fully aware that I can enable “open hub when closing projects” since I intentionally disabled it.
My issue is not about that, it is about the strange behaviour, that cubase shuts down when I close the single open project. Which it definitel should not do - be it with or without returning to the hub.
Hi and thank you. That is exactly my point.
It seems to be intentional behaviour of the application to shut down when “open the hub…” is disabled when we only want to close the project and not cubase as a whole.
If this is by design, I would not agree with the thoughts for this deciion. Otherwise I would simply consider it an unintentional oversight.
Agreed, I’d even go further, and say that Cubase window handling in general is still a work in progress, however, sympathy to the devs trying to unpick what must be software development’s equivalent of Twister.
When working with multiple open projects, it is understandable that one would not want the hub to open when one project is closed, and I think this is why that option was added, but perhaps not fully thought through.
Agreed … surely all that is needed is to test whether the project being closed is the only one open, and if so, do not open the hub if the “Open Hub …” option is not selected.
I find it convenient that the Hub opens when I close a project. Easy access to open projects that is unfinnished or new projects or templates. 
I think most of us do, but what is missing is closing cubase from the hub. Red cros does not do it. So you need to do it via menu or ctrl+Q (which is easiest and doable, except when you already have the mouse in your hand, it is counter intuitive to not be able to close with the close button)
Ah I have found the “logic”, red cross closes cubase when there is no window open, except this also goes for hidden windows. In my starting template the performance meter is open but hidden, so it does not close then. But I have now removed it from my template and now it closes.
addition
If you make sure there are no persistant windows open (like the perf. meter) cubase closes when closing the hub. Logic seems to be that only the last window closes cubase, but as in case with the OP also when that last window is a project and the hub is disabled. Closing the performance meter when it is the last window, will bring the hub back when eneabled.
OMG
the madness is that the same action can have different results depending on what windows are open.
Maybe this is is actually standard Windows behaviour - which is different from standard Mac behaviour?
Maybe I’m misinterpreting some of the Cubase changes over the last few versions, but I’ve been under the impression, that Cubase Window management on Windows has been slowly changing to be more standard Windows compliant, rather than behaving like a MacOS app on Windows.
Since I drive MacOS and Windows and Linux quite a lot, seeing different UX behaviour is most certainly confusing. But not more so, than using Ctrl vs. Command keys. And I’ll gladly pay that price of confusion for the upside of maintaining diversity and choice for us end users.
UX discussions are a deep rabbit hole, but I’ll resist the temptation to further derail this thread. 
Well, sure I can understand this. Still: Steinberg offered the option to not return to the hub when closing. So it is not reasonable to quit cubase and thereby “killing” the “Close Project” meaning of the corresponding menu item.
No, it isn’t – Word (on Windows) doesn’t shut down (requiring a restart of the application) after you close the last open document. You should still have the application open, with the option to create a new document.
IMHO the “last” application window should be (and used to be, prior to v14) the Cubase background window itself, i.e. what you were left with after closing all projects. Then again, Cubase on Windows was never totally “Windows compliant” in this regard – but I think it’s getting there, which, for me, is welcome.
On project close
If last project
If "Open Hub When Closing Projects" is unchecked
Close the project only
Else
Close both the project and Cubase
Your pseudocode snippet shows how it works.
Unfortunately.
What would make sense is the following: open the hub anyway. Closing a project should never result in vloding the program, since it also does not make any sense that a hub opens when we intend to close the program.
It should be as follows:
Closing a program means the user does want to stop working with it.
Closing a file means the user intends to continue using the application.
Are you sure?
Window.Closed
The Closed event is raised when the window closes. If this is the last window to be closed, usually the app’s MainWindow, the application will be terminated. Because there is no
Suspendingevent raised by theApplicationobject in Windows App SDK, you should use your main window’sClosedevent to save application state and clean up any managed resources.
Source: (Windows App SDK app lifecycle - Windows apps | Microsoft Learn)
Yes, I’m sure.
Quoting MS, “If this is the last window to be closed, usually the app’s MainWindow, the application will be terminated”
Up to recently, the “last window” was the background Cubase window, with no project open. Closing that terminated the application, which is compliant with the behaviour described in the MS docs you quoted. You could have left that window open, with no project loaded.
I think the question is, in Cubase 15, what is the application’s MainWindow now? Is it the Hub? That can’t be, because we can close the Hub and Cubase itself does not terminate.
Yes - the old Cubase design had a main window, while recent Cubase doesn’t.
So the new design (maybe inadvertently?) unearthed the Windows default behaviour.
Which is less desirable when your typical workflow includes working with multiple projects in a single Cubase session, due to the somewhat long Cubase startup times for users with lots of plugins.
But the new UX behaviour arguably has some benefits for Cubase users, who only work with a single project at a time on more resource constrained computers, so Cubase gets fully unloaded when you quit working on your Cubase project and maybe open some video editing software or a browser for having arguments on a forum. 
p.s. Side note: On some older Cubase versions (several years and versions ago), I always quit and re-started Cubase between opening projects, so that Cubase would start with a clean slate. Because in some of those older versions Cubase could become a bit of a mess when working for a long time across different projects.
The discussion by some of you is mislead. Like hijacking the thread! Sorry.
The point is strictly from a user perspective: closing a file closes the file and not the application. Closing the apo closes the app and cleans everythong up neatl,.
Thats it.
We should not be discusding windows internals at all. There is absolutely NO reason for skilled programmers to be forced to undermine user perspective logic.
Discussions like that are approaching things from the wrong direction.
With respect, I gave you the answer in the second post, but you had chosen to disable that option – a detail that you did not disclose in your initial question.
I was greatful by your hint. But I was aware of it and stated clearly that I intentionally disabled the hub. My point is simple: closing a project should under no circumstances close the app. Fullstop.
I am,after 40 years in major software development, simply annoyed to read things about windows internals as an argument why things are behaving in a wierd logic.
So my rant was not at all about your reply!
So, pretend for a moment that you have enabled “Open Hub When Closing Projects”.
(Side note: the option should more accurately be named “Open Hub When Closing The Last/Only Open Project”)
If you have multiple projects open, closing one project does not open the Hub; it just goes back to the previous open project.
If you close the only open project, that Hub page will open, including File/Edit/Media/Transport/Studio/Window/Help menu access across the top.
So now you have an open Cubase with no projects open, but you’re on a screen (Hub page) with all the menu options one could use at that moment.
I fail to see the purpose of disabling the “Open Hub When Closing Projects” option, unless one specifically wants to immediately exit Cubase on exiting the only open project.