-----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/jalu9uZGunHyUIFAmkwG/8ACgkQu9uZGunH
yUIQbhAAuBs2VAeWLzAHTSrEUHNPR+/R8SQW3hpDkgsXYzP2mKCRuLU56WWuC+X1
5EakejBDPJUruS/5u75tmDNMg1y9oCe0t2mBIksbIoyh/hqIBlyX+3oYjyRwFYIc
jgQDJ2amXMj2yot3Dym0Wwl0/LainA9x6ouz0M92u2lI7n2EY+JsPYglAZt8i3I6
N7w59acrjUcj17wMYOYdslJx/vlDmfn/uldToDwaawUABsLJWk1jLm4wWRiANJMs
wujS+2YnS1OdIUZAKCFi8XOBanZQj0e+yJnGhecjCOWjlWquK8C1eY5ydiKNq+FN
78gwME5SuGtq6U0IOGfYt7t1FgIvRFacvgK/EpnM4Fu6vVQoFO4ENO+Gajrqh5CP
nTO/fVl+/Zx9X9rLDBwsbzICpR/hTn0ABpvmPpP+/iWObndm6oFOCXfXH8qx7NQX
grYA50oSajh7qZHCUzP23dPdOSUi/kGHya9ycEDTNclSOaAIPUgDQGX6us1dRufP
FfidlDpOWmUjyddlwee23ybiA13ygRmZn6p1oZvzQqK8IwWSY7b0mbmQ5GuY7FmV
Q0enk9AsdPLLN4m1AnLx9iGbtxxQwpTOv6b9f4JGx4WWg1a+peJ1votnSWT5vB+1
4g9t4CuuCd68JOMxhsXd0IPycjWztC+AUwfyOOCFHnoC9UVDGv4=
=ILMO
-----END PGP SIGNATURE-----