-----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/jalu9uZGunHyUIFAmm3jbYACgkQu9uZGunH
yUJ3MQ/+KVxEyE3xAiBHVmn2v4ZhaH8Xzezrovdm9Vi5DbRlj1rSm0enlusTuuxS
JjUHV94H1TWNToiWMTsIKRerfdpz1dspfXVOAvYo6MSWnF96OTVuCH41lb7Rc6BI
CWzdRyhcrBoBHb/RKEzA/QuYFvWEOkVvf8aa7UyVMN9oZO6cNNejmFja7BqGKcGJ
aAL5V1JAuZDuiXXTA9qDGPSVeelH27lYeghksggTgnYa2ohvWybAPhOcqPKkWsZM
Gw8/OAv0+1SqUfPAlomldY+bV6gag0XZO6yUNSi/kXymr5WwHOQWeVD2MlTkqQ0f
kfEdNpKsF5mTACuuvmU6tB70HtFcKCa2rYk9rfMDpbktI66YUOwerjyosZwXqKGE
1E9HDMYvJQb83eoUKpU9wU4UMJluWJ2BC4VW1mrEVBMhDMqe2Nb2p1DGln1Ft/c0
2CX124nJNrXl86CA7rq8/xUvrXV6RY2ns8rtrjiJfHfZ/jepOGrT0kTs9COyMrRs
Vgzvu3sVHQLSpKz30k1nerfh6SCi5EKHtUw4L4PStIWucD/m4vH6gxgAB7aRtddx
g1QE+Y5WiRri/jZEwLHfXDY8pdKJJBN00eXRCgmgrRVyJWQHjLUeugrNt5ebFHsu
XpEIkTkJOl4E0DIfjwuWTnXs2q4cDxhHrOID+R+vH/wKMuuu6/8=
=az1w
-----END PGP SIGNATURE-----