-----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/jalu9uZGunHyUIFAmknaBwACgkQu9uZGunH
yUK6jhAArgcWFIun1X1DYRTYQXvdvf78tybrHhfHQ10+tCIq7OhqCsEmcp5nHMjI
DX25wWCcjBzUEANtjudcFneN5MwH1HwEANE/VWD9S+oUl5f3nJwAuJjCTlSrbmJF
HjRIZaMmN2PwUfLqKfur+xEp/DKdf966kvGNAXHY+HeAraXCd6r6NBAk0YdxJveT
BDV8rZNMaEjoFvki+ErMAcQC3fLo5desUE4jX68Gn/3Sxmh8CHInK1a33oeDRGXP
nV7kkqK7wt8N3a+Ge3efBZDjPWYQZ6oDTEdwh3I4OAcrye0SLHEi5HWxZ20c7yF2
oB7gL0cZ70utiUKSjG9aXTpEqsYP9tipwQ3szLFmNGjI+1v+4WbL/mMxxf1tQ8Vz
pp/jzxrnj56MUZczKJZXHFZH9EqPuEHDmx4gwghmd5cj2JX+zg7AS8LLfCLMkcmU
KOFVP83495BS3dgLn4fcA61DNhj9DmInnUCLDvSGBf4qXNBAFgofqv+5l4+dAnFO
8guE0WjWY8tL7+jOhV0f1s2pUR5M7hZJEy1KlKZZg6jql+NlxuTUeez91ChlTgBo
n0+OPm8eSqEcA7GFHo+yXSm+GgPhgDTwKrekZ9wjDyofQ1BIxutnts5VntmT2GuP
zACcQ29m8rTfvnII9BAGqvUpdQKHa8n1ftuWPX2yr/7ODeJLRg8=
=QA24
-----END PGP SIGNATURE-----