It has proofing but Z_proof2016_kb3141509_x64_proof-x-none.msp contains all the languages and the iso contains the base for the needed companion languages, so prolly Z_proof2016_kb3141509_x64_proof-x-none.msp updates all needed companion langs
That is nice to know, I will remember that, thanks. Btw, I have updated the code. Now the variables langOfMSP and ProofLang can be left empty (they will still ask you, if they are not set). Hope that solved this issue .
It confirmed my findings about the language settings not needed for office 2016 updates Enne, bedankt
@Enthousiast the script is mainly useful for Office 2010, due the nature of separate lang patches Office 2013 RTM had same situation, but SP1 patches ended that and it follows the model of aio neutral patch (except proofing and lync help) Office 2016 proofing only became neutral this year, it was multiple patches before thanks @hearywarlot you should have my avatar
Update: Made some minor changes and fixes to the script. You can now pass options in any order without being prompted to enter the data. Because of Office 2016 being language neutral, "langOfMSP" and "Prooflang" are now optional. Included credit and link to this thread at the end of the script. Will list which EXE files failed to extract folders. Hope that fixes all the bugs and mistakes I left behind. I also updated the Usage in the first post to reflect the changes. Nah, I am quite fond of my current avatar . It looks so cozy and full of terror, just as I like it.
Update: I did an accident : At the MSP lang check, I accidentally did not add '!' around "nameOfMSP", making lang checks fail... I fixed this now. Made the script now only accept EXE files with a Office update naming convention such as "*-*-*-*-*.exe". I hope this fixes the rest of my mistakes (With the exception of caring for most of humanity)... If you see any other mistakes, don't hesitate to post it . Also forgive me if I wasted your time because of this mistake (ah don't hit me there)... Luckily though you can make a small script and do batch jobs by calling this script using options multiple times, so that should make it up?
Fixed some mistakes and added new features: Script will now move out old MSP files to folder of choice as it copies your newer in. Now has a additional parameter for configuring where old MSP files go to. Will skip moving file if already exists at destination. If a Office KB file does not contain any MSP files corresponding with your choice, the script will tell you (eg, imeloc2010). Command Prompt window will resize and increase buffer a good bit to fit the onslaught of text, so you can read easier. Replaced URL in script with URL to this thread, forgot it still linked to abbodi1406's post. A question, is it maybe better to make moving old MSP's optional, and why? As to having multiple versions, I do not see a point, but maybe I am missing some knowledge about that. Thanks in advance.
Hello Dr.Emuler, I did not write this script with donations in mind. Me writing it was more of a way of learning to script better and create my own style and trying to contribute so everybody seeking this solution has the ultimate tool. I don't mind your donation/gift, but do know it won't speed up development on this script, since it's pretty much already finished (some polishing can be applied anytime though). Though, I have never gotten a donation or accepted money from someone unknown over the internet, so I can not say.