Changing the System Regional settings after installation using the command-line


Usually you set up the regional settings at installation time by using localized OS Version or unattended.xml. However sometimes you discover after installation that some script from your customer run under the system context needs different settings. In this case changing the system regional settings after installation using the command-line can be very useful and time-saving

As outlined in the Vista International Settings Guide, you must create an XML File which would be then executed by the regional settings control panel applet.

Creating the XML file

There are plenty of options, so here is an example which allows to change the locale to English (United Kingdom) for all users (system and new users)

There are 3 groups to outline here:

  • the <gs:UserList> tag tells which users will be impacted. Here the 2 attributes CopySettingsToDefaultUserAcct and CopySettingsToSystemAcct imply the setting will be copied into HKEY_USERS\.Default and the System profile.
  • the <gs:UserLocale> define the locales and keyboard we’ll be adding.  Here we just change the locale
  • the <gs:SystemLocale> is used for all non-modern programs which do not use specific settings.

Once you’ve create this XML file, you must pass it to the following command:

 

Checking results in the logs

If you need to check if the settings have been properly applied, you must look into the Applications and Services Logs, Microsoft, Windows, International in the Operational Logs. A successful change is event 13000 under Task Category “NLS Unattended and Regional Settings Options”

If you specified CopySettingsToDefaultUserAcct and everything is valid, Event ID 13009 will be present:

If you specified CopySettingsToSystemAcct and everything is valid, Event ID 13010 will be present:

The list of Windows available locales will guide you the list of locales you can use. Please be sure to read this list as abbreviations may differ from common sense (e.g. English (UK) is en-GB, not en-UK).

Leave a comment

Your email address will not be published. Required fields are marked *