-----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/jalu9uZGunHyUIFAmqufOcACgkQu9uZGunH
yULULhAAn6kZZu1BgHSQOB3uRAHiedKhIZHH83E5ldBPTqt1wELqV4LOYHbHwLbU
R+X8+C8D+ThUlHgoD7NWlIdOYf02MjDvjmw/j0ftPpR7C6aSWLKbsutp89ys0cap
NqhxfffZsPfUxIKYQW/W9Vx+MXw5/E3NrcN4XLTPLjBYa+TrG1BsE/bw8l8DWB5A
ySq/6zdFPKUjExYL9TvM8G4cswN1wY26AagN0Dnc7QRxFZC+uhPM+7BG6ylHd+8G
g95aoArEhJRV5ub2sgcZG4ELvk10azVJA/wDyKC0sRFR7zp67zun2Hbr9lB1bbT/
9Uu3J1lT2fIWcDyXYykTewDD4HKD+onvluSUEy0DyOUfxinoe7DVM7SIeSBzGnvf
zhJLIoiwaeCzmGO3r1QNBfuOWzyEyX6v2zb5D9aEVi8/WmPUtSS5kmfXcJyol6DP
YaMuHCMrTAbGfFbYcaUr0BI8Wl/7BPlJTWA8LOgJ/FRWGIkM/wroLjlxxtM7QyAN
sVteJw32ahYJNDHUz8yULpsqaOndZZqCdCXgqm68C5DvYuFzamX1kPSqRv/mYF7K
c6uAaZmjopmzVdNKxh+2X8adIS/ay3uFnunDIf/0q5ycpqXh2hKoSCQYehYmVD8m
bO7JR5ifBvviv3K9ad9Rn2/didqFTyJpZppulTm0K707kQi3yxY=
=355N
-----END PGP SIGNATURE-----