-----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/jalu9uZGunHyUIFAmkzn4MACgkQu9uZGunH
yULLpxAAnuuNcwRM3/0Rkn+3vBGp5R3vAKOvzzUNrNB8uOP5y4dBefc9l1OjchnL
uJSZc5ha7JwFbxYP9EyhJaaNBnDi2s0mka5TvumdOH82penXbOy/AYRWDgpRcwF4
bo3zJKRbPxOhIAhFOfE8iPOKho5xvq1tvSLYZXvf1kVlHsheStxSJ9JyMGJDowQ/
8u3yg6mR4Fp1fOGkatwIyDlqJ+HQolPMHz56Eymz+RBjkJMYhIUghqoAfRYuqTG9
tdupn9NXrUlyigIigQV0caTJ6fx/xyAH2H6/8p2RLFcEh262O48Xugcx47LeHENI
XJcJLJEY5M5HI/VRnDqnCgehcYlt6/aKdwh9G7abrJBPcTCA2qYPD8z+CeiOrQvi
b2FwjZZLvKcnlCHePnAAOfGH3s8idNdQHzKzv3DXE+pNGuQ6qjAMkCqTg9StBUQj
E1YRfbQSypfVZhGThkm7+M1vfQOghGqfdq75yCqx9DcfeOw5rE2bKvR97jDkgU12
JcAItG1YC50+lDmUK4mS4ti1HxDqdH7BDqibpleWM5ilYixxArVvpyYTLYe0SiZk
8CUjuah+KO4cXKuOT3WPbLtr90P1oOKsLstF9zOftE1aBIgNws2PfHFZIYnestfy
rIL6xOOg0x61dVDm0CicTaSFnICS8fOpyyaYoM7WDTbCD3EM7FE=
=u8VD
-----END PGP SIGNATURE-----