-----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/jalu9uZGunHyUIFAmkmJGIACgkQu9uZGunH
yUIAiQ//dE1l5D47/nvUhSw0LNSAuLg2zYAvX26ugSBJ6uzXlGHZqxV428myZI3o
OMcQS5vD5dzVMVy/kbbUK64VLOS9iukWpmZrer62naq4TYoj6PHW9DNm4FL4M3HU
78erZGJRkOzI7IxF9vOBj5kvUVGOAGCwXYOMm8Xaasgl4o7IfgeSzi1SPxNiYZf0
l6scYiPtPt1lBWXOqwlXJeNoPV41nrojMXt0k4+u1cMHv0P7OUcLhbBzzPjpYa+0
jmZQHV0mxwJ2SzqW8I92XYUlLCZka5V/O9hT5sIY71CEuoAgfTJZxL1f+VOHK62s
g4bmLv155LwltRVzM45BSvx5AXbgR6XsF5JGe+UAZUbqDVlJSpv00vGrE6l+wtIF
61K+4TLbUonpHsJ+34q9qCWUipzr8q5CSNTW2qXxZyEkoWN5V9iMOWisfESaK69o
uyN6HrWaQhUl/a9IMoKpGv5dlVOSN+tZl7KcTAGZUSQwSMEF2n593SBS/MMT6KSc
InTFtjpkuw83h8oGb9nzJU/Ba4hE6nKpYT8iWXfhj+FBKKPt+M7nxXp6ffMAnNpR
FmbKW++q6sp3WrJ9FKt092BB2+b7XmlN2WNiiHZAitOgTbmtHmPd40m78rdyv+9W
ZBi32MFuPJYh2H96uy5kw+V894y9lQA90dKO380fQw03aKYFHvc=
=30JJ
-----END PGP SIGNATURE-----