-----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/jalu9uZGunHyUIFAmm4C04ACgkQu9uZGunH
yUJwIBAAor+IWMK5Szo7gMsTWNFn0lg6ITc6E5NbsW5GlEeN576X7gd2vg5AsVPK
ZearP0VpxrPr6+936he0oOwLIJRax3bfHsg7qe1DFPscc+U1tGqYvjVHr+9CP1P8
cT5AWhMsq0xZO3Vz5L6wSxB1Sq8AHSdXsgVsLpgUJ1IyhbH0heegrVF3KdL5I8p+
fl//hf4H9gbHOgpk2mT79Hqw13+8KBMBEWAyNa1MLG4KNTc0Kv0aaOQ8F4aF9Qlm
1EHD9zgO9+wO+2Bm6hZK608vo+9PKjEGXI94X2TJSK4VYWd2X8WCuPJcE5ZgJvAA
PGuyQmGKCNvNJxvkpNMO6/EBkmO7Y4uDhYfHjHqh57oQ5Llh04PqyRjrNf6R+sr6
sumxDn0IaD/Euy/TB/vuW9lCPXv2Zl+fxAnaWdrtBLrL1cUwUZQzX0eBVeq5K4XL
Erkt5K9XxJid2XigqkYDKguK7TxUHCgR+uz1JxQAhv+Et3w3g9eZ+Ms0LIt4ntR5
rqI+OZbiCJgpTcnEk/taxC9aJ7ePqQwiQMN8I9pnC6dkYhpSAh8BMd12oA8nW5Gb
QEODocoGAEr/v305FylQ7+iJOw8MX7swWnON+jbqiTv5JOEGNO3dD6uSILjd4xPZ
qR74nNNHag8oBJTVo+e3rXKiWpWKFertteofc6kr/+yyeg8vbs4=
=qHbx
-----END PGP SIGNATURE-----