[BETA] Boot straight into MemTest86 from Windows and auto-returns to Windows after

[Chaitanya (PassMark)]

A single tool (memtest_boot.exe) that you drop next to your MemTest86 EFI binaries. It picks the one matching your machine and:

1. Auto-detects your OS disk and its EFI System Partition (ESP).
2. Auto-detects your CPU/firmware architecture and copies the matching MemTest86 EFI (BOOTX64.efi for x64, BOOTAA64.efi for ARM64, BOOTIA32.efi for 32-bit UEFI) onto the ESP.
3. Creates a MemTest86 UEFI boot entry (reusing an existing one if present).
4. Sets the one-time UEFI `BootNext` variable and reboots.

Because 'BootNext' is one-time, the firmware clears it after the next boot:

• Reboot #1 → MemTest86
• Reboot #2 → Windows (your normal boot order resumes automatically)

No USB required, no manual firmware menu, and it doesn't permanently change your boot order.

How to use:

1. Put the tool and your MemTest86 EFI file(s) together, either in the same folder, or inside an `EFI` subfolder (the tool checks `EFI\` first, then the base folder):

memtest86_self_boot

|- memtest_boot.exe
|-BOOTX64.efi (x64 machines)
|-BOOTAA64.efi (ARM64 machines)
|-BOOTIA32.efi (32-bit UEFI; rare)

or

memtest86_self_boot

|- memtest_boot.exe
|- EFI
|- BOOTX64.efi (x64 machines)
|-BOOTAA64.efi (ARM64 machines)
|-BOOTIA32.efi (32-bit UEFI; rare)

Note: You only need the `.efi` for your architecture, nevertheless the tool auto-selects it (Keeping all three is fine and makes it portable across machines.).

2. Dry run first (checks everything, changes nothing):

memtest_boot.exe -DryRun

3. When you're ready, run it for real, just double-click 'memtest_boot.exe' (it prompts for admin), or from a command prompt

4. Give it about 45-60 secs to execute and it will count down and reboots into MemTest86. When you exit MemTest / restart, you land back in Windows.

Requirements:

• Windows on a UEFI/GPT system. The tool prompts for
• *administrator* rights automatically.

Download

Note:

• This is a work in progress, NOT a finished product. Expect rough edges and please don't run it on a mission-critical machine yet.
• It modifies UEFI boot variables ('Boot####', 'BootOrder', 'BootNext') and writes a file to your EFI System Partition. These are standard operations, but firmware behavior differs between vendors.
• Always try '-DryRun' first. It's fully reversible with '-Remove', or by deleting the boot option in your firmware setup menu.

Please send feedback.