-----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/jalu9uZGunHyUIFAmpKFZUACgkQu9uZGunH
yUL4/g//bOF+yhzN67pxl1OzBMSx8i4R9lZC9jfkiDZMOpKa19QfBS13BgoboC4z
xgZOuKvjiD6VhVL64PKz8LxPmgxKoY+dujup8VK68KD9jcUSLUaOT3MeifimA29A
QrI/UuEbzMYzmI53WXmjA3VieQHhQCipUxUc4RhuVXAArIiB0zSAkbwEae10nK7w
61F3vV3Vw5WsKGmKnvQiP1+avXcyOBW8DnN42JHzB0hU8aEbp51Cy+ONzUx5K4g2
zMUP3GtEx1aUQlC3W+gwn+esUemkAZ1WEvWQea00ExgFFzIW4tC8XLHvnEKRl9bJ
E4g1P93E+wyWn4yD2EGtOMZqryWz8dQQx2spUpVmuWKQiembqANjxka/uPSWACa9
BhA1Wzk+TuAAaIWr2rThSt0JHqO7Yd8O634KDwVlHaBRxzMIeayRNTLI2INdb+zU
AUmv3aDiUj9mvlQ1lfHeoA26ku6AfgJbEHFuquy+SD/AtaGmdNgfKjFJR2jupPX2
R12kgVTH9MMxdEU5/zRGeWCrtbQDC0nOf1lG0uvbsBoQMqRzdP7W0dd+IQC4lmto
ICP8h1cArr8eI/jJ35vur0IVHCEvMXkNWit63phKjdivo5lUWxaX+WXkczO9ulwP
G6BBV8xQT4amuAanx+K3o3gZCSz3TllSuj7/rZVgXQ6ru4iZdT0=
=Si5K
-----END PGP SIGNATURE-----