-----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/jalu9uZGunHyUIFAmnXebUACgkQu9uZGunH
yUKVjQ/+KyIWxafUy2VWbUaMEOXYOQESQJa+ow2f4nRFUPXMGFae331354sRT6xB
Y3+zxvG+39A6Tp65mRAO1g0gYgqq5FzzgbVRSdWVu18iOAy47Q7nav+Mu2WqAn4/
I/80+tjjFY/B9qaedNFVLW6hns+V5+N7rB5o1TlKKCFeZE2kCHNA2ss8LL2qsuE7
XngP+mteupFl5JDqboRNaOJel0/wIzRr9xhIGRPluH14dOqRgdr/3Cy7TVYNBCa/
M/S+Ozs3TeWoho8tMOs0fm8pyoFjHN3xw/f3kYT5t9oRI8Alm6exPXvK2Mtm0EBD
89mvOvfkPkkR6qPBnaD76QFrXIFx85EdxIs2zs9ZUmoLBGTlImgty4fcGswodfQi
IbXEOOZ415B5TgmMsf81K9E/FgNUR0yhxbf85xBNsQhIIYgofoctC5TgGtteabkM
FiPRwO2HUFdOggjOYYIxcjm6c9mzAFDgepvzxAIAz9kmhnusA9HVYam0tTyuuSDa
TTzbQlPo3QcLtpKxgPqPuf935j8ZgT2qbly82iA4zTGp1H8yCYF7zC7kw3w636ie
wYXkDo//ca0XOGQRX13eH6NGexjcuwQ/P54BfzwX6+hzlCcL0Qff+Ze0tGpVgJ/k
M2eipvjnBUOkSLelN+1Sd/8qYBRGP+/sCqjmoEP8yQsNKuB12EM=
=Ltdw
-----END PGP SIGNATURE-----