How to change and manage the language in CMD and Windows like a pro

If you've ever tried using the Windows command prompt and encountered folder names in English, messages in another language, or commands that don't work when you type them translated, it's normal to wonder how on earth it works. Language in CMD and what can actually be changedEven though the system is in Spanish, the console has its own rules and it's worth understanding them to avoid going crazy.

Throughout this article, we'll see, calmly and directly, which parts of the console language can be modified and which are fixed by design, how Windows regional settings affect it, and how to use advanced tools such as DISM to tap language and international settings Windows images, and also some related practical examples (for example, programs that use the registry or English Windows servers that you want to "Spanishize" without reinstalling). All of this is presented in accessible language, but without sacrificing technical rigor.

What can and cannot be changed in the CMD language

The first thing to clarify is a key point: the command prompt (CMD) is closely tied to the original Windows design, which was primarily developed in English. This means that Not everything you see on the console depends on the system language. Not everything can be translated.

On one hand, you have the information messages, warnings, and results that CMD displays (for example, when a command fails, or when running built-in tools). These messages do usually follow the Windows language you have configured as the display language, provided the language pack is properly installed.

On the other hand, there are commands themselves, system folder names, and certain internal pathsThese elements are programmed in English and are not translated, regardless of whether you have Windows in Spanish, German, or any other language. While it may seem counterintuitive, this is normal system behavior.

This raises the typical question: “If my user folder is called 'Documents', why do I have to type 'Documents' in CMD?”. The answer is that the “pretty” name you see in File Explorer may be translated, but the The actual directory name that the system understands is still in English..

Open CMD and execute something like:

dir C:\Users\TuUsuario

You'll see that the folders appear as Contacts, Documents, Downloads, Music, Picturesetc., although in the Explorer you see them as "Contacts", "Documents" or "Downloads". To navigate them in CMD you will have to use those names in English, because that is how the system has them registered internally.

Console messages vs. commands and paths: important differences

It is important to clearly distinguish between two concepts: the messages displayed by the console and commands and paths that you writeThey are different things and are not managed in the same way.

The texts that appear when using tools such as dir, ipconfig, dism or the system itself (for example, “Access denied” or “The system cannot find the specified path”) usually depend on the display language that Windows hasIf you change the system language correctly, those messages will adapt.

In contrast, built-in Windows commands, such as dir, copy, move, cd, del or the names of their parameters, are designed in English and There is no official translation that makes them work with words in another language. That is, you won't be able to use "copiar" instead of "copy" or "mover" instead of "move".

The same applies to many system paths, registry keys, and special folder names. Even though you see "Programs" in the Start menu, internally the folder is called Program Files And that's how it should be written to the console. Hence, in practice, You will always need to use certain English terms when working at CMD.

It's not a glitch or a bugIt's not just a way to ensure that commands work the same in any language. It might seem a little confusing at first, but once you get the hang of it, it saves you a lot of trouble.

Change the language of messages in the CMD window

That said, there are aspects of CMD's language that you can adjust from within the window itself. One of them is ensuring that the console uses the Windows language you have configured, instead of a specific configuration that has been saved.

To review this, you can do the following:

1. Open the Symbol of the system (DCM)You can search for “cmd” in the Start menu or press Win + R, to write cmd and press Enter.
2. Right-click on the title bar from the CMD window and select the option Properties.
3. In the OptionsLook for a box related to the system language settings, usually something like this: “Use the system language”. If it is not checked, activate it.
4. Click on Accept and close the CMD window. Open a console again for the changes to take effect.

This ensures that the messages displayed by the console respect the display language configured in Windows and not an old or different one that might have been stored in that window.

If, however, the texts still appear in another language, it's also worth checking the settings of Windows region and language (from Settings or from the Control Panel, depending on the version) to confirm that everything is aligned: display language, regional format, keyboard, etc.

Regional and language settings in Windows 11 and their impact on CMD

Since Windows 11 it's quite simple change the language of the entire system without needing to reinstall. This not only changes the language of menus and windows, but also affects the language of the messages you see in tools like CMD, PowerShell or system applications.

To change the primary language of Windows 11The usual procedure would be:

1. Open the application Configuration from the Start button or with the shortcut Windows + I.
2. In the side panel, go to Time and languageYou will see an icon with a clock and a globe.
3. Choose Language and regionThis is where the display language and regional formats are controlled.
4. In the section Language, Click on Add a language within Preferred languages.
5. Find the language you want to use (for example, Spanish from Spain) and select it. Click on NextIf there are several variants of the same language, make sure you choose the correct region.
6. Check the box Set as my Windows display language and click on InstallYou can also activate optional features (voice, handwriting, etc.) if you are interested.
7. When the package installation is complete, Windows will display a message warning that it needs log out to apply the new language.
8. Log out and log back in. From then on, the Windows interface, most system applications, and messages from many tools will be displayed in the new display language.

Keep in mind that even if you change the language of the entire system, the Commands and internal routes will remain in English (by design), but most status messages, errors, and informational texts will adapt to the language you have chosen.

DISM and international commands for language and locale settings

When working at a more advanced level, especially with Windows offline images (for example, WIM files used for deployment in companies), a very powerful tool comes into play: DISM.exe (Deployment Image Servicing and Management). Among other things, it allows you to view and modify the international and language settings of an image, which in turn determines the interface language, regional settings, and some of what will be seen in CMD in that installation.

The basic syntax of DISM For these uses it is usually:

DISM.exe {/Image:<ruta_imagen_sin_conexion> | /Online} {opcion_servicio}

Regarding language and international settings, DISM offers several types of international commands that can be used both in the running system (/Online) as if on a mounted image (/Image:Ruta):

• Query commands (Get): They are used to obtain a report of the international configuration and languages ​​of an image or the current system.
• Set commands: allow you to define interface language, system regional settings, user language, keyboard, time zone, etc., mainly in offline images.
• Gen-LangINI Commands: create or regenerate the file Lang.ini, which is used during Windows installation to define available languages ​​and the installer's default language.

To view international settings From a system that is already running, you can use:

DISM.exe /Online /Get-Intl

If what you want is to work with an uncompiled imageThe usual practice is to use:

DISM.exe /Image:C:\ruta\a\la_imagen /Get-Intl

The tool also offers contextual help. If you add /? after a commandYou will see detailed information about its syntax and parameters, for example:

Dism /image:C:\test\offline /Set-UILang /?
Dism /online /Get-intl /?

Main DISM options for language and international settings

DISM includes a good number of parameters to address all aspects of a Windows image. Each command focuses on a specific part of the configuration, and It is important to use them carefullyespecially in production environments.

/Get-Intl

The command /Get-Intl shows a summary of the international settings and installed languages in an image or in the running system.

• With /Online You get the data from the system you are using.
• With /Image:<ruta_imagen> You can view an image offline.
• In combination with /DistributionYou can view international information for an installation distribution, including expected locations of language packs of the type …\Langpacks<nombre_localidad>\Lp.cab.

/Set-UILang

Parameter /Set-UILang It serves to establish the primary user interface language (UI) of an image. The language must already be installed; otherwise, the command will fail.

Usage example:

Dism /image:C:\test\offline /Set-UILang:fr-FR

In this case, the offline image is configured to use French from France as the default user interface language.

/Set-UILangFallback

With /Set-UILangFallback is established interface reservation language for images with partially localized packages (when the main language does not translate all elements).

Example:

Dism /image:C:\test\offline /Set-UILangFallback:en-US

This is how it is defined English United States) as a fallback language for the interface in case the primary language does not cover all resources.

/Set-SysUILang

The command /Set-SysUILang adjust the preferred system interface languageAs with other commands, the language must be present in the image; otherwise, an error will occur.

Usage example:

Dism /image:C:\test\offline /Set-SysUILang:fr-FR

/Set-SysLocale

The option /Set-SysLocale change the language of programs that are not Unicode (system regional settings) and certain font settings. This setting is important for older applications that depend on a specific code page.

Example:

Dism /image:C:\test\offline /Set-SysLocale:fr-FR

/Set-UserLocale

With /Set-UserLocale define the standards and formats for the userThat is, the default language and format for dates, times, currency, numbers, and sorting.

Example:

Dism /image:C:\test\offline /Set-UserLocale:fr-FR

/Set-InputLocale

Parameter /Set-InputLocale It serves to specify the input and configurations keyboard layouts These will be used in an offline image. It allows you to include multiple keyboards separated by semicolons, defining which one will be the default.

Examples of use:

Dism /image:C:\test\offline /Set-InputLocale:fr-fr
Dism /image:C:\test\offline /Set-InputLocale:0410:00010410

Valid values ​​correspond to the language identifiers and keyboard layouts present in the register under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts.

/Set-AllIntl

The option /Set-AllIntl It is a kind of "global shortcut" that establishes several international parameters at once in the same language: UI language, system locale, user locale, and input locale.

Example:

Dism /image:C:\test\offline /Set-AllIntl:fr-FR

Individual configurations take priority If you combine this command with other specific parameters (for example, /Set-InputLocale).

/Set-TimeZone

With /Set-TimeZone you can define the default time zone from a Windows image. DISM checks that the specified time zone string is valid.

Example:

Dism /image:C:\test\offline /Set-TimeZone:"W. Europe Standard Time"

It is important to use straight quotation marks For time zones with multiple words, such as “Pacific Standard Time”. If you copy the text from some documents (for example, Word) and curved typographic quotation marks slip in, the command might fail.

/Set-SKUIntlDefaults

The command /Set-SKUIntlDefaults automatically adjusts the full international configuration from an offline image to the default value associated with a given language pack: interface language, non-Unicode programs, standards and formats, input settings, keyboard layout, and time zone.

Example:

Dism /image:C:\test\offline /Set-SKUIntlDefaults:fr-FR

This command has some exceptions: for example, in Unicode-only languages, the system locale might not change even if the command executes successfully. Also, for Japanese or Korean keyboards, the keyboard driver portion doesn't adjust with this parameter, and it's necessary to use [the appropriate method/method]. /Set-LayeredDriver.

/Set-LayeredDriver

The option /Set-LayeredDriver It is used to indicate the suitable keyboard controller In the case of Japanese or Korean keyboards, there are different physical types (different number of keys, specific layouts, etc.).

Example:

Dism /image:C:\test\offline /Set-LayeredDriver:1

The possible values ​​cover different types of keyboards, such as the enhanced 101/102-key PC/AT keyboard or specific variants for Korea and Japan with 103/106 or 106/109 keys.

/Gen-LangINI

With /Gen-LangINI a is generated new Lang.ini file, used by the Windows installation program to identify which language packs are available and what the installer interface language is.

This file is saved in the folder Sources of the Windows distribution. It is necessary to specify both an offline image (/Image:<ruta_imagen.wim>) as the distribution route (/distribution:<ruta_distribucion>).

Example:

Dism /image:C:\test\offline /Gen-LangINI /distribution:C:\windows_distribution

/Set-SetupUILang

The command /Set-SetupUILang define the language that the Windows installation program will useIf that language fails for any reason, the installer automatically switches to English.

Example:

Dism /image:C:\test\offline /Set-SetupUILang:fr-FR /distribution:C:\windows_distribution

If this command is not used, the installer uses the following as a reference: default interface language of the image or, failing that, the first language available in the list.

/Distribution

The option /distribution simply indicates the path to the Windows distribution (the contents of the installation media). It is used in conjunction with /Get-Intl y /Gen-LangINI when there are external language packs that need to be taken into account.

Example:

Dism /image:C:\test\offline /Gen-LangINI /distribution:C:\windows_distribution

Limitations and considerations when modifying languages ​​with DISM

Although DISM is very flexible, It has a number of restrictions which should be respected to avoid problems when displaying images or changing international settings.

• It is not possible to combine international maintenance commands with other image maintenance commands on the same command line; they must be executed separately.
• The Unicode only languages These languages ​​cannot be set as the system locale. Examples include Amharic, Bengali, Hindi, Tibetan, etc. In these cases, the system maintains a compatible locale for non-Unicode programs.
• It is not recommended to install a language pack after an update that includes language-dependent resources. If you do it in that order, the language-specific changes introduced by the update may not be applied correctly. Ideally, you should install language packs first and then updates.
• When a time zone with /Set-TimeZoneIt is mandatory to use the correct quotation marks and ensure that the string exactly matches an entry of HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
• If you attend a international image in a host environment that does not support your languageYou may not be able to read some error messages generated by the attended image, which complicates troubleshooting.

Other related scenarios: registration, applications, and servers in English

Beyond CMD and DISM, there are scenarios where language is controlled in very specific ways, for example through the Windows registry or internal application settingsA typical example is that of programs that allow you to change their language after installation by editing a specific key.

For example, a business application installed on Windows might save a "Language" value in the registry with code like EN, DE, IT or SP to specify English, German, Italian, or Spanish. To modify it, the administrator would have to do something like this:

1. Open the registry editor with Start > Run > regedit.
2. Navigate to the corresponding key, for example HKEY_LOCAL_MACHINE > SOFTWARE > ProviderName > ApplicationName > Config.
3. Edit the value Language and change it to one of the valid codes (EN, DE, IT, SP).
4. Confirm with Acceptclose the registry and, if necessary, restart services or the web server (for example, with iisreset from CMD) to apply the language change.

In server environments, it is also common to encounter Windows Server originally installed in English and the subsequent need to work in Spanish. Although this affects the desktop and administrative tools more, the way to change it is usually similar to that of desktop Windows: go to Control Panel, search Clock, Language and Region, use the option Add a language, download the language packinstall it and mark it as primary display language.

After logging out and back in, the desktop, Start menu, administrative consoles, and most system interfaces will appear in the chosen language, while command-line tools will still require it. commands and internal names in EnglishHowever, they will display messages in the configured language as long as there is support in the installed packages.

Understanding how responsibilities are distributed between the system language, built-in commands, internal paths, and tools like DISM greatly helps avoid frustration when CMD seems to act independently regarding language. It also allows you to fine-tune each environment—whether it's a home PC, a laptop, a cloud server, or a mass deployment image—to display the correct system language. Information in the most convenient language, without losing compatibility or breaking the behavior of the commands.