-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
3613b1e032d878f162876e61acebe5b7
sha1:
1f3b5c0a51ab4772e8b68ed3ee25386f8fe8dc2e
sha256:
045c8b9fbbbcaaed3486f2819f9a3d9256cd75b603f6579ea1efca16f0ef6383
sha512:
d953f92481a2cbe0371f5666aaa4bff6e725234d7a5b21185fcc9596c33a4add62b09e4ce01b2f4ff87345dc3d7283056e3114ef130c7ea8af6c642ac5fcacfd

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/jalu9uZGunHyUIFAmqV89QACgkQu9uZGunH
yUKARBAApA3HGPGPi8YYZXrfyeSHk8reRsh6CCj2KA+SbaQrrwViKM98Az+fnGya
RJeVVz+nOglXNqi2QyUXUBNbf9u9cv/g7arKxdFDSzs7/WJ2yHH7xnvjy8sX24Up
Y+IiHXEXYAQPSgqDzYwCgNmGffVDmP4NmwNucJ0OlhQiYlkyP/5pXN4JEa2Uq9Re
RMFGvIz15DDy0acvWfTW+IwOANDi2HJPdONLkxnSySjgke/NzJPyLxM0GjjKxBd3
niLJJsz4PihyJq48nVZEaTh0DLx1V+ZurFTHbRcJwG4nqEddxJrVQl1AQiocgfyR
agxiwbraVHmhKmdWOsk0vLhAPfkykssgIVzFPghKWQKZusDi4CrEkm457QVMt/iY
OxmZLxpY35F7u38xbIg2+lmJX046BLEEf7yE54yJ90hRmjq3E6D5AItv4fawQSLf
Kvgj6XiM67OkZbPeG8CQ4bBvI5AIIm3DgFkPasSvaTauEygj+bq2JOSY6oL0d0/Z
9ELO59WIAYtKrksAKpBuVTF+5H1TRsDKCgWTmk++P3KKz2AuMF3B/GHjHpjV++TJ
iYe1L2MbxEg9DwO1F3VgsGc+cEsw6W0yarr3IA7o93vxKH+mtVTwMzPhav4WxDxX
WpvFBJjgE7V4KMjwENwfIjX+19xe12gp6xilgCRAKAFRZDXBBzQ=
=8iyn
-----END PGP SIGNATURE-----