-----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/jalu9uZGunHyUIFAmnG7hYACgkQu9uZGunH
yUJsYRAAuZVJjRTlwv4i/poASE2TCq+enLKdes01uNGBn+jgkIRjpcuU1gKF8cFU
6fIuXYn4aqjKMMVDo4rffXwvYcCq+QPJbS316/0OlnDSdOn5Ybmyw18Nmq8dDufT
TXotPRq7x6Ape3pTuMRc2KtfPOeO4j59gWbjvt7DYA/0jmaLghMy19PsRDaBXttI
0lN5Gb8aC+Mg52oa3TfsFtMUarg/+UEB+dD3AYnAjevBNf+X63goFDXEgmpmEGr1
aZJCkDAYCIizTpHiCMNu64kWQIVV0YleJSQgLkayS9z9aNrF3tSM+Ej+2v7g2IT2
77eBdNL9Ej4JFZ6Q5mAlVtQ4uDRGGn6vKAyAWDiKhwOTCgJvSBn9srRTsgJtyBFu
6ecZeRZ44PZDrGkOwn4nob+0CDYT1/8O80jKM/TouIBr/0wy8ZERu/l9MCDQJI9I
85EektSU5Tb6XV6rKFLGdgt860/XGWWMKXd3+Z98+SfmGCEGO1mjo9MulBr9Aec4
Hpon58sl0j91VefepQOhsey2zFf1S3/RDrpBSnhNZDm5FLSER8/xx8ez+fL1UEhA
HVFYsu1JEkY4LbGL0MUzxW33RsLe4UrbQ3UKrt9Ty/MLbsSXozZPHC9JyrOVZPd/
2A+ZXTLIDvl7yJLgXi0D9SrWszPAhdP+R4yp1tJwASG2ErCxQVs=
=Q0t4
-----END PGP SIGNATURE-----