FlyOOBE 3.0 ships a leaner, more transparent route through Windows setup
The open-source setup assistant from developer builtbybel drops the bloat-busting ambition and doubles down on getting you past Windows' first-boot experience faster and with more control.
FlyOOBE 3.0 is out, and it's trying hard to be something different than its predecessor. The free, open-source tool shipped September 18, 2026 with a smaller footprint and a "comeback release" ethos. It wants to get you through Windows setup without trying to rebuild the OS from scratch.
The origin story helps explain where the tool came from. FlyOOBE grew out of Flyby11, a small utility that let people install Windows 11 24H2 on hardware Microsoft never officially blessed. No TPM. No Secure Boot. A CPU that's technically too old. It helped upgrade plenty of otherwise-fine machines that were headed for the recycling bin.
Then the developer expanded it into a full first-boot assistant. The repo says it plainly: bypassing checks is only half the battle. The 3.0 release leans into skipping Microsoft's defaults, stripping preinstalled junk, and handing control back to you.
Keep in mind that this is a comeback in more than just name. The old page-heavy assistant has been swapped for a native, signature-driven checklist. It no longer rates every setting as "good" or "bad," and instead shows what's actually configured, how it stacks up against its own recommendations, and lets you change only what you care about.
"Personal choices are not judged, red does not mean broken, and nothing happens without confirmation," the developer writes. Notable shift in tone, and a decent nod to a broader trend toward tools that treat users as adults.
What's new (and what's actually useful)
The biggest visible change is a unified overview. One screen now surfaces settings, apps, personalization, bloatware and system tasks, replacing what used to be a multi-window circus. Recommendations sit apart from your personal choices, so you always know what the tool suggested versus what you set yourself.
Configuration now lives in editable files. Windows settings are driven by Flyoobe.ini, app installation uses Apps.ini, and bloatware detection comes from Bloatware.ini. Everything stays outside the executable wherever it can, which makes the whole thing far more transparent than a black-box optimizer that quietly rewrites your registry behind your back.
You can also save, import, review and apply complete setup recipes on another machine. A new review mode shows you a summary before anything gets applied, and imported recipes stage their choices first so you can eyeball them before committing.
Every supported setting now gets its own Apply and Restore default buttons, too. That's granular control in place of one-click sweeps, which honestly feels like the right call for a tool that touches enough system settings to make a mess.
The winget-powered app installer, bloatware auto-detection and browser setup round out the feature list. Theme changes hit Windows immediately without an Explorer restart, and quick workflows get you straight to account, network and Windows Update tasks.
There's even optional AI assistance, with a guardrail worth respecting: AI can explain a setting, but it cannot apply one. That's a sensible boundary, since letting a chat bot silently reconfigure your machine is a fast track to waking up with a broken system.
What changed, and why you might care
FlyOOBE 3.0 makes several deliberate philosophy shifts worth paying attention to. It no longer tries to become another giant Windows optimizer. When Windows already handles something well, the tool now just opens the matching native workflow instead of reimplementing it. Simpler. Less code to break.
The Windows 11 upgrader remains completely isolated in Flyby11 form, so you can remove it later without touching the rest of the app. Unchecked recipe entries now restore their defaults instead of being silently ignored, which closes a gap that likely bit a few users along the way.
Under the hood, the whole thing got rebuilt on native WinForms. That means views stay inside the main window instead of popping open in a dozen separate panes, plus better scaling for high-DPI displays and longer translated strings. Not the flashiest upgrade in the world, but it matters for maintainability in the long run.
As for how the tool actually pulls off the trick, FlyOOBE and Flyby11 lean on the Windows Server variant of setup to skip TPM and Secure Boot checks while still installing a normal copy of Windows 11. ISO downloading and mounting happen automatically through the Fido script by pbatard, matching Microsoft's own documented workaround.
One caveat worth flagging: the POPCNT requirement cannot be bypassed. If your CPU predates that instruction set, you're out of luck regardless of what the marketing implies. That limitation has been baked into the compatibility checker since the 2.3 line, so it's not new.
Where to get it
FlyOOBE 3.0 is now the only maintained edition. The previous Nightly build and the standalone Flyby11 Classic are no longer distributed separately; the upgrade path is built directly into the app. A minimal Flyby11 Classic download still exists if you only want that one feature.
Head here to download the release from GitHub.
