-----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/jalu9uZGunHyUIFAmkxeawACgkQu9uZGunH
yUJUeA/9EC1Os5rKeuNPNlwAX3899jKv/lER/WtkDGAM43phARLSTsgjJ97YFPHs
3fl+l+bAm0/MOgNZjva//TPtNcnw0kCF0FzPyA89U6disV0Bc5+6F6v6NmG/X/gt
Kg8gc/IODkCWYDZk2Oq9wMnIQbSL+RUmDrVXJSZJs2xFWzGwQnZMwyH+rZ3gQ8V+
K0zel4x8QN+a1sTgyNnLBgyPI4ycrzat8OHlan111RIqppjIkGq7jq0vPLXcij9L
oCkXMyA5TMNXl7gh41FLHx2y99guDPjBuJT72sRSosNtH5UBprXHZMEuH+ALngoS
HhY7cuXHY2Uw4UB0uMGv0TJZz0zc/vC3sD9EDSChNJ8tArmzIcVbYPSzA0uroH3p
g0cr4e9gTD3K9GMEqy3qMxQBV3V615drArKph8T9qwWLgXUtUnXQDVirUGdCGu6P
BjUCpsQNdv1q9ARZ3BebHFZ+kEnBFM+lnP9Jjv7zrbeVPbUaSyrYK9LYvKhti9OY
PlsToSmZoZTFEyykbKeLBtiObD3/FFUIfSXjQG6vyBAWIaaFmx2sszsxkKUYwwuL
HOld/CAjzQLVjREULqdO8/bnMMmu+4ERCPvcwBCOqTnSo0Yw8ch9+keEjd13PHyV
DQXP6w02MLZfJixgysNoaGGp6Edsm0zTXKVPq2cvs7/pvh21gdA=
=yd2n
-----END PGP SIGNATURE-----