-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Error: Could not parse languages #2146
Comments
Thanks for the report. It looks like Microsoft have altered the content from their ISO download servers yet again (See #2130 as well as pbatard/Fido#52) and are returning unexpected content. I'll look into this when I get a chance. |
By the way, can you please validate what you get when you attempt to download the ISO by going to https://www.microsoft.com/en-US/software-download/windows11 and trying to obtain an ISO download link? Right now I am getting:
So it could be that the language error has to do with a temporary ban. In short, can you actually download a Windows 11 ISO if you try to do so in the browser from Microsoft's website? |
I am currently downloading Windows 11 English International now, I don't get any errors on the website, it is however very slow and buggy (could be Dark Reader doing that though). |
I am having the same issue, could not parse languages. |
Thanks. I guess the error I get is not related to this issue, as I was playing with Fido earlier and that's probably why I got tempbanned. |
Yes, that is correct. The Microsoft servers serve fragments of HTML for each query (which is also how the page from the website behaves whenever you click a button there) and we process that to try to get the info we need. My current guess is that Microsoft altered their response content for the language in a manner that no longer matches what we expect (though I'm looking at it and not seeing anything obvious right now). |
Ah, I think I get it. Up until now, Microsoft returned: <select id="product-languages">
(...)
</select> but now it seems they dropped the closing
There seems to be additional changes too, so it's not as simple as adding the |
* Addresses pbatard/rufus#2146 * Also update .gitattributes to clean up release archives
Actually what I described above was wrong, we do have the closing At any rate, I believe the latest Fido update, which I just pushed, should fix this. Please try again and let me know if you still see the error. And in case you see it, please check the log to ensure that it downloaded Fido
|
That works for me. |
OK, I'll close this issue then. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
(✓)
button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
See image attached:
Log
The text was updated successfully, but these errors were encountered: