Open-source project
pbatard/Fido avatar
pbatard/Fido

pbatard/Fido: a single PowerShell script that fetches Microsoft retail ISO links, within the limits Microsoft now sets

A PowerShell script to download Windows or UEFI Shell ISOs

2,932 stars255 forksPowerShellGPL-3.0

At a glance

What is it?
Fido is the PowerShell script behind Rufus's Windows ISO download option, and it also runs on its own with a GUI or six command line switches. It gets you official retail images whose hashes can be checked, but since 2023.05 it can only reach the newest release of each Windows version, and it skips LTSB/LTSC and Windows 7 hosts.
Who is it for?
Use Fido if you want an official Microsoft retail ISO for the current release of Windows 8 through 11 and prefer a script or command line to clicking through Microsoft's download page, or if you already use Rufus and want to know what its download button is doing. Do not pick it for older Windows releases, LTSB/LTSC editions, or a Windows 7 machine, since none of those are served.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 12 days ago.
What is it written in?
Mainly PowerShell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pbatard/Fido2,932 ★ · +26
Star history
Repository2026-10-042026-11-15
pbatard/Fido2.9k2.9k

26 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Retail ISOs instead of Media Creation Tool output, for the sake of a checkable hash

Fido exists to make one kind of file easy to get: the Microsoft retail ISO. The author's argument is about verification, not convenience. Each retail ISO has a single master, so it has a single official SHA-1, which you can obtain from MSDN if you have access or from third party hash lists. If your download matches that hash, it matches bit for bit what Microsoft released.

The Media Creation Tool works differently. MCT regenerates the ISO content on the fly, so no two MCT images are the same, and there is no reference hash to compare against. Pbatard's point is that this makes it impossible to tell with certainty whether an MCT image was corrupted after it was generated. For anyone who validates install media before trusting it, that is the reason to prefer what Fido fetches. The script itself does not compute or compare the hash for you; that check remains your job once the download finishes.

It replays the software-download page that Microsoft hides from Windows browsers

Fido does what a person would do on https://www.microsoft.com/en-us/software-download, minus the friction. On that page, for Windows 10, Microsoft's servers detect when the browser is running the same version of Windows you are trying to download and may redirect you away from the direct ISO link, which is why a manual download from Windows often requires changing the browser's User-Agent string.

The script's sequence is short. It first checks basic access to the Microsoft software downloads site. It then queries Microsoft's web API for the languages available for the selected Windows version, and finally requests the actual download links for every architecture available for that language and version. Because the whole flow depends on Microsoft's endpoints, a change on Microsoft's side can break or narrow what Fido returns, which is exactly what happened in 2023, and new Fido versions are how those changes get absorbed.

Six switches that skip the GUI

Run with no options, Fido opens a GUI. Pass any of its switches and it stays in the PowerShell console instead, which makes it usable from scripts.

-Win picks the Windows version, accepting abbreviations such as -Win 10 if unique; -Win List prints the supported versions. -Rel picks the release, such as 21H1, with -Rel Latest forcing the newest and -Rel List listing the choices. -Ed picks the edition, for example -Ed Pro, with -Ed List. -Lang picks the language and accepts a fragment, so -Lang Int matches English International; -Lang List shows the options. -Arch picks the architecture, such as x64. -GetUrl stops the script from launching the download and prints the URL instead, so you can pipe it into another command or a file.

The example session from the project shows the defaults being filled in when only the version is given:

code
PS C:\Projects\Fido> .\Fido.ps1 -Win 10
No release specified (-Rel). Defaulting to '21H1 (Build 19043.985 - 2021.05)'.
No edition specified (-Ed). Defaulting to 'Windows 10 Home/Pro'.
No language specified (-Lang). Defaulting to 'English International'.
No architecture specified (-Arch). Defaulting to 'x64'.
Selected: Windows 10 21H1 (Build 19043.985 - 2021.05), Home/Pro, English International, x64
Downloading 'Win10_21H1_EnglishInternational_x64.iso' (5.0 GB)...

That transcript predates the 2023 change described below, so the 21H1 release it names is not what you will get today.

Language and architecture default to whatever machine runs the script

Two of the defaults are inherited from the host rather than chosen by the project. Without -Lang, Fido tries to select the same language as the system locale. Without -Arch, it tries to use the architecture of the current system. Without -Win, it picks the most recent Windows version, and without -Rel, the most recent release of that version.

This is convenient when you are rebuilding the same machine you are sitting at, and a trap when you are not. Preparing an ARM64 or non English image from an x64 English workstation means the defaults are wrong for your target, and the console messages that announce each default are easy to scroll past in a script. If Fido is part of an automated build, pin every value explicitly, and use the List forms of -Win, -Rel, -Ed and -Lang to check what strings Microsoft currently exposes before hard coding them.

Since 2023.05 only the newest release of each version is reachable

As of 2023.05, Microsoft removed access to older Windows ISO releases, and Fido's selectable list had to shrink to the latest release for each version. The -Rel switch still exists, and -Rel List still works, but the list it returns no longer reaches back through the feature updates the script once offered.

The consequence is practical. If you need a specific older build to reproduce a bug, match a corporate baseline, or reinstall a known good release, Fido cannot fetch it, because the links are gone at the source rather than missing from the script. The scope of supported Windows versions in the project's own description runs from Windows 8 through Windows 11, and within each of those you get the current release only. Plan to archive the ISOs you depend on yourself, along with their hashes, rather than expecting to fetch them again later.

No LTSB/LTSC images and no Windows 7 host

Fido is deliberately narrow. Because it was built for Rufus, it covers the retail downloads the general public asks for, not every retail ISO Microsoft publishes. Pbatard states there is no plan to add LTSB/LTSC Windows ISO downloads, and points people who need them to Microsoft's own evaluation center pages instead. If your use case is long term servicing builds for kiosks or industrial machines, Fido is the wrong tool and you will be working through Microsoft's site manually.

The host requirement is just as firm: Windows 8 or later with PowerShell. Windows 7 is not supported. That rules out using an old Windows 7 machine as the download box for a fresh install, which is a common situation when someone is upgrading the very machine that needs the ISO. Use a newer Windows system, or Rufus on one, to run the script.

One Fido.ps1 file, versioned with Rufus and licensed GPL-3.0 or later

The repository is small: Fido.ps1 is the whole program, next to LICENSE.txt, README.md, a sign.sh file and editor and git configuration. There is no module to install from a gallery; you obtain the script from the project's GitHub releases page or the repository and run it in PowerShell, or you get it indirectly through Rufus, which is its primary consumer.

Releases arrive steadily. Fido 1.69 was published on 2026-02-27, Fido 1.70 on 2026-03-30 and Fido 1.71 on 2026-09-30, the same day as the last push to the master branch. Since Fido depends on Microsoft's download API, staying on a current release matters more than it would for a self contained tool: an old copy can fail when Microsoft changes its endpoints. The license is the GNU General Public License version 3.0 or later, so redistributing a modified Fido.ps1 inside another tool carries GPL obligations. Beyond Windows, the same script also gives access to bootable UEFI Shell images from pbatard's UEFI-Shell project.

Editorial conclusion

Use Fido if you want an official Microsoft retail ISO for the current release of Windows 8 through 11 and prefer a script or command line to clicking through Microsoft's download page, or if you already use Rufus and want to know what its download button is doing. Do not pick it for older Windows releases, LTSB/LTSC editions, or a Windows 7 machine, since none of those are served. Before relying on an image, check its SHA-1 against an official source and pass -Lang and -Arch explicitly rather than trusting the host machine's defaults.

Frequently asked questions

Is there a Fido app for Windows?

Fido is not a packaged app but a PowerShell script, Fido.ps1, that runs on Windows 8 or later and opens a GUI when started without options. It is also built into Rufus, which uses it to download Windows ISOs.

Can pbatard Fido download older Windows 10 releases such as 21H1?

No. Since 2023.05 Microsoft removed access to older Windows ISO releases, so Fido can only offer the latest release for each Windows version.

How do I get only the download link from Fido without starting the download?

Add the -GetUrl switch. Fido then prints the download URL instead of launching the download, so it can be piped into another command or a file.

Does Fido support Windows LTSC ISOs?

No. The Fido project has no plan to add LTSB/LTSC downloads and directs users to Microsoft's evaluation center pages for those images.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. pbatard/Fido on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pbatard-fido.svg)](https://hysenlabs.com/projects/pbatard-fido)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pbatard-fido.svg)](https://hysenlabs.com/projects/pbatard-fido)

Was this useful?