{"id":114,"date":"2020-02-02T15:00:00","date_gmt":"2020-02-02T14:00:00","guid":{"rendered":"https:\/\/blog.vermeerschconsulting.be\/?p=114"},"modified":"2021-01-30T11:02:12","modified_gmt":"2021-01-30T10:02:12","slug":"prevent-windows-10-automated-language-pack-removal","status":"publish","type":"post","link":"https:\/\/blog.vermeerschconsulting.be\/index.php\/2020\/02\/02\/prevent-windows-10-automated-language-pack-removal\/","title":{"rendered":"Prevent Windows 10 automated unused Language Pack removal"},"content":{"rendered":"\n

In Belgium we speak different languages, so our Windows 10 devices are deployed with the native English “en-US” ISO. Together with extra installed Language Packs (LPs), users can change the User Interface language whenever they want. This was working for the last couple of years. (I remember doing this since Windows XP)<\/p>\n\n\n\n

In Windows 10 1803 this was still working like expected for our users but since we are recently rolling out Windows 10 1909 we experience a strange thing. Right after the deployment of the machine, users could still modify their UI language, but if the machine is in transit for a couple of days, users can’t change the UI language anymore without downloading it. So what is going on?<\/p>\n\n\n\n\n\n\n\n

When I started investigating I discovered that just after OSD all LPs are available to the user.<\/p>\n\n\n\n

\"LPs
On a fresh installed machine you see the 3 extra LPs<\/figcaption><\/figure>\n\n\n\n

After a couple of days the language packs are removed and when the user wants to add a language, it is downloaded, so this is not like expected. <\/p>\n\n\n\n

\"Remaining
After a couple of days the same command shows <\/figcaption><\/figure>\n\n\n\n

In File Explorer you see the same result<\/p>\n\n\n\n

\"Installed
On a fresh installed machine<\/em><\/figcaption><\/figure>\n\n\n\n
\"Remaining
After a couple of days the LP folders are removed<\/em> <\/figcaption><\/figure>\n\n\n\n

This must be a different behavior between Windows 10 1803 and 1909. After spending some time together with Google I found the following article that perfectly describes our issue https:\/\/docs.microsoft.com\/en-us\/windows-hardware\/manufacture\/desktop\/language-packs-known-issue<\/a><\/p>\n\n\n\n

So enabling the following GPO setting resolved the auto delete of the unused language packs.<\/p>\n\n\n\n

\"GPO
Computer Configuration\\Policies\\Administrative Templates\\Control Panel\\Regional and Language Options<\/figcaption><\/figure>\n\n\n\n

We experience the same behavior after an in place upgrade of Windows 10 1803 to 1909. We also added the 3 new LPs during the in place upgrade Task Sequence since every Windows 10 version comes with its own LP files (except 1903 and 1909 share the same 1903 LP files)<\/p>\n","protected":false},"excerpt":{"rendered":"

In Belgium we speak different languages, so our Windows 10 devices are deployed with the native English “en-US” ISO. Together with extra installed Language Packs (LPs), users can change the User Interface language whenever they want. This was working for the last couple of years. (I remember doing this since Windows XP) In Windows 10 … Continue reading “Prevent Windows 10 automated unused Language Pack removal”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[22,20],"tags":[28,29,30,25,26,31,27],"class_list":["post-114","post","type-post","status-publish","format-standard","hentry","category-configmgr-memcm","category-windows-10","tag-28","tag-29","tag-30","tag-confmgr","tag-language-pack-lp","tag-mem","tag-windows-10"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts\/114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/comments?post=114"}],"version-history":[{"count":0,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/posts\/114\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/media?parent=114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/categories?post=114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.vermeerschconsulting.be\/index.php\/wp-json\/wp\/v2\/tags?post=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}