intl.cpl in Windows: How Regional Settings Work, Their Benefits, and Safe Configuration

QUICK ANSWER

intl.cpl opens the classic Region Control Panel page in Windows. It lets you manage regional formatting—such as date, time, numbers, currency, and list separators—and provides administrative options for the welcome screen, new user profiles, and the system locale used by legacy non-Unicode applications.

Regional format, Windows display language, keyboard layout, geographic region, time zone, and system locale are separate settings. Change only the setting relevant to your problem. In current Windows versions, Microsoft has moved some international options to Settings, so intl.cpl does not manage every language or region feature. Microsoft Learn

What is intl.cpl?

intl.cpl is the command associated with the classic Windows Region Control Panel item. A .cpl file is a Control Panel component rather than a normal command-line utility.

Its principal purpose is to configure how Windows and compatible applications present locale-sensitive information, including:

• Short and long dates
• 12-hour or 24-hour time
• Decimal and digit-grouping symbols
• Measurement systems
• Currency symbols and formats
• List separators
• First day of the week
• Formats used by some applications when displaying or interpreting data

Windows identifies locales with language tags such as en-US, en-GB, de-DE, and fr-FR. Modern Windows locale names follow BCP 47-style language-tag conventions. Microsoft Learn

The canonical Control Panel name for the corresponding item is Microsoft.RegionAndLanguage. Microsoft Learn

How to open intl.cpl

Use the Run dialog

1. Press Windows key + R.
2. Enter:

intl.cpl

3. Press Enter.

Use Command Prompt or PowerShell

Run either of these commands:

control.exe intl.cpl

control.exe /name Microsoft.RegionAndLanguage

On Windows Server Core, Microsoft documents control intl.cpl as the command for opening international settings when the applicable interface components are available. learn.microsoft.com

Use Windows Settings

On Windows 11, most commonly used options are also available under:

Settings > Time & language > Language & region

Microsoft is gradually moving Control Panel functionality into Settings. intl.cpl can manage features that remain on its page, but it is not a supported interface for settings that have already migrated. Microsoft Learn

How Windows regional settings work

Windows maintains several international settings that users often mistake for one another.

Changing one setting does not necessarily change the others. For example, selecting en-GB as the regional format does not automatically change the Windows display language, keyboard layout, time zone, or system locale. Microsoft likewise documents that display language and region are independent settings. Microsoft Learn

Regional format and custom formats

The regional format determines the default cultural conventions used by Windows and applications that honor the current user’s locale.

For example, changing the regional format can affect:

• Whether a date appears as 20/09/2026 or 9/20/2026
• Whether time appears as 14:30 or 2:30 PM
• Whether a decimal appears as 1.5 or 1,5
• Whether thousands appear as 1,000 or 1.000
• How negative numbers and currency values are displayed
• Which character is used as the list separator

To customize these values:

1. Open intl.cpl.
2. Select the required format.
3. Choose Additional settings.
4. Review the Numbers, Currency, Time, and Date sections available on your Windows version.
5. Select Apply, and then select OK.

Important application behavior

Applications decide whether to honor Windows regional settings. Some applications use:

• Their own language or formatting preferences
• A document-level locale
• An online account or cloud-service region
• An organization-controlled policy
• A database or application-specific format

Windows regional settings may therefore change how data is displayed without changing the underlying stored value. Microsoft recommends that applications store persistent information in locale-independent formats and apply the user’s locale only when presenting it. Microsoft Learn

System locale for non-Unicode programs

The system locale is mainly a compatibility setting for older applications that do not use Unicode. It determines the default ANSI, DOS, and Macintosh code pages and related font fallback used by the computer. It is not the same as the regional format for the signed-in user. Microsoft Learn

You may need to change it when a legacy application:

• Displays question marks or unreadable characters
• Uses the wrong characters for Japanese, Chinese, Korean, or another legacy encoding
• Expects a particular Windows code page
• Was designed before widespread Unicode support

To change it through the graphical interface:

1. Open intl.cpl.
2. Open the administrative settings offered by your Windows version.
3. Select Change system locale.
4. Choose the locale required by the legacy application.
5. Confirm the change.
6. Restart Windows.

Administrator permission is required, and a restart is necessary before the new system locale takes effect. Microsoft Learn

Warning about changing the system locale

Do not change the system locale merely to alter date, time, or currency formatting. Use the regional format instead.

A different system locale can cause another legacy application to misread file names, text files, or application data created under a different code page. Prefer an updated Unicode-compatible version of the application whenever one is available.

UTF-8 worldwide language support

Some Windows versions display a Beta: Use Unicode UTF-8 for worldwide language support option in the system-locale dialog. This changes the system active code page to UTF-8 for applications that rely on it.

Enable it only after confirming that all business-critical legacy applications, drivers, import/export processes, and scripts support this configuration. Older programs may assume a traditional Windows code page and behave incorrectly. Record the original setting and test the change before deploying it broadly.

Copying settings to system and new-user accounts

The administrative section may allow an administrator to copy selected settings from the current user to:

• The welcome screen and system accounts
• New user accounts created afterward

On supported systems, Microsoft also provides the following elevated PowerShell cmdlet:

Copy-UserInternationalSettingsToSystem `
    -WelcomeScreen $true `
    -NewUser $true

This can copy the current user’s display language, input language, regional format, and geographic location to the selected system targets. It does not retroactively reconfigure every existing user profile. learn.microsoft.com

Review the current user’s settings carefully before copying them. The operation can affect the sign-in screen, service accounts, system processes, and defaults inherited by future profiles.

Country or region and Microsoft Store limitations

The Windows Country or region setting can influence localized content and applications, but it is not equivalent to:

• Windows display language
• Regional date and number formats
• Microsoft account country
• Store billing address
• Xbox account or subscription region

Microsoft recommends changing a Microsoft Store account region only when moving to another country or region for an extended period. Store purchases, subscriptions, available content, billing information, and account balances may be region-dependent; Microsoft account funds do not transfer between regions. Microsoft Support

Benefits of configuring intl.cpl correctly

Correct regional configuration provides several practical benefits:

• Dates, times, numbers, and currency appear in familiar formats.
• Spreadsheet and database entry is less likely to be misinterpreted.
• Business applications receive appropriate locale defaults.
• CSV and delimited-data workflows can use the expected separators.
• Legacy non-Unicode software can display the intended character set.
• Sign-in screens and new profiles can receive consistent organizational defaults.
• Users working in another language can retain a different display language while using the required business formats.

These benefits depend on application support. Programs that use independent settings may need to be configured separately.

Verify the current configuration

Graphical verification

Open intl.cpl and inspect:

• The selected regional format
• The example date, time, and number formats
• Customized separators and patterns
• The reported system locale under administrative settings

Also review:

Settings > Time & language > Language & region

This helps identify a mismatch between regional format, Windows display language, preferred languages, keyboard layout, and geographic region.

PowerShell verification

Run the following commands in PowerShell:

Get-Culture
Get-WinSystemLocale
Get-WinHomeLocation
Get-WinUserLanguageList

These report different settings. Get-Culture represents the current user’s culture, while Get-WinSystemLocale reports the computer’s legacy system locale.

A typical culture name might be:

en-US

Do not assume that matching language tags prove every international setting is identical; keyboard layouts, language lists, location, time zone, and customized format overrides are separate.

Configure regional settings with PowerShell

Change the current user’s culture

For example, to set the current user’s culture to English (United Kingdom):

Set-Culture -CultureInfo en-GB

Set-Culture changes the culture for the current user. Microsoft notes that its effects appear in subsequent PowerShell sessions; applications may also need to be closed and reopened. Microsoft Learn

Verify the result in a new PowerShell session:

Get-Culture

Change the system locale

To set the system locale to Japanese:

Set-WinSystemLocale -SystemLocale ja-JP

Run this from an elevated PowerShell session and restart Windows afterward. The command changes a computer-wide compatibility setting for non-Unicode programs. Microsoft Learn

Verify it with:

Get-WinSystemLocale

Deployment and Windows imaging

For managed deployments, Microsoft supports:

• The Windows PowerShell International module
• Windows Setup answer files
• DISM international-servicing commands

For example, an administrator servicing an offline mounted Windows image can inspect and configure its international settings with commands such as:

Dism /Image:C:\Mount\Windows /Get-Intl
Dism /Image:C:\Mount\Windows /Set-AllIntl:fr-FR

These examples apply to an offline Windows image mounted at that exact path, not automatically to the currently running operating system. Set-AllIntl changes multiple international defaults in the image, so administrators should review Microsoft’s servicing documentation before using it. learn.microsoft.com

Troubleshooting intl.cpl and regional settings

intl.cpl does not open

Try:

control.exe intl.cpl

If that fails:

1. Open Settings > Time & language > Language & region.
2. Install pending supported Windows updates.
3. Restart Windows.
4. From an elevated terminal, check protected system files:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Do not download a replacement intl.cpl file from an unofficial website. System components obtained from third-party download sites may be incompatible or malicious.

A program still shows the old format

• Close and reopen the program.
• Sign out and sign back in if necessary.
• Confirm that you changed the correct user account.
• Check whether the application has its own regional setting.
• Check document, workbook, database, browser, or cloud-account settings.
• Determine whether organizational policy reapplies a standard configuration.

Dates or numbers are interpreted incorrectly

Inspect both the displayed format and the underlying data. A value such as 03/04/2026 is ambiguous and may mean March 4 or 3 April.

For data exchange, logs, APIs, and scripts, prefer unambiguous locale-independent formats where supported—for example, an ISO-style date such as 2026-04-03. Do not change organization-wide separators without testing spreadsheets, CSV imports, accounting applications, and automated scripts.

A legacy application displays unreadable text

1. Identify the language and code page expected by the application.
2. Confirm that the program is genuinely non-Unicode.
3. Check Get-WinSystemLocale.
4. Change the system locale only if the software requires it.
5. Restart Windows.
6. Test the application and its existing data.
7. Restore the original locale if other legacy applications stop working.

Settings return after sign-in or restart

The value may be controlled by:

• Group Policy or mobile-device management
• A provisioning package
• A sign-in or deployment script
• Profile-management software
• A synchronized organizational configuration

Ask the system administrator before repeatedly overriding a managed setting.

Security and administration considerations

• Standard users can normally change many settings for their own profile.
• Changing the computer-wide system locale requires administrator permission.
• Copying settings to system accounts or new-user defaults is an administrative operation.
• Restart Windows after changing the system locale.
• Test locale changes against business applications before broad deployment.
• Record the previous configuration so it can be restored.
• Prefer documented PowerShell, Windows Setup, or DISM methods for managed deployments.
• Avoid direct registry editing unless a specific, supported product procedure requires it.
• Do not treat regional settings as a security control or a reliable method of changing an online service’s legal or billing region.

FAQ

Frequently asked questions

Is intl.cpl safe to run?

Yes. intl.cpl is the standard Windows Region Control Panel component. Opening it does not alter anything until you apply a change. Use the Windows-provided component and never download a replacement from an unofficial source.

Does intl.cpl change the Windows display language?

Not necessarily. Regional formatting and display language are separate. Manage the Windows display language and language packs under Settings > Time & language > Language & region.

Does intl.cpl change the keyboard layout?

Changing the regional format does not automatically change the keyboard layout. Keyboard layouts are managed through the installed language and input options.

What is the difference between regional format and system locale?

Regional format controls how the current user sees dates, numbers, times, and currency. System locale selects legacy code pages and font fallback for non-Unicode applications across the computer.

Do I need administrator permission?

You generally do not need administrator permission to change your own regional format. Administrator permission is required for system-wide actions such as changing the system locale or copying settings to system accounts.

Why must Windows restart after a system-locale change?

The system locale affects computer-wide code pages and related resources used by legacy software. Windows applies the new setting after a restart.

Can changing regional settings damage files?

A normal format change does not rewrite all files. However, applications may interpret ambiguous dates, decimal separators, list separators, or legacy encoded text differently. Back up important data and test business workflows before making broad changes.

Can intl.cpl change my Microsoft Store country?

It can change certain Windows geographic settings, but Microsoft account country, Store billing information, subscriptions, balances, and content availability have separate rules. Changing the Windows setting alone may not update them.

Can IT administrators automate these settings?

Yes. Depending on the requirement, Microsoft supports the Windows PowerShell International module, Windows Setup answer files, and DISM servicing commands. Administrators must distinguish between current-user, system-wide, new-profile, and offline-image settings.

FINAL RECOMMENDATION / CONCLUSION

Use intl.cpl when you need detailed regional formatting or administrative locale options that remain in the classic Region Control Panel. Use Settings > Time & language > Language & region for modern display-language, preferred-language, keyboard, and geographic-region management.

For most date, number, time, or currency problems, change only the current user’s regional format. Change the system locale only for a confirmed legacy non-Unicode application requirement, and test the result after restarting. In managed environments, document the original configuration and use Microsoft-supported PowerShell, answer-file, or DISM methods instead of registry modifications.

 

#Windows #intlCpl #RegionalSettings #Windows11 #WindowsServer #SystemLocale #RegionalFormat #WindowsLanguage #ControlPanel #PowerShell #ITSupport #WindowsAdministration #LegacyApplications #Unicode #DateFormat #LanguageAndRegion #Troubleshooting #DISM

SOURCES

• Configure International Settings in Windows — Microsoft Learn Microsoft Learn
• Manage language and keyboard settings in Windows — Microsoft Support support.microsoft.com
• Set-WinSystemLocale — Microsoft Learn Microsoft Learn
• Set-Culture — Microsoft Learn Microsoft Learn
• Copy-UserInternationalSettingsToSystem — Microsoft Learn learn.microsoft.com
• Locales and Languages — Microsoft Learn Microsoft Learn
• Locale Names — Microsoft Learn Microsoft Learn
• Using Persistent Locale Data — Microsoft Learn Microsoft Learn
• Change your country or region in Microsoft Store — Microsoft Support Microsoft Support