Sorry, I should have added this, but was thinking all I needed was someone to tell me where to set the date formats for the Cubase Hub.
My PC is Windows 10, 22H2, and its set for Region = New Zealand. Regional format = “Recommend [English (new Zealand)]”.
And in the sample date format its showing me 17/11/2025 and same for the clock/date down in my taskbar. So 17th Nov.
But the Cubase Hub shows me files of e.g. “9/18/2025”.
Changing the Windows 11 settings ‘Regional Format’ to ‘English (United Kingdom) worked for me 
Hmm - It worked just one time. Hub is back on US format - damn…
It’s funny, I use the American date system for close dated material….I can remember the month I worked on something before I can remember the day 
But for long term storage I use yyyy/mm/dd…how you guys can remember if you worked on a project on the 12th rather than the 23rd, that always surprised me
It shouldn’t matter what the Date setting is in the OS, whichever, or where in the world you are, or what language your computer/Cubase uses, Cubase should respect it. It isn’t hard, just query the setting before displaying it.
I didn’t know you had programming experience?
I taught myself in the 90s on my Atari, then in the early 2000s took a few Open University modules, using Borland’s C++Builder. I know the basics, but that’s it. I program in C#, the poor man’s C++.
I use something like this to format numbers and dates:
c.ToString(CultureInfo.CurrentCulture);
haha - and here I thought it was the poor man’s Java 
More seriously - I doubt that the hub is using much - if any - C++. I’m not sure if I remember it being mentioned in the forum before or not, but my guess is that the hub is more of a web technologies stack (HTML, JS, CSS) - but potentially with another framework or two or three on top.
So yeah - I’m also a little surprised by the apparent simplicity of this bug (assuming it actually is a bug and not weirdness on some user machines).
Or maybe it was vibe coded and we can blame the AI?
Well, it is some weirdness as for my system with the region set to german, it works, I can select my preferred short date format and it is reflected in the hub.
my suspicion is that the US date format is a fallback in case the locale query doesn’t yield a sufficient result for whatever reason.
Could be. Would be an unusual decision by a German engineer, I think, to not use the ISO standard in such a case. Besides, formatting units to OS locale is a pretty rudimentary operation in all programming languages I have encountered.
Well, I am not sure you ever tried formatting dates with Angular’s datepipe for all possible locales…
I can assure you it is not rudimentary
As Nico suggested, the hub conten might be developed with a web stack, and the issue might as well be something in the framework used there, if the time format query fails the US format is the fallback. But this is just speculation.
Still incorrect format in 15.020.
German is fine, US is fine. Just not UK.