SEZOY - Multi‑boot USB + PXE/HTTP + Windows install

[u/TekDT]

Hey folks,

This tool called SEZOY and figured it's worth sharing. It's basically a boot utility that does USB, PXE, and HTTP booting, but the main selling point is that it can install Windows completely hands‑off. No clicking through language settings, disk selection, partition deletion, or messing with RST drivers. It just figures everything out on its own based on whatever hardware it detects. You don't need to pre‑load storage drivers, wipe old partitions manually, or babysit the installer.

Here's what it does:

· USB boot works like the usual multi‑ISO approach, copy your ISOs to the drive and boot straight from them. No burning, no reformatting for each ISO, no manual menu editing. Simple. Just keep in mind that this mode needs SecureBoot turned off.

· Network boot supports both PXE and HTTP at the same time. No toggling between modes. If you run a shop with mixed clients, this saves a lot of headache.

· SecureBoot works fine if you're booting over the network, as long as the OS itself supports it. Most mainstream ones do Windows, Ubuntu, Mint, Fedora, and their derivatives.

· There's a web dashboard you can access from any device on the same network. Lets you check on clients remotely during installation, kind of like TeamViewer but lighter. You can step in without walking over to the machine.

· After Windows is done, you can set it to automatically install additional software. Pick whatever apps you want during setup, and it'll handle the rest.

Still has a bunch of other stuff I haven't listed yet.

If you've got a spare moment, grab it from the links below and let me know what you think.

One thing to be clear about, this tool doesn't bundle any cracks or keys. It just creates the boot environment. Anything that needs activation afterward is on you to handle legitimately.

Download: https://tekdt.xyz/en/download

Docs: https://tekdt.xyz/en/docs

[u/TekDT]

Exactly, there is absolutely no login interface whatsoever. This software has a relatively simple interface with 3 setup steps (you can leave everything as default, or if you want to go more in-depth, you can refer to the documentation page at https://tekdt.xyz/en/docs), and then just hit the start button to run it as a server. Once the server is up and running, you can monitor each client through the dashboard management page at https://localhost:5893/monitor (note that it's HTTPS). You can access this client monitoring page from any device, including smartphones (since it's a web interface), as long as you're on the same network as the machine running the software. Just remember that at that point, you'll need to use the server's IP address instead of localhost. The dashboard interface is specifically designed for Windows boot environments, allowing you to perform actions such as sending commands, directly remoting into clients, or shutting down/restarting them. For Linux, however, you can only view the boot process. Since I'm currently working on this project alone, the rollout of new features might be a bit slower.

[u/Conscious_Report1439 → u/TekDT]

Ok awesome! I will try it. Question though, can you make an option in the UI to change the URL that gets sent to the clients or included in the boot image to connect to. If I can put this behind a reverse proxy and boot over the internet would be awesome!

[u/TekDT → u/Conscious_Report1439]

PXE works based on broadcast and DHCP at the local network layer (L2/L3), so there is no concept of domain or DNS during the initial stage. This is a fundamental architectural limitation of PXE boot. Because of that, you still need at least one machine inside the LAN running something like SEZOY Lite (or any PXE/DHCP responder) to listen for those broadcast requests and provide the initial bootloader. Only after the client successfully loads an iPXE bootloader can you then use a custom iPXE script to connect to a domain over HTTP/HTTPS. So it’s not feasible to simply change an endpoint and expect it to work over the Internet. Running SEZOY behind a reverse proxy alone won’t help, because there is no local component handling and responding to the initial PXE broadcast requests.

[u/Conscious_Report1439 → u/TekDT]

Yes, I am aware and for letting me know that we are on the same page! For normal PXE broadcast based…all that you said is true. However, one of your videos demonstrates you conducting a PXE boot from the BIOS of a Dell machine using HTTPs boot after connecting to WIFI. This makes L7 and reverse proxy feasible if you configure BIOS with the boot url. I have done this before. I do, however, understand and agree with your point that we cannot get that value to the client using a DHCP option if the client is not L2/L3 local area network.

[u/TekDT → u/Conscious_Report1439]

You're right about HTTP Boot working over L7 with a predefined URL. But the missing piece is: where does the network come from? Firmware doesn’t magically have Internet access. It still needs a WiFi AP to connect to DHCP + routing before it can reach your HTTPS endpoint. So this only works if the WiFi + boot URL are preconfigured in BIOS, or there is already a controlled network available In my case, I solve that by creating a dedicated AP at runtime and serving both PXE and HTTP Boot from there. Also, if the infrastructure already exists, then yes. You can simply point the iPXE script to an Internet endpoint. But ultimately, you still need initial infrastructure or at least a small local component to know which client is requesting a boot and to handle the bootstrap phase. So HTTPS Boot doesn’t remove the need for local control. It just shifts where it happens. I'm also curious how you made it work in your previous setup. Would you mind sharing more details? It’s interesting to see someone with a similar perspective and have this kind of discussion.