-----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/jalu9uZGunHyUIFAmnz/ScACgkQu9uZGunH
yUKkPw/+PrfHgQDNgpaWiNZx19bzlXU9JsB5AST5TJ5b63woWbT8PljMjRrGKNyp
tsfpSNFE+QD0+rgUEj3GLbcRkorr89EIsRThY98rVxFcpXTZdYBRiGXH3Y5qqzLo
BmCmX7cDoUB3lTwXvKcz9Haq6f1n+LwcPFSRdma0KKbBnuB9ph+WGZ9M57KoxkP1
s5cnPykMTEje+gi1eT4Iq4YhwXB12u/KJjwEBLezL2fA7JuLigy4RPbOH6AeKgJ1
wCX8IcXUiGtQSdflui251tED/8FNLu2Pz2VJzj0nkdNNcJMFlf61vEJVA8F1nrQs
3I+uclLxb6ad6uTKOS2ii39dQsFf2Sl28UjaFGlBSufAlVprNg+EoOpwJ86Jt1z7
/2oRNtfxpPnqfnbKCNW8IhaJnfE5CkGD3YkLR01gRlsbdH8yNVv9S8D0azf54gm8
O7/YQbIPk6e0UO1kDVXEvm7NlOZuqwUjXMp9DX//ixetjCVcc6MOEUUSeX60YhBG
zg56dUD0CQJlEiMudfskfAZdcNAdNbQId7FLpNw/Y/qAamxr3bRC6MySXoU0dQP/
maiVru5lmqG2xVvGW04G5cqszQbGwOIvT6EGMp7N1ntmZ5tX0pNXM92zdIPJSAW9
Nmq/JdAvk+q+jLWPoXbdyG9Wc1sMo0Rvb48Tq5fKawJ/mScn/ZA=
=TNHR
-----END PGP SIGNATURE-----