Skip to content

24 Comments

  1. haty
    September 13, 2021 @ 8:02 am

    Thanks. Second method works for me.

    Reply

  2. David
    September 21, 2021 @ 8:44 pm

    Thanks you!!

    Reply

  3. Milk
    October 6, 2021 @ 3:26 pm

    The second method works fine.

    Reply

  4. Stanko
    February 9, 2022 @ 4:18 pm

    The first method didn't resolve the problem, but the second one worked fine!

    Reply

  5. Mahdy
    February 20, 2022 @ 4:53 pm

    The second method worked for me,
    thank you

    Reply

  6. Martina
    February 24, 2022 @ 6:55 pm

    Thank you so much, option 2 worked wonders!

    Reply

  7. Albert
    March 1, 2022 @ 8:38 am

    Thanks!!!! The method 2 work fine for me!

    Reply

  8. Roland
    March 22, 2022 @ 12:28 pm

    Option 1 worked. Thanks!

    Reply

  9. yariv inbar
    April 4, 2022 @ 4:50 pm

    Thanks!!! Works perfectly

    Reply

  10. Ferdinand
    May 23, 2022 @ 11:34 am

    BIT THANKS I LOVE YOU whoever you are

    Reply

  11. Sandy
    May 29, 2022 @ 1:27 am

    Thank you – option 2 also worked for me

    Reply

  12. Mohammad Refaie
    May 29, 2022 @ 1:30 pm

    for the second method, in power shell you may need to import a module before running the mentioned command:
    Import-Module -Name International -UseWindowsPowerShell -Verbose
    Get-WinUserLanguageList

    Reply

  13. Sorin
    July 13, 2022 @ 5:49 pm

    First method was enough to solve the issue. Thank you!

    Reply

  14. Andrey
    July 22, 2022 @ 5:33 pm

    Thank you very much, the 2nd way was successfull!

    Reply

  15. Woot
    August 7, 2022 @ 11:08 pm

    Thank you thankyou thankyou
    I really can't understand what they (microsoft) are thinking with this kind of settings

    Reply

  16. Anton
    August 24, 2022 @ 3:21 pm

    Thank you so much! The second method really helped! After several months of the existence of this problem…

    Reply

  17. Jacob
    September 2, 2022 @ 10:41 am

    Awesome! Thanks! Second works for me!

    Reply

  18. Nikos
    November 18, 2022 @ 8:38 am

    The powershell worked! Nice. Thx

    Reply

  19. E
    December 15, 2022 @ 9:12 am

    The second option worked! It was so frustrating shifting through three languages before! Thank you!

    Reply

  20. Samara Morgan
    July 16, 2023 @ 9:55 pm

    Second method works! Thanks

    Reply

  21. markos
    September 12, 2023 @ 3:07 pm

    THANK YOU , you save me ! i was trying for months to fix it

    Reply

  22. Otto Herman
    September 21, 2023 @ 10:21 pm

    Thank you. I think I got this since the new win 11 install. I never had this on Windows 10.
    This was very annoying when I needed to switch between my two languages.
    I would always miss the one I needed.
    This definitely helped.

    Reply

  23. Ofir
    November 25, 2023 @ 9:04 pm

    Thanks.
    Second method fixed it.

    Reply

  24. Stacey
    December 5, 2023 @ 5:45 pm

    Thank you very much! Ran into this issue today, in December 2023. I got two QAA and one QAB locales. After trying method 1 I was able to get rid of one QAA, the other one and QAB still remained even when I repeated the step. But force resetting default language in powershell solved the issue and no weird locales appeared after selecting additional languages.

    Reply

Leave a Reply

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