PowerShell GUI for Downloading Language Packs - W10_11LangPack.ps1

use this command in powershell ,after you started it in admin mode: powershell -NoProfile -ExecutionPolicy Bypass -File "path\to\your\script\.ps1"
 
There's a .bat file included (in case you have a default or restrictive Execution Policy), which calls the PS script with -nop -ep bypass.
 
Hello.
The script is great, thank you.
But where were the files downloaded? :p
I can't locate them.
It would be nice if the script indicated this.
 
The files are downloaded to the current folder where you started the script.
Are you using a desktop shortcut? If you have a shortcut, change the property for "Start in" folder.
 
The folder containing your scripts is located in an smb share. I still saw a window where there was "Writing...". But it's true that no file was written in the folder apart from the bin folder which was then deleted. Maybe the script doesn't manage UNC paths? I'll try again locally.
 
I just ran the script locally, and after selecting the language files, the window closed.
Okay, I just found the files downloaded by the script. I just compared the installation with a recent backup, and the script placed the files:
Microsoft-Windows-Client-LanguagePack-Package_en-us-amd64-en-us.esd
Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64.cab
Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64.cab
Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64.cab
Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64.cab
Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64.cab
in C:\Windows\System32. So, I'm guessing that when I restart it, it detects these files already present in C:\Windows\System32 and closes.
I'll move these files elsewhere and see what happens.
 
I created an optional command-line parameter -Folder, with some sanity checking on the path and whether it's really a directory or not. Because I've added the option here I'll have to retrofit some of my other scripts to match likewise.

W10_11LangPack.ps1 -Folder ..\path\somewhere
 

Attachments

After several tests, I determined that the W10_11LP.bat script runs fine locally and on an SMB share, but on an SMB share, it returns an error when it tries to convert the .esd.
I think you need to make it more verbose so that it reports any errors it encounters.
 
UPDATE: Fixed a problem with ESD2CAB not finding any ESD file(s) to extract, because you're running W10_11LangPack.ps1 from a different path than the one you're currently working in.

abbodi's esd2cab_CLI.cmd has a limitation where it only recognizes .esd files in the same folder as itself. Instead of extracting the ESD2CAB files into $PSScriptRoot, I switched to the current working path ($PWD).
 
You must log in or register to reply here.
Back
Top