-----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/jalu9uZGunHyUIFAmlsce4ACgkQu9uZGunH
yUJQCQ/+Kv7RsTVA2NCTPJlpD6mJuOCNMIEJTx4mzho+STJHJAdGnCnzZ/birZwD
9CIB18ohSG5/0/N4T5sqnhv88aJWOgNHVc7gT6rrqRWiC95Lh8VkeuBweg0r+kTE
IDorVFJ3vd1s0UKkWov5Bt2nBldL8iX/zKh0d0slezJyH6I72ZiPW4m2N54Z47fG
WnkcT4qHPaj2Evx1cZNHG4JEAxwOK8mWBVqxMYf3Gj0+LMkVq8k0guZguM/2mXwa
KlsG2M91080pF1JL6AE2W3mXZjGKWqbHvbI9gG0t/kruIZi1Fx/z0i3t7/aEq/w7
7ZHSkDefCTHb0uV2+DPRKsbmSvXYfL/pHimN/x08H5gxNnJCnIaMh5BHc6UzpPX1
XHvgoQ3WsdYGAT+XN3o7iLtEyhb9tuzxfOVT0RvT/Hmn6fYyI8aO72ieZtytIkKZ
qHJjxH8reZvfi+lJXZ5On1mmdBWX4/c31mk6AnQ4Qivfp5XRtUcMsswOfBBxsR8D
Qhg0Wt/dGMMunFb7oiR1eCrSSpYJZamYr3mMquResDl8JpY1bu1wjVyStXliuWd7
tVpo3xEM4aES6+XVEvDiQ6LA/KhvF+EApA6QkYwOdAuK8kYso/br/QGuepcTjhNV
1tQFuJgfXi+wn36zqvVIgmdo3fbPiMsc6Ag/w/nFua8bkxwZ3w8=
=XJqV
-----END PGP SIGNATURE-----