This is an alternative to Rufus, AOMEI's competing apps & similar. It will format a USB stick for booting, and either copy the needed Windows files from a .wim or .esd image file for a Windows to Go drive, or copy the files currently used by an installed copy of Windows for a Win2Go drive, or copy the files in an ISO for a Windows setup USB stick/drive. For that last option, creating a bootable Windows setup USB stick, to use for installing Windows fresh, it appears that it can modify a Win11 setup to ignore Microsoft's hardware requirements, same as AOMEI's Win11Builder, though this is based on an included file, and not anything I saw documented. Otherwise, e.g. for Win10, an app called Ventoy *might* be quicker / easier, letting you use an ISO as-is rather than copying the individual files in that ISO.
More than a few times [probably too often] I've talked about the difficulties booting USB drives. Older devices use a legacy BIOS -- current devices use UEFI -- many UEFI BIOS can emulate a Legacy BIOS -- a UEFI BIOS may have certain triggers that automatically cause a switch to Legacy BIOS emulation. Long story short, there's no one guaranteed successful way to configure the drive [MBR vs. GPT] or the boot files [Legacy vs. UEFI or both], so like Rufus etc., WinToUSB Professionall gives you choices -- there's no way around that. You can Google to get more info on the devices you use, but in the end you might just have to try creating a USB stick/drive one way, see if it works, and if not, try again using different options.
WinToUSB Professionall itself is a small app that only installs to the program's folder. That folder include x64 & x86 folders, each with the main files for the 64-bit & 32-bit versions respectively. If you install it in 64-bit Windows, the files in x64 are copied to the bin folder & used. The registry gets an uninstall key, and a key for the app when you register it. I had an earlier version of WinToUSB Professionall installed, and this one used that existing activation key.
Please Note:
When Microsoft came up with Windows to Go it was designed as a corporate tool, with Win10 Enterprise signing in to the corporate licensing server(s) every time it ran to establish & maintain activation. The original [now deprecated] tool to create Win 2 Go drives Only accepted Win10 Enterprise ISOs. Windows collects various hardware IDs, which Microsoft uses in some secret way to determine if your Windows license is valid. You're permitted an unknown number of *mostly minor* hardware changes before Windows deactivates. Hard disks are normally not a problem, though eventually too many hard disk swaps *might* trigger deactivation, & while Win10 even accepted a new CPU without deactivating, a new network adapter MAC address is a known no-no, e.g. from swapping the motherboard. You can see the *potential* problem here... You copy your Win10 install, which is tied to your Microsoft account, to a USB drive and run it on a different PC/laptop -- how do Microsoft's activation servers handle that? Remember those servers have historically been a bit wonky, e.g. sometimes refusing to activate Windows when given a valid key. At the very least, using the Win2Go drive on the original PC/laptop would count as a hard disk change, and we don't know how many of those you can have, or how frequently they can be changed. Personally I run Windows Enterprise unactivated on my Win2Go drive, because it only checks for a licensing server that does not exist, and isn't tied to any Microsoft account.
Because [as above] I use the Enterprise versions of Windows for Win2Go, I would never think of copying an installed copy of Windows, physical or VM, to a Win2Go drive, but if that's what you're after, WinToUSB Professionall *might* be your best option. Hasleo's docs say that they've gotten better performance out of Win2Go on a USB stick using the VHD option -- Microsoft's Sysinternals has a small, free app called Disk2vhd that might help in that case. I am skeptical regarding Hasleo's claims when it comes to Windows versions earlier than Win10. I have used projects from reboot[.]pro to create tiny versions of Windows XP, 7, & 8 using emulated & universal drivers, including Win7 on a CD (!), but haven't seen 7 or 8 work near as well as a Win10 Win2Go drive -- they have to rely on hacks & workarounds to stuff that's native to Win10.
And last, I couldn't find any mention of secure boot, including using Google. Two of the biggest unknowns surrounding Win11 is what's going to happen with Win10, and will Microsoft enforce Win11's hardware requirements? Like it or not, if your device meets the requirements for Win11, your best option may turn out to be running Win11. Win11 requires secure boot. It can usually be turned on/off in the BIOS settings, though turning it off may effect other BIOS settings as well, & it could be a mistake-prone PITA to turn it off, boot from USB, then remember to turn it back on, checking other BIOS settings etc. There was enough concerned feedback apparently that the Rufus dev overcame his own long-time objections, making Rufus secure boot compatible. So for now, based on that, and the millions [billions?] of Rufus users, I'll stick with that when possible.