-----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/jalu9uZGunHyUIFAmqnhs8ACgkQu9uZGunH
yUJ5/RAAlFK021iwn5xvkDfhYb/IHmJOJbfX3Sa+i/iP1M0X/v/hfiZ+3Zbkryi6
zdckum8oQ4rxSYDDgImwZPyMeAFckYFN6CFiZzbO4yQL5MkkaGIcdQF5vWaeNo00
tfZgYt8jJWhmdqSoHKJ+srIu3dskstw7wbNikRQiF5llfj7iu3sihi/S89yL8Fsv
B7UHcAtO5QgJ/Eodu9YxRv3dyK4T7ea9OC9Lx3j4Pad86OMSSdxJ1ED4sm0jLdrh
e+WRBXU7cCQnVrI7GjQ8Lw04CMyOY+/ZoYI6UstfBVf/E+yzgG3LSQojDhUOsAyf
SoNDwG1Fy8fKYLXgtZsC9uxxQCp+T6JBvwC6uWHwvM9ZfKDc/tBED+9oXUU3o+Ti
Jdzs/yhLF2Pgxd6ZS16lNOTdcEotS/OpOTsEN6qQ2zdzjuGHYfFmAuNY4J737E4l
7g1fIJ5X/st9XmWsMxDsUtXa5Juetq+Kl8IYbzvZftmIUiTviwHPL5oPgkU6HAlo
T9uSn0mgxulvapuGb2wu6Fsv/88C/lCs98ji1+dtuUQFMoTlGkHphzJK8mFrCp16
ImPT0oE4kPFs6VEhU0q4QBc+845TgMv1G5U0tcY4aVYQOZidzUHcycOhw2Kj0qth
q9rPTluz64RE5y2Uaf6NeZMs02PhNAaGF1DLV4g5t5wYI7EqQds=
=NqK/
-----END PGP SIGNATURE-----