md5: ee68217d5031b49319f8fcb195014761 sha1: 2a58c35bd51179df75d9ba46efbac577037dd59b sha256: dd2d9f536b5aaab87b7c38de3e4d44d5a57fe7082b1e932959ad72f4a6c8199f sha512: cfb52f7a0cb06d3cd0ced1974329e3cbe067799f9bd627c3703fcfe381f196aa4fb840471ab190271f8b9b459b4e0c0b11971aeb2b2dadc271580b7ceb9e1fd2 Use https://www.quickhash-gui.org/ to verify file integrity hashes in Windows or you can use the built-in certutil command as described on https://cryptostorm.is/windows If you're concerned about us using weak algorithms here like md5 and sha1, there's no way to collide md5 and sha1 at the same time. I.e., you could do a collision with just md5, but that would change the sha1, or vice versa. That's why you should be checking all 4 hashes, or at least the sha256/512 ones. The md5/sha1 sums are more for CRC than security.