-----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/jalu9uZGunHyUIFAmpEkecACgkQu9uZGunH
yULxkhAAurPRuOaKPySJFl1ouBIdq4DgvWIfk95Yg+jILo4jFc/VHMfHjP3MjGgM
yH612Wu7qtcm14M8mWpXiIRr7gEQS6r6rSJnu4zYkDBxsZC0BTTgcRkhK7Zc/oIq
KyrT0gyo1ZvtrhbzQ0f3v32nwFVdNEmQOsTzBHNBI2DZFuXzkH6mz570CfrKNxYH
AYrv7/SA6dEPrzBVN2pq8ZafD5lHwbXhLTMDYvnE3RBhxI1rZJwXhj36+ORA/rH9
uXGjzrVMYGD9TfhL4sKxqsHO5iQy080t+aCPnsJccIIqlK5A/pnzaq71c0mjlGu8
DlB0W4x5hsaO7ta4s4cNb07pofLKYGguKrEbWHHF/88DskFzJ2tv+MZsw0oxF0BT
nvQfNLBnqFd1qaIHcZwvkBvhKCjj+W3E7ghj4vRTc3sqEPD0pxI87zO0UTJRREzr
PaUSRpBRawR1bxV+w6Rssy11mkk3WbOZFy5gZMdo3/8rJiTUdbVO+ZwUZvVcA7TH
N5ELOqiPEnr/bkjTpT8ieTcm60K/wRz8OcskMu98XRmpoZkxlnMko+J58ke9faw1
qzj+3Ut8RO0cxsV/aNSiKsJT1Qzqc7Ppj5uLo+i4tYiLUboqTotHpevgl1fM2sDu
PUt0UqrlLgvAcOlB3KlgLe6x4SKfI9QZsk+nlox+GCut4KytuMg=
=QyDp
-----END PGP SIGNATURE-----