Excel's short date formatting is based on the system's short date format, but it does not match it. That is not a minor inconsistency. It is a broken promise. When a user sets their system to display dates as "26 Feb 2026" and Excel shows "26-02-2026" instead, the software is not respecting the user's regional settings. Microsoft's own documentation admits that the default Short Date format can only be changed by updating system settings, and Excel reads the relevant registry key. But it does not honor what it reads. That is a design choice, not a technical limitation.
For anyone who works with dates daily, this is more than an annoyance. It erodes trust. You configure your operating system once, expecting every application to follow the same rules. Excel breaks that expectation. The user in this discussion has learned to live with workarounds, but the frustration is clear: Excel lies about respecting regional settings. The practical effect is that you cannot rely on Excel's default date display to match what you see in your system tray, your file explorer, or your other applications. Every date you enter or import requires a manual check, a custom format override, or a macro to correct the mismatch. That is lost time, repeated for every spreadsheet.
The deeper issue is that this problem is not new. It has been documented, discussed, and apparently accepted for years. The workarounds exist, custom number formats, locale-specific functions, even registry edits, but they should not be necessary. A spreadsheet tool that positions itself as the standard for data management should handle date formatting with the same fidelity it applies to numbers and text. When it does not, it signals that user productivity comes second to internal implementation shortcuts. That is not the kind of trade-off users should have to accept.
Our view is clear: Excel should either fully respect the system's short date format or provide a transparent, user-facing setting to override it. The current behavior, where the software reads a preference and then substitutes its own interpretation, is not a bug, it is a policy. And it is the wrong one. If you have ever wasted time reformatting dates that should have displayed correctly from the start, you know exactly what we mean. The solution is not another workaround. It is a commitment from Microsoft to make date display as reliable as every other default in the operating system. Until then, the workarounds remain your only option, and that is a failure of design, not of your understanding.