-----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/jalu9uZGunHyUIFAmo4TlkACgkQu9uZGunH
yUKgVBAAkfDpFzAVbzVAOnZiY6Wtf+qOjMnBkgUFjFTE+Zb3Efy/0YngrXv8Z7JP
3D5UzaejrpqwE6vncrjR2sOZ63p2hkNSA/+yJkkJyXTzpKQc4RI5p2Zvu1gHuIj8
EI3owf8/JulFiuGJfmrqsfCxmxluuxV8vhsfPkLRbO7ZUuncCIRRPnf8JKXQ28oD
VLI0MfREnUflvzk3U0Isg5oNr49pGk7701m8zaN+LtAYLohRKV7ZgtAjay6tBiMF
dVX56x/jOoA2IgCxInYugSr54R1elkWk5YAq+0Okjl4bnxNvVJKAjIIDl2aAJh2V
o6tNwDvYl/Mw3VxNRCTZwXhlXfS37IWPAPVb1tGOfI6YuUwX+b3kitbLqeofOGxJ
hcuRoGLyq4uRM9ojpNuUFbDVsVY6BHFOxon5W5gF19tGrgqvZtAZc16Z5NLOPfAi
LQ3UUEIhae75rqBsajEjrFEwF8ETwPL6pQ1zAn+tWzK8dT8cwVER0fP0Thv+4DGm
gyLwUss1uDf11zHM5+Uu4/SUPuaG6fT+85VONqIJb0l6BllSk1LhG3y2yU9BF/WY
Xy5EC9xmjBajgSfIbM53ZnUO/wOqU2DyALxAwPHaQjYBgJDEZv8aCFfnTM4jPSdS
tUl22ZsD6nl3d0LMRlKGkJkVixnqWYie+pE3BK33hLZ/eAanKOU=
=K2s+
-----END PGP SIGNATURE-----