BootForge
Get
← All guides

Make a Windows 11 install USB from an Android phone

How to build a bootable Windows 11 installer USB with only your phone and an OTG cable, no PC required, and what to expect when you boot it.

Yes, this is possible, and you don’t need a working computer to do it. With an Android phone, a USB drive and an OTG adapter you can build a USB stick that boots the Windows 11 installer.

The part that trips people up is that the obvious method is the one that doesn’t work. Writing a Windows ISO directly to a USB drive from a phone generally produces a stick that won’t boot. The routes below avoid that problem entirely.

Why writing a Windows ISO straight to USB fails

Most Android USB writers perform a raw write: they copy the image onto the drive byte for byte. Linux distributions are built to survive that treatment, so it works well for them. Windows ISOs are not built that way.

EtchDroid, the best known free Android writer, states the limitation in its own FAQ: Windows ISOs “use the UDF filesystem, which most BIOSes don’t support on USB drives”, and to work with EtchDroid they “must first be converted to a different filesystem”.

That conversion isn’t something you can reasonably do on a phone with a dead PC in front of you. So if your goal is Windows, raw writing is a dead end.

There are two routes that do work, and BootForge covers both. Pick by what you want the drive to be:

  • Just a Windows installer, nothing else → the dedicated installer mode below. It’s the simpler boot experience: the PC boots straight into Windows Setup.
  • Windows plus other tools on one stick (a Linux live image, a rescue toolkit) → the Ventoy route further down.

Route 1: the dedicated Windows installer mode

Since version 0.1.9, BootForge can build a purpose-made Windows installer drive. It does from your phone what desktop tools like Rufus do from a PC: formats the drive with the standard layout Windows setup media uses (GPT with a FAT32 partition), copies the ISO’s files across, and splits the one file that’s too large for FAT32 into parts Windows Setup understands. Microsoft’s official ISO goes in unmodified, and nothing needs converting on your side.

Two things to know before choosing it:

  • It’s for UEFI machines. There is no Legacy/CSM support in this mode. In practice that’s any PC that meets Windows 11’s own requirements, but if you’re targeting an older BIOS-only machine, use the Ventoy route instead.
  • One drive, one job. Like any installer stick, the whole drive becomes Windows setup media. If you want other systems alongside it, that’s what the Ventoy route is for.

The flow in the app: pick the Windows ISO (from the Home screen or Tools), and when BootForge recognizes it as a Windows installer image it offers the installer drive route. Confirm the erase warning, and it formats, copies, splits, and then verifies every file it wrote before reporting the drive done and safe to unplug.

Route 2: a Ventoy drive

Ventoy uses a different model. Rather than writing one image across the whole drive, it installs a small bootloader once and leaves the rest of the stick as ordinary storage. After that, adding an operating system means copying its ISO file onto the drive like any other file. When you boot, Ventoy shows a menu of every ISO it finds and you choose one.

This solves the Windows problem in two ways:

  • No conversion. Ventoy boots the ISO file as it is, so Microsoft’s official ISO works unmodified.
  • No 4 GB file limit. Ventoy’s storage partition is exFAT by default, so the large install.wim file inside a modern Windows ISO copies across without complaint. This is the step that breaks the older “format as FAT32 and extract the ISO” advice you’ll find in a lot of guides.

There’s a useful side effect. Because the drive stays a normal storage device, a Linux live image or a rescue tool can sit on the same stick as Windows, and you pick between them at boot.

BootForge does this Ventoy setup from your phone. If you only need a single Linux ISO and nothing else, you don’t need either Windows route: BootForge writes single Linux ISOs directly, and so does the open-source EtchDroid.

What you need

  • An Android phone or tablet with USB OTG support, which most have.
  • A USB-OTG adapter matching your phone’s port, plus the USB drive itself.
  • A USB drive of 16 GB or larger. Everything on it will be erased.
  • An internet connection to download the Windows ISO, which is roughly 6 GB. Use Wi-Fi.
  • A valid Windows licence for the machine you’re installing on. BootForge doesn’t provide Windows or a product key.

The steps

Step 1 is the same for both routes. Steps 2 and 3 describe the Ventoy route; on the installer route the app’s single build flow replaces them, as described above.

1. Download the ISO from Microsoft

Get the ISO from Microsoft’s official download page: microsoft.com/software-download/windows11. Choose the “disk image (ISO)” option, pick your language, and save the file to your phone.

Download it from Microsoft and nowhere else. ISOs from third-party mirrors and file-sharing sites are a well known route for tampered installers, and you have no practical way to tell from the outside.

2. Prepare the drive

Connect the USB drive to your phone through the OTG adapter and prepare it in BootForge. This writes the Ventoy bootloader and sets up the storage partition. See Preparing a drive for the full walkthrough.

This erases the drive completely, so move anything you care about off it first.

3. Copy the ISO onto the drive

Once the drive is prepared, add the Windows ISO to it. There is no writing or flashing step here, it is a straight file copy, which is why it takes a while for a file this size. See Copying images to the drive.

4. Boot the PC from it

Plug the drive into the target machine, power it on, and press its boot-menu key. The key varies by manufacturer and BootForge has an offline list of them under Tools → Boot menu keys, also documented in Boot menu keys. Choose the USB drive. On a Ventoy drive, pick the Windows ISO from the Ventoy menu; on an installer drive, Windows Setup starts directly.

From there, Windows setup runs as it would from any installation media.

Secure Boot on the Ventoy route: what you’ll see the first time

This section applies to the Ventoy route, where the drive boots Ventoy before it boots Windows.

On a machine with Secure Boot enabled, the first boot from a Ventoy drive usually shows a blue MokManager screen rather than the menu you expected. This is expected, not a failure. Enroll the key it offers and reboot, and the Ventoy menu will appear with Secure Boot still switched on. You only do this once per computer.

Some points worth knowing:

  • Certain machines also need Allow Microsoft 3rd Party UEFI CA enabled in firmware setup before Ventoy will boot.
  • Recent Ventoy versions require enrolling an additional key relating to the UEFI CA 2023 certificate change.
  • If you get an error screen instead of MokManager, that machine isn’t compatible with the enrollment route and you’ll need to turn Secure Boot off in firmware setup.
  • By default Ventoy does not enforce Secure Boot checks on the images it boots, which is what allows unsigned ISOs to run. That is a deliberate design decision by the Ventoy project. If it matters to you, Ventoy’s own Secure Boot documentation covers enforcing the policy instead.

Troubleshooting boot problems covers the rest.

Windows 11 has its own hardware requirements

Getting the installer to boot and getting Windows 11 to install are two separate hurdles. Setup runs its own hardware check, and on older machines it may stop with “This PC can’t run Windows 11” because of TPM 2.0, Secure Boot or an unsupported processor.

That check comes from Microsoft’s installer, not from your drive or from BootForge, and no USB tool changes the outcome. Microsoft publishes the current requirements at microsoft.com/windows/windows-11-specifications. If your hardware doesn’t meet them, Windows 10 or a Linux distribution may be the more practical destination for that machine.

What can still go wrong

Being straight with you about the failure modes, because there are a few:

  • Phone side. Not every phone supplies enough power over OTG for every drive, and some cheap adapters are unreliable. If the drive isn’t detected, the adapter is the first thing to swap.
  • Drive side. Large or slow drives can take a long time for a 6 GB copy. USB hubs make this worse.
  • PC side. Whether any given machine boots from USB depends on its firmware, its boot order, and its Secure Boot configuration. Some older machines need Legacy/CSM mode.
  • The drive gets erased. Preparing a drive destroys everything on it. Check twice that you’ve selected the drive you meant to.

None of this is specific to doing it from a phone. The same variables apply when you build the stick on a desktop.

BootForge is an independent application. It is not affiliated with or endorsed by the Ventoy project, and it uses Ventoy under that project’s licence.

Microsoft, Windows and the Windows logo are trademarks of Microsoft Corporation. BootForge does not distribute Windows, does not supply product keys, and links only to Microsoft’s official download page. Installing and activating Windows remains subject to your licence with Microsoft.

BootForge is available for Android and macOS. There is no iPhone version yet. If you have a Mac to hand, Ventoy on macOS covers building the drive there instead.