Hello Scott, :)

You could change the display language of Windows 10 using the method in the tutorial below.

https://www.tenforums.com/tutorials/3...dows-10-a.html

Thank you Shawn, very much. I believe the following comments will save at least some readers a large amount of time:

1. If one is trying to change the System Default UI language (and not the displayed language of an individual user), then the relevant tutorial is not the one you cite above, but is instead: https://www.tenforums.com/tutorials/3815-region-language-settings-copy-windows-10-a.html (How to Copy Region and Language Settings to Welcome Screen and New User Accounts in Windows 10)

2. If you're like me, you don't want to really change the default system UI language at all. Your problem is that you have in your hand an upgrade .iso, but the upgrade won't allow you to preserve apps setting and files because the 'edition' of the iso isn't the 'same' edition as your current installed Windows. And logic tells you this can't be the real reason you can't preserve files apps and settings, because OF COURSE the .iso is of a different edition -- that's why you using it at all, to UPGRADE.
The shameful truth is that it is the system default UI language which is likely to be different between the .iso and your installed Windows. None of the other language settings seem to matter, although YMMV. Rather than go through the rather delicate procedure in the tutorial just cited, i found that indeed if I just change the value of the "default" key of this tutorial, changing to the correct, desired, LCID (i.e. the one matching the upgrade .iso), then the command dism /online /get-intl reports the system default UI Language to be immediately changed. So you can proceed with the upgrade, and --miracle of miracles -- you can keep files apps and settings.

When the upgrade completes, it is probably safer to restore the registry value using he control panel Region settings in the tutorial mentioned in the previous paragraph. However you choose to do it, making the default system UI language agree between the current installation and the upgrade media was absolutely critical to keeping my apps settings and files.

Hi Shawn,

First of all allow me to send my warmest wishes for a very Happy Easter, to you and your loved ones!!!

I seem to have a PowerShell culture problem. Let me be more detailed:

1. Installed language: en-us = English (United States)



2. Locale (Region): en-150 = English (Europe)



3. PowerShell shows culture en-us and subsequently date format M/d/yyyy whereas,
Powershell ISE, shows culture en-150 and subsequently date format dd/MM/yyyy (which is the preferred for me)





Any idea? How can I change the PowerShell to the en-150 culture? If I run the command Set-Culture en-150, nothing happens.

Hello Dimitri, and Happy Easter to you as well. :)

That is a bit odd.

Have you already tried changing the "Format" in "Region" CP to something else, apply, change it back to "English (Europe)", and apply to see if that may help?

Yes I had tried that, but did again, with no success.

I was running some commands in PowerShell and I noticed the following:



The en-150 "English (Europe)" is a UserCustomCulture and is neither InstalledWin32Culture nor FrameworkCulture. Maybe PowerShell can only set "InstalledWin32Cultures" and/or "FrameworkCultures".

Now how come by running the same command ("Get-Culture"), the PowerShell ISE reports as current culture the correct en-150, whereas PowerShell reports en-us, I have no clue!

Strange conflicting settings.

What does it show for you in the registry key below? This is for the current user setting.

HKEY_CURRENT_USER\Control Panel\International

Brink said:

Strange conflicting settings.

What does it show for you in the registry key below? This is for the current user setting.

HKEY_CURRENT_USER\Control Panel\International