scorch VS HashCheck

The method I use is to run scorch every night to compute hashes for new files and check around 12% of old files for hash errors every night. Even if your backup is the same day as a ransomware attack, you will still catch it if the attack hits enough files for one to get randomly scrubbed. Also scorch is designed around making the hash database small and independent from the rest of the system, so you can automate copying it to a bunch of different places.

Lastly, you could just point scorch (https://github.com/trapexit/scorch) at your drives and run it on a cron or systemd timer - just have the script alert you with an e-mail or whatever your preferred method is. Not ideal but probably less work than rebuilding two arrays because you don't like the format of error messages.

If you really care, you can use something like scorch or file-digests to get the hashes of your files and just store that in a text file, recalculating monthly. No need to get fancy with it. Hell, write your own simple script that hashes, outputs to file, and checks previous versions.

Not exactly what you're looking for but close -> https://github.com/trapexit/scorch

Scorch should fit the bill (https://github.com/trapexit/scorch)

You can use HashCheck or similar (https://github.com/gurnec/HashCheck) to create hashes of your files and verify them. Periodically do this and if it ever fails, restore from one of the good backups.

Still better safe than sorry though, so I've been using TGRMN's ViceVersa Pro and sometimes Robocopy ever since. For easy checksum/hash gathering I use HashCheck Shell extension - but if you want to be a purist, the built-in certutil utility in modern Windows can get SHA-1 and other hash types .

Do you want to make sure it's the same file? GOG Games allows to "Verify that your collection matches" GOG Games here. To use, install Open Source HashCheck Shell Extension (old version) to compare against it.

That's good. In that case I would make at least TWO copies and verify those copies. I've been around long enough to see USB have random bit errors. I use ViceVersa Pro to copy and verify but that's overkill for your needs. You could also create a hash manifest with HashCheck Extension (Win) or the like, and diff the two manifests.

I use HashCheck: https://github.com/gurnec/HashCheck/releases/tag/v2.4.0

What I was suggesting is more subtle. There's an open source program called HashCheck https://github.com/gurnec/HashCheck I found that hooks into your Windows Explorer context menu to make viewing a checksum hash or generating a checksum file just 2-3 mouse clicks—it's actually pretty nifty as you can load the checksum file to check for data integrity across multiple files.

First verify you got from qbittorent.org and that the SHA256 matches. You can use certutil, powershell or https://github.com/gurnec/HashCheck

Not knowing how to hash check files https://github.com/gurnec/HashCheck