-----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/jalu9uZGunHyUIFAmoTjLoACgkQu9uZGunH
yUJQYw/+OvsbT+l6Uj60M++0t1sEdVkbtKlrAw/Q1DU4GbAtvmpJ/H0mZJ2UzYkt
5AgcAAn13SKufxkcgMeq/MrP6aX6CNpuJuPWTq0PTvHauNL5CwV5BwR5D/YkuU+a
a3vDlcnB0yjUPtamcPBd9nwyfpYHZ4vDHN/B8sBiyQLmWxaKTI+V1Gvfz8VWK6rm
xxjwtD/xMrVUFUllfcYb6hT2cXl4gM6euLWLMoYktxmOMezc/aT2pYjaDY9vlZpX
FaH6jNbQodU7rG6xWPvlFbwaK3ysr52MUqAcz1n4NdHde+WRV8qJdA2Fe6+2375T
Mu16BbkU10zHdTb412nVyp7344SBa/5BVs2noYhaaO9xsqXtu07xfvqdWKPq/A/5
HxN/bH7b8L/9g06AXcG0j6oEJjSGT3+nW5/i80cvbZfaA4jLXvUp0vq3hDyqO22l
2AmVnHQVKq4xK9I8zyj78ZrWPgvcchY+dIEcAYbiR7bUhuebKuG7cpVSN7d6OxHR
JFuMMci9hzYcH8CTsuOrcNt8hKiCBztQnTbCCIR6P0+joi9qvn3bulx1j/0dwrym
l5JNa4tIjublI6boRId7rzgPaPF+UejrfVma32e/cEdZWs/O42g/L7E4+YQXtUgq
kOKSfm4pDmK+as+qLNoAUp4FbjU0wZkV8mDVKnV8D63zN6/X+Sw=
=BeMX
-----END PGP SIGNATURE-----