-----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/jalu9uZGunHyUIFAmj3+/EACgkQu9uZGunH
yUJQohAAqLAe0mFlwZecVcKThFFV6aZd5t9gnBSgbyOmXlRnoKIVf2MLnbyx/ZZz
b2ODjMB2R/wNYrmMQ++qb0Nuenbvr1J7sjFnocR5zOBCBN5LEIoMHCV5MgTaQRO3
To/QloGl+eGeYeEOknvp2/wuVhOKvlEQ9Yep0sWYAEAtXXH/73/9lLEppdlqm9zn
SW4PKJ6ygm+V4X28resBR84pGaYk7aJ4BkGX3gKK2g4cU2AprPiBW4tGMrGYpnY9
xq5eqSJod6NBNn+oujsGdYUQfqsE3I+vQqNWdBfn4z5CO7pQYJmVYhNKWiE3LJoo
rBv8E2W4r+PXlmujEFf+3Ee869R15WiFMTeirEHWsiRoOOXhO7L8GhpGHqze0XFh
ccJ9MY8rwJsGA4qwDNL3zuqyEP6sxkyAQ5xjBtdnwudFSBvCAcaposbb5+9j9dX5
vWx9CuuufD073RPaJ8cLiCLUD8Rgwy2r4idSexxfqes+9Sxku+h53mJ3Q/CPEoFV
Ssk0zPL5YEeh7CxU84m1RUbKnAoYz5Xt2uhEQCremc4B7dw0/zd5lzkrr86WuJyQ
f+qOmLvQUJAc+FyRpVmF0Zrhwn/l1GLC3yuRmSEuXXw30EwWGB/+PhWSL7W0p1aW
uYf9QQsjdPH2/7pmAI8iAh6mvruBgtbJsQLJZ4XXXhfuwg+D8x0=
=0Tlf
-----END PGP SIGNATURE-----