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

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpIwHQACgkQu9uZGunH
yUICZw//fzDCPdy9k+tr2bbG0HQIhzf7agn5WSR1waPvz6WoHd49ZKCWuH22aHyE
XfXoq/bC/575aMkmDLGc93Lza4PJPJH+06GarZO4XYqBoFXZjDHZryb7WGusz3EW
rh7Tdhy1Pnnjr14EQc0cgP2eF/FQmYXocmeecNoSs0M1zHgGNeKjAOZF9rRiwj39
LeBIdT6Qe0CprPS9/w6gyQeYbIMOr495xEFdKanbiy4Mm1vj0F4N/Ei4fE+CgBek
oH1+wczDVSxEkuGkcQFM0bLl5AxHNDp1rP5R1jIsu0+lR5zXXk4d50gp/q9lqYVf
HFhecQqvjtH7B/dSbj2Js0UkuV+GdxRbK9hjw3xA4OVIAQ6ypsrCq1KSc7Xvp+iL
V8kQDiqh20HZi07107Z/WYPsKiXbAnwfpU9kAbkntUv4dWw1BI1rym2vBU5+KG68
D802P2pKsRBjM4AFQStO51ofDB+fPgSIYe6trIMS3vHIHwb7q11nsKX+tMLf0aPc
0di3Xh5L0VAsn2YzhxHIfdITVd6cGSj9A5e0IjaZ3e4Dul8qLvbbtciyBVSsluuk
kO+3Xd4vhRsvT5HjUWUc08WzDjkwDNLFFQWa9DbMx54Ss1obp0fkFw8WdtbbeSbk
m0qymm3/2F6NyGndL4LHFmVw6szC6JRERaVkQErPoGu4c60ha88=
=zcmB
-----END PGP SIGNATURE-----