Recent content by Brutser

garlin Thanks for the explanation! I was not really trying to script anything, but rather noticed this after installation on a virtual machine. But then it's still not expected, because MyUser (the standard user) opens an elevated terminal, authenticates as MyAdmin user (the admin user), then...

When I opt to include updates Microsoft.UI.Xaml.2.8 and the Windows Package Manager (app installer, winget), then I notice the following behavior: Logged in to Windows 11 as Standard User: - When opening the terminal as Standard User, winget command works as expected. - When open the terminal...

garlin I was too soon, the script works fine, I made some small changes and final script is very easy, running after logon (user): # US International keyboard $LanguageList = New-WinUserLanguageList en-US $LanguageList[0].InputMethodTips.Clear()...

I understand and I tried his solution, but after-logon worked fine, but only for future users, not the current admin user. When before-logon with the same solution, nothing happened, also not for future users, the registry settings were not there and NTUSER.dat was probably not modified (did not...

garlin if I put the script in separate commands (after logon), it works except for the keyboard section, i guess the variable I cannot use over multiple commands, so that is why I tried putting it all in a script.

garlin but I use it After logon (BeforeLongonMode="0") to set it for the default admin user, so after this all users will be created.

Found some solution, though it is not perfect, it should work: Powershell script: # US International keyboard $List = Get-WinUserLanguageList $List[0].InputMethodTips.Remove('0409:00000409') $List[0].InputMethodTips.Add('0409:00020409') Set-WinUserLanguageList $List -Force # Belgian regional...

So the new user shows this in Language Settings, it's really insane, it still shows French (Belgium) and the French keyboard: Yet, the actual keyboard is indeed the US International keyboard as set with the registry settings, what is going on?

Yes, this at least set it correctly for the new user, now all I have to do probably is run the powershell commands for the admin user as garlin showed before, then I will add the standard user also from powershell, because if I would create this from unattended, again this would not work I...

maybe here is the solution? how must I implement this in current version NTLite, without setupcomplete.cmd ? Are these commands for the current user or for all users?

By setting <UserLocale>en-BE</UserLocale> the Format "English (Belgium)" and the Location: "Belgium" is what I want and as you can see is also set for future users, that is also desired. However, the Input language: "French (Belgium) - Belgian French" will be set automatically as you explained...

I still end up with all settings correct, except French (Belgium) keyboard installed - but no 2nd keyboard is now present when adding the reg delete. Still I would like not to have the French (Belgium) keyboard but the US (qwerty) one only.

Ok, will try that and let you know.

garlin so in other words, i still appreciate your input as I am nowhere close to a good solution yet :p

It is a struggle to get this working the way I want it, I just want basically 1 language, 1 keyboard and a fixed country, regional format - but it's not working through unattended, as it will simply add the Belgian keyboard if UserLocale is set to en-BE as garlin explained and I can add a...