/build/static/layout/Breadcrumb_cap_w.png

Looking for information on Language Packs as updates

I noticed an large amount of updates pushed from KACE on our Windows 10 computers is language packs.  Typically over 30 patches per computer, and they require a reboot. In an effort to learn more, I followed the MS link in the Patch Detail.  It takes me to
https://support.microsoft.com/en-us/kb/3109599 which is a dead end with an error from MS, but appears to be the same as KB3109596

For someone that only needs Windows in one language, do they need these 33 patches?
Should I have a label that excludes these?
This looks a lot more like an optional feature than a patch. Are there more updates in this category that I can and should be excluding from automatic installing?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 8 years ago
Red Belt
0
Windows 10 patches seem to be taking a little while for us all to get used to. Whether it is that they are being released with a different naming convention or different functionality i.e. OS upgrades, I am not too sure. 

With regards to the language pack updates, if your Windows 10 users are already operating in a language that is working OK, then I would suggest that you filter those updates out into a specific Patch label. 

Do not deploy that Patch Label to all machines, this will prevent you pushing it out unhindered, but it also means that you have them segregated on one side should an end user come up against an issue that requires a language pack update to resolve

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ