-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmlfvZgACgkQu9uZGunH
yULCWQ//fiw7tHZM6eeXwX9SXWCFRZMkmNF88hTmt0aCH0mxhsGC5TLwa9Kv8u0w
ctuKD5h83GV8U6xwDMroGh2SYDSbgis+xgfs+QO1KHqziXR3C4FJT6imYYA4baBM
tXAcS7cZYzyFeftvXSwSUcPIomw/baiTvvO2q0+ecDDcT/EJV+GMuMVmSQ+RyEDh
mN9ak4Y41Qcy0KyE08THFlaJOxqLSi4NhExPa7laQPhuzxTk/FmrlYi4wkNEF7go
VtKrYjm6//571vuUU7vNPUZtE6d3kEOcjr6qbmhSEAQOQLx+4YRHqNx8lnRwxlQ2
tlJdjoNPEnugaLV5Eobg5PZMGVydmgjCfoOpjEEaqRkNFQxLKMd2qOcXwDHcswhw
g7DOaCJaAALGL6J/qNUQUzXdb54Id7erf4x9+FHq6kPVnX7gDFsyXICQCBshADO1
qd2yu64ZU4Ftvl+mHejj2njYV73hf7QV9pLqY5pDxzaftpcA8kt5Uf+YkkzCtfGP
PfGTViyu+WidrG0opcwYGJzJ23dB0dAP8LPR4ss8te2Ci/uSdH2mCBzkSApReYL2
5tEaVK3Jk5aVTNvRahxlXLP+LJ7/y2YjUOo6UIWwDjgQDgcTYMqf2qZLwVMQNQ1R
UQEpjGX8KHyO4H384XhkHtQTmO7wsib1OhtEgPB3e50sFDvVFds=
=fKFg
-----END PGP SIGNATURE-----