-----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/jalu9uZGunHyUIFAmnxaH0ACgkQu9uZGunH
yULcxxAAvEAIIiyUir5eYUtZiOL8DIdxooFxuiG+EJVuuakbxtjtabOWIIRnDKy9
Pqf+V6EAqXCt7kV6udkImIRwEH/5SsxaP2m36QFz/ROCq6yCAdISbjW700f5VxVN
4Pve68WYZzejwVUQiqxrpc8UaKhrWRLfOCgLta0e5EBvVffvE//uU7QiuXEy2GTl
2oF4bmcAuJJLOqujx/tqV1ed6hT6g6fqYb7P5kY8MpwLAhUW4U7sDujWGRFBXGNF
Dm4P8w38EJ3GG4paS/dqEQS+0VAGaWiO9qPd/CuVuy31P2c4NUdelveTK+wXU7PL
K6sXoiazUvZXGOnx7+ut9jceqUrUjDqSL04PpxHjuDzLT8pLyJNCzFkqdweKgWGi
s5P4gTxVsng2W0aI8YMztfv4dc5ajEUD7mzaMmcL/nf9/IQ7Z1fnWi+0XgCSXoX/
H7GrIeZGomD/IS39fWJQiicQcem9boyFP6EdXI9rKS4bbjADUVKXL/Cx2dP3zVHJ
L2Ra3BJnBy/jPhAo1BywEoPfcx4Zq3YoRQz+iFrxvNJAYwpbyngCMudKsVtrI/iN
mPCoRJ66CYblUvcRBY4Tzh0xirwhbQxy8LkNEJBtMuv9PlZKGDzljxB6hKUazvoH
hz9Qr3GWHrjnM+58qxva/diCjVp2EoM3guVo9kbkcg8y8MTEwxY=
=uxDG
-----END PGP SIGNATURE-----