Windows Server ships in English with a US keyboard. What actually gets in the way day to day is not the English menus but symbols coming out wrong and the clock not being yours (logs, scheduled restarts and wipes all go by it). Everything is fixed from PowerShell as administrator.
Your keyboard layout
For example, for a UK keyboard:
Set-WinUserLanguageList -LanguageList en-GB -ForceUse your own language tag: es-ES (Spanish), fr-FR (French), de-DE (German), pt-PT (Portuguese)... Log out of the remote desktop session and back in. If you have several layouts, switch between them with Win + Space.
Your local time
# UK and Ireland
Set-TimeZone -Id "GMT Standard Time"Other common time zones:
| Where | Identifier |
|---|---|
| Spain, France, Germany, Italy | Romance Standard Time / W. Europe Standard Time |
| US East Coast | Eastern Standard Time |
| US Central | Central Standard Time |
| US West Coast | Pacific Standard Time |
| Brazil (São Paulo) | E. South America Standard Time |
If yours is not there, search by city name:
Get-TimeZone -ListAvailable | Where-Object DisplayName -like "*Lisbon*"Windows handles daylight saving changes by itself.
Date and number format
To see dates as 31/12/2026 instead of the US format:
Set-Culture en-GBIt changes how dates appear in File Explorer and many programs. Log out and back in to see it everywhere.
What about the menu language?
On Windows Server 2022 the interface language is installed from a separate language pack, not from Settings as on regular Windows. In practice it is not worth it: English menus affect nothing, and almost every game server guide is written for Windows in English, so it will be easier to follow them.