Create and verify SteamOS recovery media

Use only the current image linked by Valve. This procedure writes an image to an entire removable drive; it does not copy the compressed file onto an existing filesystem.

Every partition and file on the selected target is overwritten. Disconnect unrelated external drives, back up the USB device, and stop if its model or capacity does not match the device in your hand.

Scope

Valve currently calls for an 8 GB or larger USB drive. Rufus is the documented Windows path; balenaEtcher or a bzcat/dd pipeline is the documented macOS/Linux path. The command-line procedure below adds target identification, an explicit confirmation gate, and byte verification.

Data-loss boundary

The source image is read-only. The target is destructive. Never substitute a partition such as /dev/...1; write only after confirming the whole removable device through a stable /dev/disk/by-id/ link.

Download and preflight

  1. Open Valve's current installation or recovery page and follow its recovery-image link.
  2. Connect one empty 8 GB or larger USB drive directly where practical.
  3. Disconnect other removable disks and close applications using the target.
  4. Keep the device on reliable power during writing and recovery.
  5. Record the downloaded filename and date; Valve can replace the image behind its support flow.

Identify the Linux target

This command is read-only:

Find the corresponding stable link and inspect where it resolves:

The model and size must match the USB device. Unmount any listed target partitions using your desktop's eject/unmount action. Do not continue while a target partition has a mount point.

Write on Linux with bzcat and dd

Set the image path, print the target again, and require a literal confirmation:

Do not unplug the drive until both commands return. A short or decompression error means the media is not ready.

Verify the written bytes

The following reads the decompressed image and the same number of bytes back from the target. The two hashes must match:

This verifies the write against your local download. It does not authenticate that download without a trusted expected checksum from Valve.

Use balenaEtcher on Linux or macOS

  1. Select the downloaded compressed recovery image.
  2. Select the removable drive by matching capacity and model.
  3. Review the source and target one final time, then flash.
  4. Let Etcher finish its validation step before ejecting the drive.

Do not accept a target you cannot distinguish from internal storage.

Use Rufus on Windows

  1. Obtain Rufus from its official project channel and run it with the required privileges.
  2. Select the exact removable device and the downloaded recovery image.
  3. Confirm the destructive warning only after rechecking the target capacity.
  4. Wait for completion, then use Windows safe removal.

If Rufus asks how to write a hybrid image, follow the current Valve page rather than an old screenshot. Rufus releases and prompts change.

Ventoy status

Ventoy's upstream documentation says installing Ventoy erases the USB and then allows supported image files to be copied to its data partition. Valve does not list Ventoy in the current SteamOS recovery procedure. This handbook therefore does not recommend it as the primary path and has not marked it physically validated.

Boot and recovery verification

  1. Fully shut down the target device.
  2. Open its documented UEFI boot manager and select the recovery USB.
  3. Confirm that the recovery environment reaches its desktop before choosing any repair action.
  4. Recheck the device model and the exact recovery choices; their data-loss behavior differs.

Booting the environment verifies more than a successful write, but only a completed device-specific recovery test validates the whole path.

Rollback

Writing recovery media does not change the SteamOS device until a recovery action is selected. If verification fails, stop, safely remove the USB, redownload from Valve, and write a different known-good drive. Do not compensate by erasing the internal SSD.

Known issues

  • USB firmware, ports, hubs, UEFI settings, and damaged flash media can prevent a byte-correct image from booting.
  • An 8 GB label is nominal capacity; use a larger drive if the current image does not fit.
  • This project tested the compressed-image pipeline against a regular-file target, not a physical USB or Steam Deck boot sequence.

Frequently asked questions

Does a locally calculated image hash prove the download is authentic?
Does a locally calculated image hash prove the download is authentic?
No. It can prove that the bytes read back from the USB match the downloaded file, but authentication requires an expected checksum or signature published through a trusted Valve channel.
Can I reuse a Ventoy drive for SteamOS recovery?
Can I reuse a Ventoy drive for SteamOS recovery?
Ventoy supports many generic image formats, but Valve currently recommends Rufus on Windows and balenaEtcher or bzcat with dd on Linux/macOS. Treat Ventoy as unvalidated for this workflow unless you test the exact image and device.

Sources

Version history

  • 2026-07-15: Phase 3 reviewed procedure; Linux write pipeline simulated with a regular-file target and byte comparison.