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

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrIDq0ACgkQu9uZGunH
yUJiahAAnGN7pmnU4MmDIvS+ighKuECkOFrk2sZx5q9bH9v11ejhQiJqNNvVzvk8
Ym6idO5FR10istM1pHxh32o3KYeqMO0rdGRZoCWAi//8K4BuVRAgfdfW5KSKW4t1
meZ5tdt0LW2D/hS7SEZjiX/d3P88/A9g6GA7kqCLU5QFx8BR9nMPFUUA9ZLzgtIv
9nUW8FlnJjEXz2veXDcxd4A4oMhdbEYoBFAOWBOB62IoPANUoP70/Qk6/QfRbzmf
VpKWh/eFyK3zSl8LvjUOl33EtjZWc36kV4LooBr2yVqQY6UUZOVgvrN2OElleeYc
kdXmF7BLDB86oDtsZ0AETd0RgWE2hxeoiwh0wTZ7/nIl7jzTzmE/9QwYXrSXEJLp
ihd9UDSOZpouQNCW30YD4TKpRw8IuUbGg7HsBGgQzTYk9SPBjHPBcCsqbOUfXoUe
6+X517DJxBPfvv1bqD1Qe2hx8w6OBLmyY5x7SlGHoqgeFo+67vvTpAnn5GLvd4rN
r3WG/VXXhT3wqTV41QrkLsU2niEJKnRCLjrd9kySQP12KoJ6jPLkKKzRFwE7uhNj
qrQyW5sfR5QtplwsEIJCpkI5n8IP/jUleSpBFRO42AqWNF4O9MWL6edYT9YTCyCB
7R4BBNFTGEn7IS0+I13geEeTPctbIHsgo76p4qktoRTnXolKHW8=
=qDG+
-----END PGP SIGNATURE-----