Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше
Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.
Архівовано

Group Policy - intl.accept_languages

NathanH

I previously posted this question: https://support.mozilla.org/en-US/questions/1495577

Asking how to use the "intl.accept_languages" setting within the JSON for the new preferences setting within group policy.

A moderator posted this as a comment which I have only just noticed: "The value is a string, so it has to be in quotes "en-GB"" - the post is now too old for me to reply.

I'm still having issues using this setting even after putting the name in quotes. I've tried:

"intl.accept_languages": { "Value": "en-GB", "Status": "user" }

"intl.accept.languages": { "Value": "en-GB", "Status": "user" }

But neither work, please can someone clarify what exactly needs to be used within the JSON?

I previously posted this question: https://support.mozilla.org/en-US/questions/1495577 Asking how to use the "intl.accept_languages" setting within the JSON for the new preferences setting within group policy. A moderator posted this as a comment which I have only just noticed: "The value is a string, so it has to be in quotes "en-GB"" - the post is now too old for me to reply. I'm still having issues using this setting even after putting the name in quotes. I've tried: "intl.accept_languages": { "Value": "en-GB", "Status": "user" } "intl.accept.languages": { "Value": "en-GB", "Status": "user" } But neither work, please can someone clarify what exactly needs to be used within the JSON?

Усі відповіді (2)

This question is now showing as "Last reply by Abidah Sultan" but I'm not seeing any responses to this?

His response was spam. We're working on an answer.