Forum Discussion
Edge Chromium changes the operating system language
Thanks for your answer
I mean the OS UI-Language. What also surprises me
Edge Chromium is installed as a replacement. Not side-by-side.
The installation package was created with the new SCCM feature "Microsoft Edge Management":
powershell -File ".\Install-Edge.ps1" -MSIName "MicrosoftEdgeEnterpriseX64.msi" -ChannelID "{56eb18f8-b008-4cbd-b6d2-8c97fe7e9062}"
The Powershell script that Microsoft created and used for installation is attached.
We are still in the test phase, so the package will be installed immediately after the installation (via Software Center). So not yet installed in the task sequence.
To create the Screenshots here, I installed a VM (Hyper-V) today. Here the error did not occur!
Then I took a laptop again (HP EliteBook 850 G4). Here the error occurs (therefore reproducible)
Bevor Edge Chromium installed (without starting the old Edge Browser):
After installation and reboot:
berwan Sounds very strange to me, that this behavior is Hardware-dependent.
As I can see your PowerShell-Script is just a straight-forward MSI-Installation, nothing suspicious there. To debug this, I would add an argument /L*v C:\Temp\MSEdge-MSI-Install.log to the Script.
OR: maybe you already have an Installation Log, because the "inner" Setup-Package usually creates a log in C:\Windows\Temp\msedge_installer.log => maybe you can find something helpful there.
- michliFeb 13, 2020Former Employee
berwan are you still facing this issue? If yes, can you try rebooting without installing Edge on Chromium to see if the UI language still changes in that case?
If the issue does not occur when not installing Edge, and does occur after installing Edge, then we will investigate further. A screenshot of the Windows version info from running "winver" in the Start Menu will help us diagnose.
Thank you!
- berwanFeb 13, 2020Copper Contributormichli I was sick the last few days and unfortunately I did not have the chance to continue testing. As soon as I get back to testing and I have new findings, I will let you know.
- berwanFeb 14, 2020Copper Contributor
I found the bug and it's not Edge Chromium (an outdated configuration baseline
).
I'm sorry about the false alarmand thank you for your support
The thread can be closed.
regards