Checksums · read-back · Windows media
What Bootable verifies
Bootable checks the source and written drive separately.
1. Check the download
Bootable uses the strongest available publisher checksum: SHA-512, SHA-256, SHA-1, or MD5. A mismatch blocks writing.
Without a publisher checksum, the download is labeled HTTPS-only.
2. Check a raw write
Bootable reads back the written range and compares SHA-256 with the source.
For compressed files, it compares the expanded image bytes.
3. Check Windows media
Bootable checks the source before erasure. After copying, it checks the UEFI files, setup payload, split WIM parts, and FAT32 limits.
What these checks do not prove
- Installation will finish.
- The image supports every computer or firmware version.
- The publisher checksum itself is trustworthy.
- Unused drive space is valid.
Do not use a drive that failed verification. Rewrite the full image.
Developer boot test
The repository includes a read-only QEMU/OVMF test. It checks that firmware reaches a loader frame. It does not test installation.