guidox / PC
Run **RecoveryDrive.exe**, tick **Back up system files to the recovery drive**, then boot from it once to prove it works. A 16 GB stick is the practical minimum.
The tool reformats the stick completely. Confirm the drive letter and the size before you start, because everything on it is lost.
Get-Volume | Where-Object DriveType -eq 'Removable' | Select-Object DriveLetter,FileSystemLabel,FileSystem,Size,SizeRemaining
Get-Disk | Where-Object BusType -eq 'USB' | Select-Object Number,FriendlyName,Size,PartitionStyle
reagentc /info**RecoveryDrive.exe** is the supported path and it writes a UEFI-bootable FAT32 partition automatically. Manual copies of the recovery folder are not bootable on their own.
Start-Process RecoveryDrive.exe
# tick 'Back up system files to the recovery drive'
# select the USB stick > Next > Create
Get-Process RecoveryDrive -ErrorAction SilentlyContinue | Select-Object Id,NameWith the backup, the drive can reinstall Windows and includes the recovery image. Without it, the drive only offers the repair tools and needs an installation source.
Get-Partition -DiskNumber (Get-Disk | Where-Object BusType -eq 'USB').Number | Select-Object PartitionNumber,DriveLetter,Size,Type
Get-ChildItem "R:\sources" -ErrorAction SilentlyContinue | Select-Object Name,Length
Get-ChildItem "R:\Recovery\WindowsRE" -ErrorAction SilentlyContinue | Select-Object Name,LengthA drive that shows files but does not boot usually lacks the EFI boot folder. Checking the layout takes a second and saves a failed recovery.
Get-ChildItem R:\ -Force | Select-Object Name,Mode
Test-Path R:\EFI\Boot\bootx64.efi
Test-Path R:\bootmgr
Get-Volume -DriveLetter R | Select-Object FileSystem,DriveType,SizeThe only real test is a boot. Use the firmware boot menu, not a Windows restart, so you prove the stick itself is bootable.
# shut down, power on, press the boot menu key (F12, F11 or Esc)
# select the UEFI entry for the USB stick
# confirm the recovery menu appears, then exit without changing anything
Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersionA recovery drive is only useful if it is findable and current. Recreate it after each feature update, because the recovery image belongs to a specific build.
Set-Volume -DriveLetter R -NewFileSystemLabel 'RECOVERY-24H2'
Get-Volume -DriveLetter R | Select-Object FileSystemLabel,Size,SizeRemaining
Get-CimInstance Win32_OperatingSystem | Select-Object Version,BuildNumberWith system files the image needs more than 8 GB. Use a 16 GB stick, or skip the system files and keep only the repair tools.
Secure Boot or the firmware needs the UEFI entry, not the legacy one. Enable USB boot in the firmware setup.
The EFI files are missing or the stick is FAT32 with a broken boot record. Recreate it with the same tool; do not copy files by hand.
It needs an elevated session and a mounted recovery image. Check reagentc /info, then run the tool as administrator.
No. It contains the recovery environment and optionally a system image, not a full setup with all editions.
It is formatted for the recovery layout. Adding files is possible but can break the boot if you move the existing folders.
After every feature update. An old recovery image may not match the current build.
Format the stick with diskpart or Disk Management to get the full capacity back; the recovery layout uses only part of it.
Free · no account needed · tracks your progress