Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fido is stuck #88

Closed
Joeym0180 opened this issue Feb 7, 2024 · 2 comments
Closed

Fido is stuck #88

Joeym0180 opened this issue Feb 7, 2024 · 2 comments

Comments

@Joeym0180
Copy link

Hi,
When running Fido.ps1 the script is getting stuck at the locale query.

PS C:\Scripts> . .\Fido.ps1 -Win 11 -Verbose
No release specified (-Rel). Defaulting to '23H2 v2 (Build 22631.2861 - 2023.12)'.
No edition specified (-Ed). Defaulting to 'Windows 11 Home/Pro/Edu'.
Querying https://vlscppe.microsoft.com/tags?org_id=y6jn8c31&session_id=ff56121f-d0f5-4bb0-bc47-50aa72b2da4c
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=ff56121f-d0f5-4bb0-bc47-50aa72b2da4c&productEditionId=2935&sdVersion=2

when starting with gui options:

PS C:\Scripts> . .\Fido.ps1

and clicking continue on Windows 11 its stuck immediately
image

We have tried different machines with different network connections. also tested it in Rufus 4.4 and is also not working.

it worked fine yesterday.

Hope to have an update soon! :)

@pbatard
Copy link
Owner

pbatard commented Feb 7, 2024

Thanks for reporting. I can replicate the issue. It seems Microsoft have once again changed something on their servers to make it more unfriendly to scripts.

I believe I have found a workaround however, and this is a good opportunity to add timeouts to our web requests, so, hopefully, the version of Fido that closes this request should address the issue.

@pbatard pbatard closed this as completed in 9d46fbf Feb 7, 2024
pbatard added a commit that referenced this issue Feb 7, 2024
* It looks like Microsoft are actively filtering our script by detecting our first request with the
  spoofed user-agent, so work around that.
* Also switch to using 'curl' instead of 'Invoke-WebRequest'. May break PowerShell 7.0, but I'm only
  concerned about Rufus usage for now.
* Also add timeouts on web requests.
* Closes #88.
@pbatard
Copy link
Owner

pbatard commented Feb 7, 2024

Just a note that I have force pushed a new update, because the previous workaround missing some elements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants