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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmq9P/wACgkQu9uZGunH
yUIt/A//SqTLV7FmyQu7VFHJoCbR1fWYW4I2m7N0PdA/EuumdiriiYTxnsgb/rgu
3PM0uVI1cHd/cWCdqVobIsI5cM8fSlOIb4amCvkDRwEYbNJKhSgA3gHddNvdCM+3
w9oTGO2uy3t0E3Q2YKGIPpu/l4qh/NvMgHAsu939gTK2TjTfUCkKFdTxOsDvJuQc
tmOSO6hms1CKsNL1Eb6qBv0MEXEOPncKC8ATD8MeaVqlBgMVXsthZC0YGwEn3Rbk
K4E320Z6txN6v9SG7Bgl6vOkTKila0Rynm+vbYEJb20oOvV94d1z3ST/6UGIiVn1
ejoKey9y88tUvQXd/itkU+7/8mkK5sgw6H361n0ipibjXsu40YHfLAdPOXHxJIGa
B5Ti0L7NvKiwruTviiDk4StjEJrfeBwBc5FSvJDnHvSVv8IIqYeWIB3cCDTbsgbT
Z1mpd8g0axD7PjJgGMRGSXoP2eiKWGNiZdRcdNDpPeU5mVqaSdeNsD7iR9OAR+77
DbUxA1Nns2eurKoGLBGH4rj30ikvmd4IzuYk/MVrF5FGtZ6QmmUJxIw0HQ9mANDH
QdBYz9Zfm4Cz7NbLXPS7xEH21sorKfoSH+qD8RIRXX9CiGY8gp7YgXulcOacRHtG
FOXu7UiOvcfFUBLtkRQ8ZxFnOyp0Grh+hbN0L0JjRfA39Us/ObY=
=A9+h
-----END PGP SIGNATURE-----