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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmqk4A4ACgkQu9uZGunH
yUICTxAAudkxBkVdWtz2uRE1Qk88tmTYCJT8R/ob2ZTzXnwxDTELLTs9w11qnMwJ
p6/W6kAuF1Jl2Wjc5fMStSNcNwODusQI/FxUi1q3SQeoT9YKiIuGDnr1JFOyk3Yh
/jfYlP5r2UxHhVs5KjbjCAsYF7uucQz9h5RsbH8oMwEkmc3NW4AtzEzLSk3sYBfg
slquhSEQCf9mK87zMdP25SfiwHcclyeAo49DlDGYdKOh3QX2SgBjJMc++6jT7Lsn
FFNrPUcpo9tQd53mE7heQt+JATXEjrcoI6rLTP8IeoNZBLLnZIizrZSFAFhofNH8
d5ltyiuh/7oJVbhYH9f0OsWR300hm4eXLDRgpX5osYWGCa8Q/0WC9vqSBxoOASil
LaMLZUx/4ul52DoruMlJTj1Y+ChuW1V5k8TtSVNuApnMvwN2t7cDuK55YIj0ghlK
h12sQQS7KWTWtmxRypQLSAsubdqhMqyVP1POWPH3idTx7V9U5b0OajpxUbfCwTja
0In6kCVulF8N9ikaU9INrnRoXW/hgdXRI2v45LIiKUhyyIC6g2M65yER1H9RQjHP
tkmXWZ48dEi0DVYlfy+v33rWwXcPURrXBsXHbjBTUDZ6E+KlHT9EkSNVVcwpMLe4
aU+oEtvZaBAvcevrK3NLdwe8jPPpHSaeNLSTXizScn0kuO0qITk=
=eeIs
-----END PGP SIGNATURE-----