AI prompts
base on Fly through your Windows 11 setup π # π Flyoobe (ex-Flyby11) β Windows Setup Assistant
_No specs? No problem!_
<img width="1024" height="1024" alt="Flyoobe_mockup2" src="https://github.com/user-attachments/assets/8096fa8f-e1b5-4f88-8dfd-938327177aea" />
---
## π’ Quick Note for Returning Users
**Flyoobe is the natural evolution of Flyby11.**
The classic Flyby11 upgrader still exists and is included inside Flyoobe,
plus it's also available as a **separate download** if you only want the minimal upgrade tool.
You can now **choose**:
| Version | Purpose | Features | Download |
|---------|---------|----------|----------|
| **Flyoobe** (New) | Upgrade + OOBE Toolkit | β’ Windows 10 β 11 upgrades<br>β’ OOBE customization<br>β’ Tweaks & Debloat<br>β’ Scriptable setup extensions | [β¬ Download Flyoobe](https://github.com/builtbybel/Flyoobe/releases/latest) |
| **Flyby11** (Classic) | Upgrade Only | β’ Win10 β Win11 Inplace upgrade<br>β’ Hardware check bypass<br>β’ Minimal footprint | [β¬ Download Flyby11 Classic](https://github.com/builtbybel/Flyoobe/releases/latest) |
---
## π Why Flyoobe?
Originally, **Flyby11** was a simple patcher to remove the restrictions stopping you from installing Windows 11 (24H2) on unsupported hardware.
Old PC? No TPM, no Secure Boot, unsupported CPU? Flyby11 let you install Windows 11 anyway.
After helping thousands upgrade, one thing became clear:
**Bypassing checks is only half the battle.**
We needed a **full setup solution** β one that respects user choices instead of Microsoft's defaults.
**Flyoobe** was the next step:
- Skip the fluff
- Remove the junk
- Take full control from first boot
Because your PC should work for you, not the other way around.
Flyoobe keeps the original idea alive and pushes it even further.
---
No complicated steps.
**Just run the tool** (see ["Releases"](https://github.com/builtbybel/Flyoobe/releases/latest)),
unpack if needed, and you'll be running Windows 11 on your βunsupportedβ machine in no time.
Think of it as sneaking through the back door without anyone noticing.
---
## π Technical Overview
**Flyoobe method:**
- Uses Windows Server variant of setup β skips TPM, Secure Boot, CPU checks
- Still installs **normal Windows 11**
- ISO download/mount handled automatically (via [Fido script](https://github.com/pbatard/Fido))
- Matches Microsoftβs own documented workaround for upgrading unsupported devices ([source](https://support.microsoft.com/en-us/windows/ways-to-install-windows-11-e0edbbfb-cfc5-4011-868b-2ce77ac7c70e))
---
## π‘ Why Keep Flyoobe Alive?
- **Upgrade freedom** β Donβt ditch a perfectly fine PC just because Microsoft says so
- **Eco-friendly** β Less e-waste from forced upgrades
- **Save money** β No need for new hardware if yours still works
---
## β Disclaimer
Flyby11/Flyoobe uses known, currently working methods to bypass Windows 11 24H2 restrictions.
**POPCNT requirement** cannot be bypassed β needed for Win11 24H2.
Introduced a compatibility checker in v2.3 to warn if unsupported.
---
## π FAQ
<details>
<summary>β Will my unsupported device still get Windows 11 updates?</summary>
**Short answer:** Yes β for now. But there are no guarantees.
Microsoft says: _"These devices aren't guaranteed to receive updates."_
π [Source β Microsoft Support](https://support.microsoft.com/en-us/windows/windows-11-on-devices-that-don-t-meet-minimum-system-requirements-0b2dc4a2-5933-4ad4-9c09-ef0a331518f1)
Reality: Most still get monthly security updates, but:
- Likely no automatic major version upgrades
- Future updates may fail if new hardware features are required
- Microsoft could block updates anytime
Bottom line: Works today β but unsupported means you accept the risk. π
</details>
---
## β€οΈ Support Development
If Flyby11 or Flyoobe has helped you, consider supporting its continued development.
Every bit helps keep the project alive and improving. ππβ
π [**Donate here**](https://www.paypal.com/donate?hosted_button_id=MY7HX4QLYR4KG)
", Assign "at most 3 tags" to the expected json: {"id":"12773","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"