# Flyoobe: a Windows 11 setup companion that reviews defaults instead of hiding them > Flyoobe is an MIT-licensed C# application for Windows 11 setup that turns OOBE choices into a reviewable list of recommendations, apps and recipes. The catch: the refactored 3.x source is not published yet, so the code on the default branch is the previous generation. **builtbybel/Flyoobe** — Fly through your Windows 11 setup 🐝 - Repository: https://github.com/builtbybel/Flyoobe - Stars: 7,367 · Forks: 382 - Language: C# - License: MIT - Published: 2026-09-22 · Updated: 2026-09-22 · Language: en - Canonical page: https://hysenlabs.com/projects/builtbybel-flyoobe ## The problem Flyoobe targets: setup as a review, not a click-through Windows 11 setup asks a long series of questions, and most of them have a default that someone else chose. Flyoobe's README frames the goal plainly: it is "a focused Windows setup companion for people who want to make deliberate choices instead of clicking through somebody else's defaults." That is the whole pitch, and it is narrower than the older versions suggest. The project began as Flyby11, a small tool for getting usable PCs past the Windows 11 hardware checks. Flyoobe grew out of what happened next: once the machine was installed, the harder questions were which defaults to keep, which preinstalled apps to remove, and how to repeat the same setup without maintaining an unreadable script. Flyoobe 3 answers those questions with a single setup flow covering accounts, networking, browsers, apps, personalization and Windows Update. The audience is specific. This is for a person who is installing Windows 11 on their own hardware and wants to see each decision, not for fleet deployment. There is no documented unattended mode, no MDT or Intune integration, and no server component. If you manage hundreds of machines, Flyoobe's per-machine review flow is the opposite of what you want. ## How Flyoobe 3 organises recommendations, recipes and Setup Actions The README describes a flow built around file-based recommendations. Flyoobe checks the PC against those recommendations, then separates real differences from choices that are simply personal. That distinction matters: a recommendation about a security setting is not the same as a preference about a browser, and the interface is meant to keep them apart. Preinstalled apps are handled with a confirmation step. The README states that Flyoobe lets you "review and remove preinstalled apps only after confirmation," which is a deliberate brake on bulk debloating. Recipes are the repeatability mechanism: you export a recipe so the same choices can be applied again, and the README says recipes are exported "without embedding opaque code in them." That is a design constraint against the pattern where a tweak tool turns into a folder of unexplained scripts. Setup Actions are the extension point, and they are optional and disabled by default. An action is a small PowerShell-based job that can provide a description, selectable commands, live output and recipe integration in approved cases. The packages live in the Actions directory, and the authoring guide is docs/setup-actions.md. The README is explicit that Flyoobe never runs an action merely because the package exists. The repository layout reflects this split. Alongside Flyoobe.sln, Flyoobe/, Actions/, assets/ and docs/, there is a legacy/ directory. That folder is where the history lives, and the README says the previous Flyoobe implementation still present in the source tree is legacy software. ## Installing Flyoobe and running a first setup review There is no package manager entry documented, and no build-from-source instructions for the current release, because the 3.x source is not published yet. The README points to a single official source: the releases page at github.com/builtbybel/Flyoobe/releases. It also carries a security alert stating that flyoobe.com and the GitHub account github.com/flyoobe are not affiliated with the project, and that official releases are published only through the builtbybel repository. So the install step is a download, not a command. Open the latest release and take the current Flyoobe 3 asset: ```bash # No package manager or CLI install is documented. # Download Flyoobe 3 from the official releases page: # https://github.com/builtbybel/Flyoobe/releases/latest ``` The README also keeps older builds available for deliberate legacy use. Flyoobe 2.4.854 is distributed as FlyoobeApp.zip, and Flyby11 Classic as Flyby11-classic-deprecated.zip. The README states that neither represents active development. Setup Actions need one extra step after Flyoobe is running. Download the Actions asset from the same release page, extract the included Actions folder into Flyoobe's Data folder, and enable the feature in the application: ```text Data\Actions\\action.ini Settings > Advanced > enable Setup Actions ``` After enabling it, you should see the actions listed with their descriptions. Read an action before running it, particularly one that requests administrator rights or downloads code. The README's caution is blunt on this point, and it is the right posture for any tool that executes PowerShell on your behalf. ## The source tree you can read is not the build you run This is the limitation that should shape any adoption decision. The README states that Flyoobe 3 has begun rolling out and the project changed substantially, that the application was rebuilt around a smaller core, and that the refactored 3.x source is still being prepared for publication. The repository status table is equally direct: Flyoobe 3 releases are active, the refactored source is "being prepared; coming soon," and the source currently on the default branch is the previous Flyoobe generation. The README calls this split intentional and says the new structure will be published when it is ready to be maintained in public rather than uploaded in a hurry. That is a defensible reason, but it has a concrete consequence for you. If you audit code before running a setup tool, you cannot audit the 3.x binary against the 3.x source today. You are trusting the release artifact. Two related boundaries are worth stating. Flyby11 is retained but no longer actively maintained, and the README says the same applies to the previous Flyoobe implementation in the source tree. Flyoobe Extensions, an earlier extension model, is retired and replaced by Setup Actions, so any guide referencing extensions describes something that no longer exists in the current design. ## Flyoobe compared with Rufus and with its own predecessor The comparison people actually search for is Flyoobe against Rufus, and the two solve different problems. Rufus writes bootable installation media. Flyoobe's README describes a setup companion that runs around the Windows setup experience: reviewing recommendations, configuring accounts, networking, browsers, apps, personalization and Windows Update, removing preinstalled apps after confirmation, and exporting recipes. If your problem is that you have no bootable USB, Flyoobe is not the tool. If your problem is that setup keeps making choices for you, a media writer does not address it. The more instructive comparison is Flyoobe against its own earlier versions. Flyoobe 2 grew into what the README calls an ambitious OOBE and upgrade toolbox, and it "accumulated several ways of doing the same job." Flyoobe 3 is described as a reset that keeps the useful ideas and removes the accidental complexity. Flyby11 Classic remains the narrow option for the Windows 10 to 11 in-place upgrade on unsupported hardware, and the README says to choose it only when the classic upgrade workflow is all you need. So the real decision is scope. Flyby11 Classic does one job and is frozen. Flyoobe 3 does the broader setup review and is the version receiving development. Running the older 2.4 build means accepting a workflow the project has already decided to move away from. ## Maintenance, licensing and what the MIT terms do not cover The repository is not archived, and the last push was on 2026-09-21, one day before this article's reference point. Releases are close together: 3.00.44 on 2026-09-18 and 3.01.53 on 2026-09-20. That cadence fits a project in the middle of a rollout, and it also means the 3.x line is moving quickly enough that a guide written today can describe an interface that shifts next week. Upgrade cost is low in the mechanical sense, since there is no service to migrate and no database. The real cost is attention. Each release can change recommendations, the action format or the recipe output, and the changelog is the file to read before replacing a working build. If you rely on exported recipes, re-check that they still apply after a version jump rather than assuming compatibility. The licence is MIT, which permits use, modification and redistribution with the copyright notice and permission notice retained. Two things sit outside that grant. First, the README's security alert is a naming and distribution warning: flyoobe.com and the github.com/flyoobe account are not affiliated with the project, and official releases come only from the builtbybel repository. Second, Setup Actions execute PowerShell that the project did not write. MIT covers Flyoobe's own code, not the behaviour of a third-party action package you choose to enable. Read the action first. ## Conclusion Flyoobe suits people setting up or upgrading Windows 11 who want to see and record each choice rather than accept a vendor default, and who are comfortable running an unsigned third-party tool. It is the wrong pick if you need auditable source for the exact build you run, since the 3.x refactor is not published yet and the default branch holds the previous generation. Do not judge it by the old source tree; download only from github.com/builtbybel/Flyoobe/releases and read the Actions folder before enabling Setup Actions, which are PowerShell and disabled by default. ## FAQ ### Is it safe to use Flyoobe? The README carries a security alert about fake websites and repositories impersonating the project: flyoobe.com and the GitHub account github.com/flyoobe are not affiliated with it, and official releases are published only through github.com/builtbybel/Flyoobe/releases. The optional Setup Actions run PowerShell, and the README advises reading an action before running it, especially when it requests administrator rights or downloads code. ### Which is better, Rufus or Flyoobe? They do different jobs. Rufus is a media writer, while Flyoobe is a setup companion that reviews recommendations, configures accounts, networking, browsers, apps and Windows Update, removes preinstalled apps after confirmation, and exports recipes. Flyoobe's README does not describe writing bootable installation media. ### Which is better, Flyby11 or Flyoobe? Flyby11 is the historical predecessor and the README states it is retained but no longer actively maintained. Flyoobe 3 is the current generation and the version receiving active development, with a broader setup review flow. Flyby11 Classic is described as the choice only when the classic Windows 10 to 11 upgrade workflow is all you need. ### How do I install Flyoobe? There is no documented package manager or CLI install. Download the current Flyoobe 3 asset from the official releases page at github.com/builtbybel/Flyoobe/releases, and avoid the impersonating sites named in the README's security alert. ### How do I use Flyoobe to upgrade to Windows 11? The README lists opening the Windows upgrade path as part of the current workflow when the machine and scenario call for it, alongside the setup review features. For the classic Windows 10 to 11 in-place upgrade on unsupported hardware, the README points to Flyby11 Classic and says to choose it only when that workflow is all you need. ### How do I use the Flyoobe app? Flyoobe 3 presents setup as a short review: check the PC against file-based recommendations, configure accounts, networking, browsers, apps, personalization and Windows Update, review and remove preinstalled apps after confirmation, and export recipes. Optional Setup Actions extend the post-install workflow and are disabled by default. ## Sources - [builtbybel/Flyoobe on GitHub](https://github.com/builtbybel/Flyoobe) - [Issues](https://github.com/builtbybel/Flyoobe/issues) - [License: MIT](https://github.com/builtbybel/Flyoobe/blob/main/LICENSE) - [README](https://github.com/builtbybel/Flyoobe/blob/main/README.md) - [Releases](https://github.com/builtbybel/Flyoobe/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/builtbybel-flyoobe