-----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/jalu9uZGunHyUIFAmnwFicACgkQu9uZGunH
yUKQ3xAAhkNPQCAQtqVyI+HsecQ6aho9f5i2o5ynbYMcw8+FSfJ7qo6umWH4ALtW
3nSEshnbVOXs9HnRwxwrQ3P8b/n9pcyll7yLq2nB+1QtezOKq6ulN9L26r5XhaZ3
VGQoQn9e2iVaUFImv0dCwiFvDER496eHEI2UoBSdacrpRjzN08oSbhfbS1DZ1Vv+
XrL0wVGFuA0AwnuRJBV8ogg4NI0wK2wgE5ZlICIfRytbEZ8qELTMBOMcWMinU+/G
dJcd9dC8EkI2bf5wVN0nBB+/lIECooM2zDNHLiwQD8k80YsSRnOA1YBlLJ1rFmez
Jk8xvoc1NOhIZFyFHQXxmlVj7FaViuCSPgsJsFqU+05X0RL6LiPHB2V1UKmoqkmf
6Kryj48qPfxRbLlbIeIgGJI4DSQCowffnsgX9v7KkCe+z8obQCEX/foLzOpe+ZNL
0aSfVEBiSgJVHlMmOFaTVtB1jI1BADlOWFJh4jW7W/kdFLT+fAN2Thhst65xqmc3
un/ulatq9OVaUERc6bCK6/4DeUBOSbLEpa/HTazajeXmAXknp7UMR3CmJzEDQzSO
/BBsmA5U3yb/b9hSkdCPc1TOysfHqfe/OtvmOtnSVbeKNJC93EX23YjZI2JVEymT
7EuB/fgI1HqtWfmsV9WQm4oVGe0X3yjsgUuJxC/0NBV9/M/BSh8=
=qP6O
-----END PGP SIGNATURE-----