Caution
SECURITY ALERT: Fake websites and repositories are impersonating Flyoobe.
flyoobe.com and the GitHub account github.com/flyoobe are not affiliated with this project. Do not download Flyoobe from either location. Official releases are published only through github.com/builtbybel/Flyoobe. Read the original community report in Discussion #491.
Flyoobe is a focused Windows setup companion for people who want to make deliberate choices instead of clicking through somebody else's defaults.
Important
Flyoobe 3 has begun rolling out, and the project has changed substantially. The application was rebuilt around a smaller, cleaner core. The refactored 3.x source is still being prepared for publication, so the source currently visible in this repository represents the previous generation. It will be replaced as soon as the new structure is ready to be maintained in public, not merely uploaded in a hurry.
Official downloads · Read the changelog · Explore the documentation
The current generation and the version receiving active development.
Set up Windows, review recommendations, choose apps, remove unwanted packages,
reuse recipes and add optional Setup Actions from one focused application.
⬇️ Download the latest Flyoobe release
Looking for an older version? Flyoobe 2.4 and Flyby11 Classic are still available.
The previous complete Flyoobe application with its original OOBE customization, debloating and upgrade workflow.
The small legacy tool for the familiar Windows 10 → 11 in-place upgrade on unsupported hardware. Choose this only when the classic upgrade workflow is all you need.
These versions remain available for deliberate legacy use, but neither represents active development.
This project started as Flyby11, a deliberately small answer to a very specific problem: perfectly usable PCs being stopped at the Windows 11 hardware checks.
Flyby11 helped people get through the installation door. But once they were inside, the more interesting questions began: Which defaults should stay? Which apps are useful? What should be removed? How can the same setup be repeated without turning the whole thing into an unreadable script?
That became Flyoobe.
Flyoobe 2 grew into an ambitious OOBE and upgrade toolbox. It proved the idea, but it also accumulated several ways of doing the same job. Flyoobe 3 is the reset: the useful ideas kept, the accidental complexity removed, and the workflow rebuilt around a simple overview of recommendations and personal choices.
Apparently software grows up much like people do: it stops trying to impress everyone at once and develops strong opinions about sensible defaults and tidy folders.
Flyoobe 3 treats Windows setup as a short, understandable review instead of a maze of tweak pages.
- Check the PC against transparent, file-based recommendations.
- Separate real differences from choices that are simply personal.
- Configure accounts, networking, browsers, apps, personalization and Windows Update from one setup flow.
- Review and remove preinstalled apps only after confirmation.
- Export repeatable recipes without embedding opaque code in them.
- Extend the post-install workflow with optional, local Setup Actions.
- Open the Windows upgrade path when the machine and scenario call for it.
The interface intentionally uses native Windows controls. It is modern where that helps, but it borrows some clarity, colour and friendliness from Windows 7, the last Windows version that seemed to know where everything lived.
| Part | Status |
|---|---|
| Flyoobe 3 releases | Active |
| Refactored Flyoobe 3 source | Being prepared; coming soon |
| Source currently on the default branch | Previous Flyoobe generation |
| Setup Actions | New optional extension model |
| Flyby11 | Historical predecessor; retained but no longer actively maintained |
| Flyoobe Extensions | Retired and replaced by Setup Actions |
This temporary split is intentional. A large refactor deserves a source tree that can be understood after the release-day coffee has worn off.
Setup Actions add small PowerShell-based jobs without turning Flyoobe itself into a collection of hard-coded utilities. Actions can provide descriptions, selectable commands, live output and recipe integration in explicitly approved cases.
They are optional and disabled by default.
- Download the Actions asset from the release page.
- Extract the included
Actionsfolder into Flyoobe'sDatafolder. The resulting path should look likeData\Actions\<action-id>\action.ini. - Open Settings > Advanced in Flyoobe and enable Setup Actions.
The packages maintained for the optional asset live in Actions. The complete authoring and safety guide is in docs/setup-actions.md.
Caution
Setup Actions are PowerShell. Read an action before running it, especially when it requests administrator rights or downloads code. Flyoobe never runs an action merely because the package exists.
Flyby11 remains in the repository because it is where this project began and because the classic upgrader still explains an important part of Flyoobe's history. It is now legacy software and is not actively maintained.
The same applies to the previous Flyoobe implementation currently present in the source tree. It remains available during the transition, but new development targets the refactored Flyoobe 3 codebase. See docs/legacy.md for the exact distinction.
Hardware-check workarounds do not turn unsupported hardware into supported hardware. Microsoft can change setup behavior or update eligibility, and newer Windows releases may introduce requirements that software cannot bypass. Keep backups and understand the trade-off before upgrading.
Flyoobe is built independently and shared freely.
If it saved you time or kept a good PC useful for longer, you can help me continue developing it.
❤️ Support Flyoobe development
Thank you for testing, reporting the strange corners of Windows setup, and giving this little bee far more places to fly than I expected when Flyby11 began.