What the 😲😕❗❗❓❓
Thanks for your comment. I couldn't explain my issue better. 😂😂😂
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
What the 😲😕❗❗❓❓
Thanks for your comment. I couldn't explain my issue better. 😂😂😂
If you are curious, see here what it is for:
Thanks but like I suspected, it is nothing special plus I don't need it.
Hi.
I got something funnier.
When I click "Time and Language" and then click "Add language", a new window opens and I have very strange wording.
The new window has a Heading titled "Punishment Science" instead of "Choose a language". The O.K. button reads "Mechanic" and the Cancel button reads Highway Transport Technology.
Looks like they screwed up all the Local Experience Packs for the different languages.
Hi IanRG,
All I have to do here to solve the problem is by removing the latest version 22535.1.1.0 and reinstall older version 22534.1.1.0. and then stop the update from the MS Store.
I use the following PowerShell commands; you can probably change these to match the Pack and version for your Zone Language, I don't know which one you use, your snapshot showed Camberra,Melboune,Sydney.
Mine is for en-US and the problem goes away if I reinstall the older version 22534.1.1.0.
Get-AppxPackage Microsoft.LanguageExperiencePacken-US -AllUsers | Remove-AppxPackage
Add-AppxPackage -register "C:\Program Files\WindowsApps\Microsoft.LanguageExperiencePacken-US_22534.1.1.0_neutral__8wekyb3d8bbwe\appxmanifest.xml" -DisableDevelopmentMode
I appreciate the work around, but the silly mistake by Microsoft does not make the computer unusable. It is up to Microsoft to fix the problem.