A match before you play.

On Windows

1. Open PowerShell in the folder containing your file.
2. Run this command, replacing the example filename. Keep single quotes around the filename.
3. Compare the entire SHA-256 with the value for that exact file and version. Letter case does not matter. If it differs, stop.

Get-FileHash -LiteralPath 'your-source-file.ext' -Algorithm SHA256

This reads the file without changing it. Repeat for the extracted patch and, if published, patched output. Compare each with its own labeled checksum. Hash the file itself, not its ZIP archive, unless an archive checksum is specifically labeled.

Use the header/container form named in the release. A match establishes file identity, not ownership, translation quality, safety or gameplay. No approved game source identifiers are published here yet.

Microsoft’s Get-FileHash documentation

Something doesn’t match?

Wrong source checksum

Recheck platform, region, revision, size and required header/container form. A filename is not proof. Don’t edit bytes to make a checksum match.

Wrong patch checksum

Check that you hashed the extracted patch, not its archive. Download that version again from the release link. If it still differs, stop.

Patcher rejects the input

Confirm tool version, source form and patch version. Start from the untouched original; don’t patch an already patched file or force a source mismatch.

Output checksum differs

Keep it separate and don’t treat it as verified. Recheck inputs, options and patch order.

Correct files, but the game fails

Match the published emulator/core version, machine and region settings. Disable undocumented cheats or automatic patches. Use the documented boot sequence instead of an old save state.

Public reporting is closed for now. Keep error messages and non-sensitive setup details locally. Do not send ROMs, disk images, firmware or private logs.