-----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/jalu9uZGunHyUIFAmomZp8ACgkQu9uZGunH
yUJrAw//f7kxdWggTc3bIS+6TY8cjFRijhPoNBidyUQbWI0tvYGKCJUZQ6H5Nxbs
lOMHLD4hr46dBIHlwPPaX19xQ3tQEnLGg6H8ZDnX0WXZgSWJ3M2cP18fQJ5DYXA1
kC46SgKx05mOCgRkQklbPA//7UeMezkF6GLuQJ18y85rn8rrXV8xHZ9N0u+NcUOO
n/29Gn3Pn7vxS5xoCb8ZxQnjzv/pNQpxwQrmcv7BxXj53FzHFRZVuX510Mr5KNWt
wSLHFwF6DC61BUg+UlWC56VkkA7Lhw6TNKJ2R8sFJlFFo5LYZJF80kn4dYSctTDm
rvpoQixIuhkifM8HkaWMv/H1V3kyob+UJ5GTbTnh53tG13woFVz79h6KBOeY4JYr
rd7eIpDexLOFGBnp+wq9aWqA77UONGYGuyFYKEulWJhEhQyTl4A39fzaxSwKFr7n
KbDoyAvZ1qfbx0dYwX5cCgbCELvRjDR2cBRLZHq2/2l56XEeXOjUM8Qx98Fz4sDu
NmMKuEBN146aEVTuOr1hiHANA7JEjS1YM+RGeSVX6CBwTp0s7maF3b3OvXi+jsL6
1inYd/tnme3H5Ii2xWPuZId2GKNU12OohinVpHJm+nj8VgaGrcbRlSrVyXmcqy/H
gGtI7WkDje04B+ITBjbR+Wg65WhT+2J2Br7r8fwZGwFEL1vaUkI=
=/Ma4
-----END PGP SIGNATURE-----