New Update Flyoobe (formerly Flyby11)

Flyby11 version 2.6
For those who like to push the boundaries, this build adds an experimental upgrade mode.
When you check Enable experimental upgrade mode (bypass compatibility and driver checks), the setup will:
  • Bypass system requirement checks (TPM, RAM, Secure Boot, etc.)
  • Skip driver compatibility verification
  • Attempt to migrate drivers from your current system to the new install
 
Flyby11 version 3.0
  • Flyby11 now supports the Media Creation Tool as a download source. A suggestion that came from some clever users who pointed me to the YouTube tutorial by memory It actually makes a lot of sense and I wonder why I didn’t add it earlier. Big thanks to the creator Memory! If you choose this method, you can directly watch the tutorial from within the app. If the Fido downloader doesnt work for you or the ISO language doesnt match your system, it's recommended to use the Media Creation Tool instead, it always downloads the ISO in your system language and "gives you the best chance of keeping files, settings, and apps"
  • Improved ISO mounting using PowerShell for more reliable drive detection
  • Improved bypass parameter handling for /Compat IgnoreWarning /MigrateDrivers All
  • Added Hungarian language support. #192 Thanks to JohnFowler58 - Overview
  • Updated Japanese translations #177 Thanks to reindex-ot - Overview
 
Flyby11 was never just a one-time upgrade tool, it was a mission: to bring Windows 11 to unsupported PCs. But what happens after the upgrade? Flyby11 deserved to evolve, and now it has.

Over the past few days, Ive been building a new OOBE experience (my own platform, OobeLux) and Flyby11 is now deeply integrated into it.
The result? Something like Frankenstein's monster (but way more helpful): FlyOobe
FlyOobe doesnt just help with the upgrade anymore. If you're already on Windows 11 (with or without Flyby11), this app still has a job to do. It helps you fully set up and customize your system after the upgrade from personalization, account setup, app tweaks, Windows updates, debloating, UI & experience tuning, and more... (We're talking about things Microsoft hides from you in the OOBE and doesnt let us do right away)

So, FlyOobe is basically Flyby11 version 4.0 (even if the app version got reset internally) and at first it just helps you upgrade to Windows 11. If you click the "Next >" button, you can continue setting up your Windows 11. Of course, the app also supports Windows 10. FlyOobe is way smarter than Flyby11 release 3.0. Compatibility checks are done automatically in the background, and you can even ask Copilot for help directly if you want.
 

Improvements & Fixes​

  • Improved upgrade logic for bypassing Windows 11 requirements
  • Automatic compatibility checks before ISO selection
  • New hybrid UI with dark main window and a light sidebar. Drop a comment: full dark, back to light, or keep the hybrid look?
  • More intelligent handling of setups with and without Internet
  • Hundreds of fixes, cleanups, and refinements under the hood
  • Clippy was killed. Again.
  • The old FAQ was removed (a new one will appear in the repo soon)
  • Localizations are currently offline because they no longer fit with the core features. I still need to figure out how to move forward with this

OOBE coverage includes:
  • Region and language settings
  • Keyboard layout
  • Internet connection (or offline setup)
  • Account creation (Microsoft / local)
  • Privacy and telemetry controls
  • Personalization: wallpaper, theme, taskbar layout
  • Device naming
  • Pre-installed app cleanup (debloating)
  • Windows updates and tweaks
  • Copilot integration - ask for help any time during setup
 

What's new in 0.30​

  • I've refreshed the UI with a modern, light design that uses a frosted-glass look inspired by Windows 11. It now feels cleaner, more consistent, and visually up to date
  • The upgrade window has been reworked and now lets you choose your preferred download source directly
  • Added Stack-Based Navigation, so the back button now follows your actual click history instead of a fixed linear sequence, making navigation feel more natural
  • Otimized the UI initialization so that controls are only loaded when needed. This leads to faster startup times
  • Several display issues related to high or custom DPI settings have been fixed
  • Added a new OOBE page called “Setup Extensions” which appears in the final step and allows custom scripts to be executed
  • ISO mounting has been further refined with several bug fixes. If you encountered issues with the last Flyby11 release, please try again using Flyoobe
  • Error handling has been improved, with optional Copilot support for smarter troubleshooting
 

What's new in 0.40​

  • Added update check feature. Flyoobe now automatically checks for updates via the GitHub API when you open the About screen (bottom-right corner). This feature didnt exist in Flyby11
  • Redesigned OOBE Windows Update page with improved layout and various code fixes
  • Enhanced Manage Installed Apps (Debloating) page and added smarter search, a one-click “Select all apps” option ("I don't want any of these apps"), and minor UI tweaks
  • Modernized Upgrading (first OOBE screen) with sleek drag-and-drop panel
  • Tons of small fixes under the hood.
 

What's new in 1.0​

  • Gave the UI wrapper a cleaner, more modern look and made navigation smoother
  • Upgrade Assistant (formerly FlyBy11) updated and tuned again for Windows 11 24H2 upgrades
  • OOBE views now run on a faster, more stable code base
  • Debloat section reorganized so it’s easier to pick what to remove and faster to run
  • Tweaks and changes now apply instantly
  • “Setup Extensions” step is now modular – just drop your own PowerShell scripts in the Scripts folder and they’ll run automatically (instructions coming soon)
  • Minor performance improvements across all steps
  • Improved Copilot integration for better reliability

Heads up: Flyby11 and Flyoobe will be merged into a single project in an upcoming release, along with further code cleanups and improvements. I’ll drop the full Flyoobe source once both projects are merge, so right now itas just a bit too messy, and Ive still got time for some refactoring 😃
 

What’s new in Flyoobe 1.1​

  • The setup steps are now neatly displayed right inside the UI wrapper, giving you an at-a-glance overview of the entire process
  • Flyoobe now automatically detects if you’re already on Windows 11 (for example, if you upgraded from Windows 10) and lets you apply all customizations directly from a single interface inside Flyoobe. This feature was originally planned for the recently released final version 1.0, but I didn’t manage to get it in on time.
 

What’s new in Flyoobe 1.2​

  • New "OOBE" windows for custom Windows 11 installs and repairs. Currently rolled out in Preview with support for MCT and Rufus (limited CLI, no stable automation yet). Still considering whether to add a native solution, similar to the very first Flyby11 builds, holding off until future releases. Flyoobe now already covers the full spectrum: upgrades, clean installs, and the complete out-of-box experience
  • Improved ISO mounting now filters volumes to only those that actually have a drive letter
  • Minor performance optimizations and reduced RAM usage.
 
Flyoobe 1.3
  • New OOBE view that lets you set a default browser right after installation – and even download a third-party browser if you want (see Intro video)
  • Personalization OOBE view now includes extra options like aligning the Windows 11 taskbar left or center
  • Setup/Finalization extension view has been optimized and extended at its core
  • Improved header design that clearly shows which OOBE view is currently active
  • DPI handling improved
  • Lots of UI polish
  • Various minor bug fixes
  • Heads up: Flyby11 and Flyoobe will be merged into a single project in an upcoming release, along with further code cleanups and improvements. I’ll drop the full Flyoobe source once both projects are merge, so right now its just a bit too messy, and i've still got time for some refactoring😃
 
Flyoobe (Flyby11) 1.4

What’s new in Flyoobe 1.4​

  • The executable now goes by flyo.exe (think “fly/start”) – your launchpad into the app
  • Added a brand-new little helper called spot.exe. I always found it annoying to hunt down tools during Windows 11 setup via the Start menu or Run dialog. Spot fixes that: it surfaces the most important locations/tools and even doubles as a mini help center for Flyoobe. Type Help and you’ll instantly see key GitHub issues. (Spot = 🔍/radar.) Launch it by clicking the search icon in the top right.
  • Added support for Windows 10 Consumer ESU enrollment (with or without a Microsoft account) via the legendary abbodi1406 ConsumerESU script → GitHub - abbodi1406/ConsumerESU: Windows 10 Consumer ESU Enrollment
  • Further UI polish for the Bee UI
  • Refactored numerous OOBE views for a cleaner structure and easier maintenance.
 
Flyoobe (Flyby11) 1.5

What’s new in Flyoobe 1.5​

This release brings a major upgrade to the Install only area, making both clean installs and repair scenarios easily accessible for everyone.

The concept:

Combine native Windows built-in tools/providers (like Reset or In-place Upgrade) with external tools (like Media Creation Tool or Rufus) all in one place, directly accessible from Flyoobe. External tools can even be launched with CLI arguments (note: Rufus CLI is limited, and Ventoy CLI isnt integrated yet).
The idea: bundle every possible installation and repair path right at your fingertips.

Ive been working on these features for quite a while, with one clear goal: to give the end user everything they need for installation and repair in one single place. From booting into the BIOS, to resetting Windows, to doing a clean install, all the steps that usually feel hidden or complicated are now directly accessible.

With this update, the Install Only section gets a major overhaul. It brings together the native Windows tools (like Reset or In-place Upgrade) and the most popular community tools (Media Creation Tool, Rufus, etc.), all in one interface. This release also sets the stage for renaming the repository from Flyby11 to Flyoobe in the coming weeks, so both projects will be unified in a single codebase.

Don't be put off by the number of options in the dropdown menu, each one comes with a short explanation once you select it. And in future versions, I'll add smart auto-recommendations. I've chosen not to rely on AI inside Flyoobe itself, even though the Copilot button will remain down in the corner as an optional helper

Maybe at some point I'll give in and build a native ISO creator too, but I dont really want to compete with Rufus 😅

Available Providers
  • Native Reset Provider: Launches the built-in Reset this PC wizard. Choose between Keep files or Remove everything with cloud or local reinstall.
  • Rufus Provider: Lets you build a bootable USB stick using Rufus. CLI arguments are supported (ISO, filesystem, locale, etc.), though Rufus CLI is limited.
  • Media Creation Tool (MCT) Provider: Starts Microsofts official Media Creation Tool. Create a Windows 10/11 USB or ISO directly from Microsoft servers.
  • Ventoy Provider: Installs Ventoy onto a USB drive. Afterwards you can just copy multiple ISOs onto it and boot from them, no re-format required
  • In-place Repair Upgrade Provider: Runs Windows setup.exe from a mounted ISO in repair/upgrade mode, keeping apps and files intact
  • Run Setup from ISO Provider: Starts the full Windows Setup wizard from an ISO for a complete clean installation
  • Mount ISO Provider: Mount any Windows ISO natively with PowerShell > so you can run setup or extract files easily
  • Reboot to UEFI Provider: Reboots the PC straight into firmware/UEFI settings (BIOS) without pressing hotkeys on boot
  • Boot Menu Info Provider: Shows a quick list of common Boot Menu hotkeys (F12, F9, F8, …) so you don't have to Google every time
  • Backup Drivers Provider: Exports all currently installed drivers into C:\DriversBackup. Perfect before a clean install to avoid missing NIC/Wi-Fi drivers afterwards
  • Spot.exe (introduced in v1.4) now fully supports High DPI displays
  • Windows Update section has been completely rewritten for better reliability and UX
  • Tweaks and polish the Bee-UI around the edges
 
Flyoobe (Flyby11) - 1.6

What’s new in Flyoobe 1.6​

This release brings a major upgrade to the Install only area, making both clean installs and repair scenarios easily accessible for everyone.
  • New Home/Start View: A fresh entry screen presenting the 4 core options of the app (also accessible via Setup)
  • Install Only OOBE View (introduced in v1.5) has been expanded with badges, full-text search, and one-click actions, plus dozens of small optimizations for clean installs and repairs
  • Unified UI: All views got another visual refresh for a more consistent experience
  • Smarter Bloatware Remover: Detects and removes unnecessary apps more reliably
  • App Installer: Now includes a few more apps to choose from
  • Experience OOBE View: Core functionality has been updated and improved
  • Performance: Lower RAM usage and slightly faster startup (a few milliseconds shaved off)
  • General polish: Minor optimizations and fixes throughout
  • You can now try out Nightly (Dev) builds updated regularly with the latest features and fixes before they roll into the next stable release
  • This release also sets the stage for renaming the repository from Flyby11 to Flyoobe in the coming weeks, so both projects will be unified in a single codebase.
 
Flyoobe (Flyby11) version 1.7

What’s new in Flyoobe 1.7​

  • New OOBE page to discover and disable Windows Copilot and AI features right after installing Windows 11
  • Improved Apps page for “bloatware” removal - now supports presets ranging from Full to Minimal, plus the option to load community presets from GitHub
  • Optimized Install Provider “Backup installed drivers” feature, with support for exporting to custom folders
  • Fixed a critical High DPI bug
  • Minor tweaks to the Bee UI
  • Extensive refactoring under the hood with the first commits already live on GitHub
  • You can now try out Nightly (Dev) builds updated regularly with the latest features and fixes before they roll into the next stable release (NO NIGHTLY AVAILABLE)
 
Flyoobe (Flyby11) version 1.10

What’s new in Flyoobe 1.10​

  • This is a major update!
  • The repo has finally been renamed from Flyby11 to Flyoobe.
  • The 1.10 preview release oddly threw some false positives, caused by one of the simplest OpenURL methods C# ever had. Well, AV engines remain a mystery. Turns out the extension download + OpenURL/Process.Start combo tripped heuristics (looked like a classic downloader/phishing attempt). Fixed now
  • Navigation has been restructured: Introduced a modern bottom navigation with Next button: the OOBE/Installer now follows a clear step-by-step flow. I replaced the old right-side TreeView with large, tappable buttons at the bottom, making navigation easier and more comfortable than narrow tree nodes
  • Improved AI detection and review
  • Improved Refresh button (Ref. IView)
  • In some cases no Wi-Fi networks were shown when location services were disabled.
    Since Windows requires location access for Wi-Fi scanning, this resulted in empty results. Improved behavior: if access is denied, the app now displays a helpful message and redirects the user to the Windows Location Settings to enable access
  • Improved control naming conventions to align with Microsoft Windows style, making the interface more intuitive and familiar for users
  • Experience page streamlined by removing redundancies related to Microsoft Edge, AI, and UI; AI features have been moved into a dedicated OOBE page
  • Extended scripting support for Setup Extensions: now anyonecan provide PowerShell scripts.
    • How it works can be read here: Write an Extension Guide
    • Extensions can also be downloaded directly via a URL
    • Local extensions/scripts can be imported from your PC
  • 🧩New Extensions:
    • Default Power Plan – quickly switch between Balanced, High Performance, and Battery Saver during setup
    • File Explorer Tweaks – configure common Explorer settings such as showing file extensions, showing hidden files, or opening This PC by default
    • Post-setup Cleanup – remove temporary files, Windows.old, component store leftovers, and update caches to free up disk space after installation
    • Windows 11 Honest Mode – inspect telemetry settings, startup apps, and scheduled tasks to reveal what Windows is running in the background
 
Flyoobe (Flyby11) version 1.11

What’s new in Flyoobe 1.11​


My Github repositories and organization were temporarily unavailable for about 10 hours (source @X) due to an automatic account suspension.

This issue was resolved at 03:58 UTC (05:58 in Germany). GitHub Support told me that “sometimes our abuse-detecting systems highlight accounts that need to be manually reviewed.”

I assume this may have been triggered because Flyoobe is currently receiving a lot of attention with over 10k unique visitors per day.

In that short downtime I must have received at least 50 emails with questions and concerns - some feared Microsoft might be behind it 😆 , others thought I had given up Windows development, and a few even worried the app had turned malicious. None of that is true 😉 You know, when Explorer randomly crashes and all your icons disappear...🤦

As a precaution, I have improved the update mechanism in Flyoobe so it no longer risks putting unnecessary load on the GitHub API.

Please grab the new update right away so you're on the safe side (and help keep things running smoothly)
NOTE: releases and stats are still syncing on GitHub, so they might look empty for now


  • Added OOBE Assist tile (Windows 11 only) – a friendly welcome after Microsoft's OOBE, showing setup steps we can only dream of in the stock flow (set a real default browser, review AI features, debloat preinstalled apps, and more)
  • The ToolSpot.exe has been removed as an external helper. Instead, the Extensions button in the top-right corner now replaces the old "Spot" button, since extensions can pretty much cover everything Spot used to do
  • The ExtensionsInputDialog (Install from Url) now includes a Browse Extensions link, making it easier to grab scripts that aren't shipped with the program
  • Improved execution of scripts/extensions in embedded and console mode
  • Updated several OOBE pages in the UI, along with context menu entries (including those for extensions/scripts)
  • New Default Extensions:
    Microsoft Defender maintenance: update signatures, repair, show status. Quite handy to ensure you have the latest definitions right after a fresh Windows 11 install
    • Post-install essentials: quick launcher for Windows tools
  • Refactored update checker: previously it parsed JSON from the GitHub API on every app start (heavy + rate-limited). Now it simply resolves the /releases/latest redirect URL (lightweight, no abuse detection, no risk of false DDoS flagging)
 
Flyoobe (Flyby11) version 1.20

What’s new​


Preview v1.20 – A Fresh New Design

With this release, Flyoobe takes a big step forward in terms of modern UI and Windows 11 style.
The old design (bottom navigation, heavy gray) looked more like a classic Win10 setup wizard.
The new design is modern, structured, colorful – it makes Flyoobe feel at home on Windows 11 and closer to Microsoft’s Fluent Design principles.

  • Navigation sidebar (left-aligned)
    Replaces the old bottom bar. This follows modern design guidelines (e.g. Settings, Edge) and gives more room for content.
  • Lighter surfaces, less gray
    The overall UI now feels brighter and cleaner, aligned with Windows 11’s visual style.
  • Improved performance
    The lightweight UI not only looks fresher, it also makes Flyoobe feel faster, smoother and more responsive
  • Improved provider and extensions integration, making the overall experience faster and smoother
 
I used Flyoobe (Flyby11) version 1.20 to install the pre-release version of Windows 11 25H2, and it works perfectly on a 15-year-old computer.
One question: will Flyoobe (Flyby11) be available in multiple languages for those of us who don't have English skills? Thanks.
Seems translations might be still work in progress but not really sure... ;)