Tags: pbatard/Fido
Tags
Fix localization of error message 715-123130 * As usual, Microsoft are completely unable to properly process UTF-8 content, even if the response from an Invoke-WebRequest query explicitly specifies "charset=utf-8". * So, once again, we need to force PowerShell's hand to treat the content as UTF-8. * Also improve the default error message if we can't get it from Microsoft.
Switch to using the new JSON Windows download API * This simplifies things quite a bit since we were converting HTML to XML to JSON before. * Also drop the custom User Agent for now. We'll have to see how long it takes Microsoft to go back to filtering out PowerShell... * Closes #98.
Add ARM64 Windows 11 downloads * Gotta really praise Microsoft for having designed their download servers to handle multiple archs for the same Windows SKUs... and then completely throw that out of the window to instead make Windows 11 ARM64 a different SKU. * Now, because we don't want to be *AS MORONIC AS MICROSOFT*, we go the extra mile (and issue multiple requests, using multiple session IDs) to make the ARM64 *ARCHITECTURE* fall into the fold of where it belongs, i.e. as a user selectable property of a single Windows 11 release. * Closes #97.
Work around the latest Microsoft server restrictions * 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.
PreviousNext