How to change the GeoID and regional settings in Windows 11

If you've ever tried to change the regional settings and GeoID in Windows 11You've probably noticed that, in theory, it seems like a very simple change… but in practice it's not so simple, especially if you want it to affect all users on the computer and not just your session. The information available online is often quite scarce or confusing, and many tutorials fall short when it comes to… apply those adjustments at the system level.

In this article we will look in detail How do the Country/Region, Regional Format, and GeoID settings actually work in Windows 11?What are the implications for date, time, numbers, and currency? Why do PowerShell commands only change settings for the current user? And how can you force those changes to apply to every new account that logs on to the computer using a GPO, a scheduled task, and a RunOnce registry entry?

What is GeoID and regional settings in Windows 11?

Before touching anything, it's important to be clear What exactly is changing when you modify the regional settings? of Windows 11. We're not just talking about the interface language, but a whole series of parameters that determine how dates, times, numbers, decimal separators, and currency symbols are displayed and interpreted in the system and in applications.

The call GeoID It is an internal numerical identifier that Windows uses to represent the computer's country or region. Each territory has a specific number associated with it, and Windows uses this value to adapt certain system behaviors, such as localized services, regional content, or some location-based personalization options.

Furthermore, the regional settings It defines how date, time, numeric, and monetary data are displayed. For example, if you enter 11/19/2023 in the date field, the final format you see (with slashes, hyphens, month name, day/month/year order, etc.) will depend on the regional settings configured in Windows for that user or the system.

This directly affects working with applications like Access, Excel, or any program that relies on system formats. You can enter amounts with the pound symbol (£)However, if Windows has the euro set as the default currency, the system may display those amounts with the € symbol, as it depends on the regional settings and not necessarily on what you typed.

In short, when you change the country or region and regional format in Windows 11, you are influencing the way the system interprets and presents information which is based on date, time, number and currency data, both in the Windows interface itself and in the programs that rely on that configuration.

Differences between country or region, regional format and other adjustments

Within Windows 11 Settings, in the Time and Language section, several settings appear that are often mixed up: Country or region, Regional format and language settingsAlthough they may seem the same, each one affects a different part of the system.

The setting of Country or region It is closely linked to the GeoID. When you select Spain, the United States, Mexico, or any other country, Windows internally updates this location identifier. This data can be used by both the system itself and some applications to offer localized content, adjust services, or optimize the user experience based on the configured location.

El Regional formatHowever, it focuses more on how the data is displayed: the order of day, month, and year in dates, whether periods or commas are used for decimals, the type of thousands separator, the currency symbol, the short and long time formats, etc. For example, using the Spanish format means seeing something like 19/11/2023 and 13:45, while a US format typically displays 11/19/2023 and 1:45 PM.

Finally, the language settings This refers to the language of the Windows interface (menus, dialog boxes, messages) and the installed language packs. Although it's usually linked to the regional settings, you can actually mix and match: have Windows in English but with the Spanish regional format, or vice versa, if you want to work with the numbering and date standards of a specific country but keep the interface in another language.

All of this explains why, when you adjust the region settings, sometimes you only notice changes in how dates or currency are displayed, but not in the interface language, or vice versa. Each group of options acts on a different layer of the system, even though they are all under the umbrella of “regional and language”.

Change GeoID and regional settings with PowerShell in Windows 11

If you only want to change the settings for your own user, PowerShell offers very direct commands This allows you to adjust the GeoID and regional settings without having to click through the graphical interface. This approach is very useful for automating tasks or applying quick changes using scripts.

One of the key commands is Set-WinHomeLocationThis allows you to set the device's primary location using the country's numerical identifier (the GeoID). A typical example would look something like this:

Set-WinHomeLocation-GeoId 244

In this case, the value 244 corresponds to a specific country or region; each number is associated with a different territory. Running this command updates your Windows home location, which in practice is equivalent to changing the country or region the system uses for certain services.

On the other hand, for the system's regional settings (the location used by system processes and applications that rely on that setting), there is the command Set-WinSystemLocaleA common example would be:

Set-WinSystemLocale en-US

This indicates that the system's regional settings should use the format corresponding to US English. This impacts how certain applications and system services display text, dates, and other location-sensitive data.

The problem arises when you discover that, When these commands are launched, the changes only affect the current user.Especially if you run it within the context of your interactive session. If you then log in with another account or create a new user profile, those settings won't be automatically applied.

Why do the changes only apply to the current user?

The reason for this behavior lies in how Windows manages user profiles and regional settings. Many of these options are stored in the Windows registry under the HKCU key (HKEY_CURRENT_USER)which is specific to each user. This means that, although the command appears to operate at the "system" level, in practice the visible effect remains within the scope of the session in which it is executed.

When you install Windows 11 for the first time and choose a country or region during the wizard, those settings are applied to a sort of default profile template that the system uses as a base for new users. From there, each account inherits certain initial parameters, but can have its own variations if the user modifies its settings.

The problem is that, once the system is installed and running with multiple accounts, simply changing the region settings for one user is not enough to prevent it from working. all existing profiles and those created from that moment on These new values ​​will be automatically adopted. Windows does not rewrite the profile template by default, nor does it force regional settings on existing accounts.

In home environments this may not be a big deal, but in corporate networks or shared equipment it can be a hassle to have users with different configurations, with dates displayed one way for some and another way for others, or with inconsistent currency symbols depending on who logs in.

That's why the need arises to Apply the GeoID and regional settings changes "system-wide"That is, to ensure that each user who accesses the equipment receives consistent settings without having to configure them manually one by one.

“Global” location of the configuration and actual limitations

When it comes to region and language, many people wonder where that supposed “secret location” in the system where the global configuration is stored which affects all users. The reality is that there is no single magic file or registry value that controls absolutely everything.

Windows distributes location information across several parts: registry keys under HKLM (HKEY_LOCAL_MACHINE) for certain general system values, keys under HKCU for each user's specific preferences, and, in addition, the aforementioned default profile template used when creating new accounts. This makes changing it manually for everyone impractical and prone to errors.

In theory, you could try directly modifying the profile template or applying scripts that overwrite settings, but it's a delicate solution. It is much more robust to rely on tools designed for centralized administration, such as Group Policies (GPOs) and scheduled tasks, which allow actions to be executed under certain conditions and user contexts.

The key is to understand that, even if you want a “global” configuration, What you're actually going to do is force each user to apply those changes locally. The first time you log in, this happens automatically and without manual intervention. This is where the idea of ​​using a GPO to deploy a PowerShell script via a scheduled task and a RunOnce registry entry comes in.

Apply GeoID and regional settings to all users with GPO

An effective way to solve the problem is to create a Group Policy (GPO) This generates a scheduled, one-time task on each computer. This task then creates a registry entry in RunOnce for each user, and that entry launches a PowerShell script responsible for changing the region using the appropriate commands.

The workflow, to simplify, is as follows: first, the GPO is applied to the team or users, depending on your decision. That GPO create a scheduled task which runs only once, with the appropriate permissions, to register a key in HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce. That RunOnce key points to a PowerShell script that contains the instructions for changing the GeoID and locale settings.

The log entry generated by the scheduled task has a structure similar to:

REG add HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce /v !SetRegion /t REG_SZ /d «powershell.exe -file \\%path_to_script%\LocaleSettings.ps1»

That command adds a value called, for example, !SetRegion within the user's RunOnce key. The data type is REG_SZ (text string) and its content indicates that, when the RunOnce condition is met, Windows should execute PowerShell with the LocaleSettings.ps1 script located in the shared path or folder that you defined in %path_to_script%.

That LocaleSettings.ps1 script will include the necessary PowerShell commands, typically something like Set-WinHomeLocation-GeoId 244 y Set-WinSystemLocale en-US (or the values ​​you need in your case). This way, when the user logs in, the RunOnce entry will cause those instructions to be executed and the region settings will be applied to that account.

The advantage of this approach is that, being based on a GPO and RunOnce, The changes are applied automatically for each new user that logs into the computer, without anyone having to manually open PowerShell or touch Windows settings. It's only necessary to keep the script available in the designated path.

How exactly does RunOnce work in the Windows registry?

RunOnce is one of the classic Windows registry keys designed to Run commands or programs only once when the user logs in.It is located within the HKEY_CURRENT_USER branch for actions linked to each profile, and there is also a variant in HKEY_LOCAL_MACHINE for the entire machine.

Each value you add to HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce represents an instruction that the system will automatically execute the next time the user logs in. Once the command is executed, Windows typically removes that entry to prevent it from being repeated.

That makes it a perfect tool for apply initial or single-use configurationsFor example, you can change the region and GeoID you want to apply to each user profile. By placing a PowerShell script call there, you ensure the settings are applied on the first login without having to force further changes later.

In this case, the scheduled task generates a RunOnce entry that points to powershell.exe with the -file parameter followed by the script path, for example, LocaleSettings.ps1. Thus, when the user logs on, Windows executes that script, applies the Set-WinHomeLocation and Set-WinSystemLocale commands (or any others you may have included), and then deletes the RunOnce entry, completing the operation.

In this way, the administrator It avoids having to manually edit each user's record. And at the same time, it maintains centralized control over what runs and when, something especially useful in Active Directory domains and business environments with tens or hundreds of computers.

Relationship between Access, date formats, and regional settings

An important point that is often overlooked is how Windows regional settings It directly impacts applications like Microsoft Access, and how to troubleshoot date and time issues in Microsoft Office This can help avoid inconsistencies, since these applications rely heavily on how the system represents dates, times, and numbers.

When working in Access, you can enter dates in a specific format, for example using slashes (11/19/2023) or writing the month in words, but the result you see when applying a format like "General Date" depends not only on how you typed it, but also on the regional formats that are configured in WindowsIf the settings are in US English, the order and style may differ from a Spanish format.

The same applies to numerical and financial data. If you have Windows configured to use the euro as the currency symbol, but you enter amounts using the British pound (£) symbol, Access may choose to display those amounts with the € symbol, adapting to the system currency. Everything is governed by what Windows considers the currency and its default formats.

This means that, if users on a shared computer or corporate network have different regional settingsYou might find databases that look different depending on who opens them: dates in different orders, currencies that change symbols, and even problems interpreting commas and periods in decimals.

That's why it's so important to ensure that the region and GeoID settings are consistent across all profiles. Applying common settings via GPO, scheduled tasks, and RunOnce not only provides aesthetic uniformity, but also... avoid mistakes and confusion in applications that are heavily dependent on location, such as Access, Excel, or billing systems.

If you need to change the regional settings in Windows, the classic procedure involves going to the operating system's Settings and manually adjusting the country or region and regional format. However, when we're talking about dozens of users or a corporate standardRelying on automation and scripts is almost mandatory to maintain consistency.

Ultimately, mastering the relationship between GeoID, regional settings, PowerShell, GPO, and RunOnce It allows you to fine-tune the system so that all users work with the same date, time, number, and currency formats, minimizing surprises and errors in applications that rely most on these settings.

This whole approach, although it may seem somewhat technical at first glance, ends up being a very practical way to ensure that Windows 11 behaves the same for any user who logs into the computer, respecting the location you need in your work environment and avoiding the chaos of different configurations in each profile.