-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrPECMACgkQu9uZGunH
yUJu3g/+KkCCaQTahZHznd1sOJ8Briz+t20+R92Paz4Sr6SctLEk6YBMJtDVu0bq
lNdDrjOgTZ0CCB5nfiZ3soFNpBl7Ri4S2zfydd7G4Gz9XNpmj46Cl2R+t9+7SL9B
DyZHFx6OTyaiOgzB2qDaVGMkc1qO6EFpTPrHvNVr3PYulBMMaV7VThRt1/5X0/nQ
qPNwOJx0FeCdTKfoOPxJ/j9NKYxY+EnwvuRXBLnCdu2Tpg80vlsoJqOKZ9/Nj8xf
X6qfFaYUnkjCzxYAhnnIyNJF6kiS8B9SH55XsJAkGSG04ns5YsjFB30FxJEMx8H+
Rgsk9GCA6vKjBFuEn7fDC5iLduL1FWgFUwk05zL1e2rFX2eREpMitoZbOFhIY0CU
5xBFL5n7eNyEQ1OFK7PTP5ncFC+YU34lgGY7er4wF3PSYDnHIbARYe5tTtqvrzFA
IvrxD6A3GvdmrAX0gA1gOAV2gYafgfllulb6eWlsGgYpUgxChnP73aNteKoeV4P+
cE0pAs9q2b2LHJRPW5T8pZCX6gxY33KOpnfVZeXWh5hYVCfBlYBi3jFmda+EwdEl
Z+5BN78hfGxJf8T/CRD6+NiUVQhD+5FQEC0KN026W4VAOm/ma5+d/cKMUGlFit0k
brYQlLHHvXgK3Ew491Gv9SxsbKlbwNBYF8As7NxyZaPZApkIuD4=
=t/tz
-----END PGP SIGNATURE-----