FreeMCBoot 1.966: What’s New vs 1.965 and 1.953
FreeMCBoot 1.966, released on 13 April 2019, is the latest stable version of FreeMCBoot (FMCB). If you are installing FMCB for the first time, 1.966 is the version to use. If you already have an older version running well, 1.966 is a small maintenance update rather than a reason to rebuild a working card from scratch.
The 1.966 changes are narrower than that: a shutdown option, a renamed menu item, updated storage modules, a clearer recovery path, and a recompiled disk-checking tool. None changes which consoles FMCB supports, and none adds applications to the package.
What changed in 1.966
The author’s changelog for 1.966 lists five items. They are worth reading literally, because each one answers a different practical question.
| Change in 1.966 | What it means in practice |
|---|---|
| POWEROFF shutdown function added | A shutdown option is available from within FMCB, rather than only using the console power button. |
| Reload Configuration renamed to Restart System | The menu item now says what it does. It restarts the system instead of sounding like a settings reload. |
| USBHDFSD and HDD modules updated | The storage modules were updated with the aim of reducing wear on 2.5-inch hard drives. |
| Recovery mode via mass:/RESCUE.ELF | If your configuration is broken, FMCB can boot a rescue file from USB. Pressing START+R1 forces recovery mode. |
| FSCK recompiled with the new HDD modules | The disk-checking tool was rebuilt to match the updated HDD modules, so the two stay consistent. |
The recovery change is the most useful of the five for everyday users, and it is also the easiest to misunderstand. Recovery mode does not repair a card by itself. It gives you a way back in: FMCB boots the file at mass:/RESCUE.ELF from a USB drive, so you can fix a bad configuration instead of being locked out of your own setup. The START+R1 combination forces that path, which matters when the normal boot configuration is the thing that is broken. If you ever change FMCB settings and the console no longer reaches a usable menu, this is the escape route to remember before you reformat anything.
The storage module update is about Fat PS2 hard drive setups, where FMCB runs from the drive through the Free Hard Drive Boot (FHDB) route. The 1.966 notes describe the update as reducing wear on 2.5-inch drives. That is a design goal, not a promise about any particular drive, so back up your own saves and your own dumps and keep a second copy of anything you cannot afford to lose.
The renamed menu item also prevents a real mistake. “Reload Configuration” could be read as reloading a settings file, while “Restart System” plainly means the console restarts.
How 1.966 compares with 1.965 and 1.953
| Version | Release date | Position |
|---|---|---|
| 1.953 | 16 December 2016 | Older 1.9-series release |
| 1.965 | 8 December 2018 | Previous release before 1.966 |
| 1.966 | 13 April 2019 | Latest stable release |
The honest limit of this comparison is that the detailed intermediate changelogs for 1.953 and 1.965 are not reproduced here, because this guide only reports changelog entries that have been checked against the author’s notes. What can be said with confidence is the timeline and the endpoint: 1.966 is the latest stable release, 1.965 came immediately before it, and 1.953 is an older release from 2016 that still appears in guides and on pre-made cards because it circulated for years.
That timeline explains a common confusion. A card or tutorial mentioning 1.953 is usually just old, not current, and 1.965 was current for only a few months before 1.966 replaced it. For a fresh install, start with 1.966, and only consider an older version as a troubleshooting step for a specific, documented problem.
Also separate the installer version from the FMCB version. The FMCB Installer source code named alongside 1.966 is version 0.987. The installer writes FMCB to a card; FMCB itself is the software that boots from the card afterwards.
Should you update an existing card to 1.966?
Use this decision checklist:
- Fresh install: Use 1.966. Get it from the Download page and follow a current install guide.
- Working card on 1.965 or 1.953, no problems: Leave it alone. An update is not required to keep playing, and every reinstall is a chance to make a mistake with a working setup.
- You use a Fat PS2 hard drive setup: 1.966 is the more sensible choice, because of the updated HDD modules and the recompiled FSCK tool.
- You have broken your FMCB configuration: The mass:/RESCUE.ELF recovery path in 1.966 is a reason to prefer it when you rebuild.
- You are troubleshooting a specific problem: Change one thing at a time. Updating FMCB, updating your loader, and changing storage at the same time makes it impossible to tell which change fixed or caused the problem.
Updating FMCB is not the same as updating Open PS2 Loader (OPL). FMCB is the bootloader on the memory card; OPL is a separate application that loads games. Updating one does not update the other. See Open PS2 Loader Versions and exFAT Support Explained.
What 1.966 does not change
Version updates invite overclaiming, so here are the boundaries that stay the same in 1.966:
- Compatibility is unchanged. FMCB supports PlayStation 2 consoles except late SCPH-90000 models from the third quarter of 2008 onward (datecode 8C and later, boot ROM 2.30 and newer) and the PS2 TV. Always check the ROM version, because datecode 8C was a transition period and cannot be judged by datecode alone. Late Slims need a different route; see FunTuna, Fortuna, and OpenTuna Versions for Late PS2 Slims.
- No applications are included. The author’s release package contains only the files FMCB itself needs. Open PS2 Loader, uLaunchELF, and ESR are separate applications, or parts of community bundles such as the Noobie package. They do not ship inside the 1.966 package, and a guide that says otherwise is describing a bundle, not the author’s release. See FreeMCBoot Installer Versions and the Noobie Package Explained.
- FMCB alone does not add import or copied-disc support. That is a hardware limitation described in the author’s FAQ, not something a version number removes. FMCB boots homebrew from a memory card; it does not turn the console into a region-free or copy-playing machine by itself.
- exFAT is not a 1.966 feature. exFAT support belongs to modern Open PS2 Loader builds, not to the FMCB core. If a page credits 1.966 with exFAT support, it has mixed up the bootloader and the loader.
FAQ
Is 1.966 still the latest FreeMCBoot version? Yes. 1.966, released on 13 April 2019, remains the latest stable FMCB release in the author’s notes. Check any claim of a newer numbered release against the author’s release history before trusting it.
Do I need 1.966 to use Open PS2 Loader? No. FMCB and OPL are separate. You need a working FMCB install to boot homebrew, and OPL itself, updated separately, to load games.
What is the difference between FMCB 1.966 and installer 0.987? FMCB 1.966 is the boot software. Installer 0.987 is the version of the installer source code named alongside that release. One is what runs from your card every boot; the other is the tool used once to write it there.
I have 1.953 on a card that works. Should I worry? No, not on version grounds alone. 1.953 is older, but a working card is a working card. Update when you have a reason — a fresh install, a hard drive setup, or a broken configuration — not because a number looks old.
What should I do before updating FMCB? Back up your saves and configuration, note where your applications live, and follow one guide end to end. Do not combine an FMCB update with a loader update and a storage change in one session.