search

pbatard / Fido

A PowerShell script to download Windows or UEFI Shell ISOs
GNU General Public License v3.0
2.35k stars 225 forks source link

Error: Could not parse languages #66

Closed MaxstarPCW closed 1 year ago

MaxstarPCW commented 1 year ago

Hi,

I receive this error when using this script. Also on different machines, one with en_US as default language and another one with nl-NL as default language.

PS C:\WINDOWS\system32> cd $home PS C:\Users\Gebruiker> sl desktop PS C:\Users\Gebruiker\desktop> PowerShell.exe -ExecutionPolicy Bypass -File .\fido.ps1 Please Wait... Querying https://www.microsoft.com/en-US/software-download/ Querying https://www.microsoft.com/en-US/api/controls/contentinclude/html?pageId=a8f8f489-4c7f-463a-9ca6-5cff94d8d041&host=www.microsoft.com&segments=software-download,windows11&query=&action=getskuinformationbyproductedition&sessionId=e74363f0-b9db-4ca3-837c-887b0aa954ac&productEditionId=2370&sdVersion=2 Error: Could not parse languages

Screenshot: https://i.postimg.cc/sDs5GR14/fido-error.png

farag2 commented 1 year ago

Hi @MaxstarPCW. There's no need at all to call powershell.exe from powershell.exe :cat:. Just run script & "path_to_fido.ps1". To change execution policy pemanently run

Set-ExecutionPolicy -ExecutionPolicy Bypass -Force

to do it temporarily

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force
pbatard commented 1 year ago

I'm afraid I can't replicate this issue.

Also, you don't appear to be running the latest Fido script because there should be a line Querying https://vlscppe.microsoft.com/tags?org_id=y6jn8c31&session_id=<GUID> that is missing from your output, which is most likely your issue.

Please make sure you ALWAYS run the latest version of the script. Earlier versions are not supported.

Maki079 commented 6 months ago

Hi! i encountered the same issue today. It seems it appears while executing script form Windows Server 2022 machines. I tested on Windows 10 client and all worked fine for me.

Regardless just letting you know how to replicate this issue.

ave9858 commented 6 months ago

image Works fine for me, idk how running on server vs client could even change the response returned by the server anyway. Do the 2022 machines have the same IP as your Windows 10 client?

pbatard commented 6 months ago

Regardless just letting you know how to replicate this issue.

Yeah, I'm not gonna go through a server install just to test this issue especially when other folks who tested on Server don't see it.

The reason why the whole script is Open Source is so that people who experience some issue can debug it and then try to propose a patch.