![]() |
Flyby11 - Printable Version +- Too Many Message Boards (https://tmmb.co.nz/forums) +-- Forum: PC World Forums (https://tmmb.co.nz/forums/forumdisplay.php?fid=86) +--- Forum: PressF1 (https://tmmb.co.nz/forums/forumdisplay.php?fid=87) +--- Thread: Flyby11 (/showthread.php?tid=4195) |
Flyby11 - Galaxy01 - 19-07-2025 What you guys think of this? Safe to use? https://github.com/builtbybel/Flyby11 RE: Flyby11 - king1 - 19-07-2025 never used that one but I have used this and it hasn't let me down https://github.com/AveYo/MediaCreationTool.bat 1. Backup! 2. Download the zip from the CODE button in the link above 3. extract it somewhere 4. run MediaCreationTool.bat or to automate the initial upgrade process... rename MediaCreationTool.bat as auto 11 MediaCreationTool.bat then run it and sit back and watch it do its thing... RE: Flyby11 - Wainuitech - 20-07-2025 Tried it Just last week on a Workshop PC that wasn't capable of "Officially" Running Windows 11 -- Worked Perfectly. PAys to watch some videos 1st. https://www.youtube.com/watch?v=Yd3isXSBTUs RE: Flyby11 - Agent_24 - 20-07-2025 The tool is probably fine. The question is - if you're installing Windows 11 on unsupported hardware, will there be a point in the future when Microsoft releases an update that is incompatible with whatever changes were made to do an unofficial installation, and leave the system unbootable, or similar? Just be aware of that possibility. Not saying it will happen - but I imagine it's plausible. RE: Flyby11 - Wainuitech - 20-07-2025 (Yesterday, 01:50 PM)Agent_24 Wrote: The question is - if you're installing Windows 11 on unsupported hardware, will there be a point in the future when Microsoft releases an update that is incompatible with whatever changes were made to do an unofficial installation, and leave the system unbootable, or similar? That's 100% true; I actually had it happen on an incompatible workshop PC. Windows 11 worked fine for roughly 5 months, but after one (security) update, it wouldn't boot anymore, and I couldn't roll back. Wiped the drive put W11 back, again same update caused the same problem. Wiped drive ran W10 again, few months later tried W11 again, this time no problem, been working fine for over a year now. |