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

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmqNlfwACgkQu9uZGunH
yULrbA//URAr5oV1r3T2R3GFnyKmp+cJ2vmXKl+pa6h4qH4Fz0Un2d20EQnF86Zf
9SMmsrYUFSJ7UJo5WBq5mW8bKO41InYPR6ci74omFZuSacLT6RHXOcGb00jqN7YI
lhhXrP1wXrQ9zYqdbz0q/O8Su3bBY+FsTdF4WFHHeXtPtOEGmE1dJuxp9Yf4RC+4
1ws71HyvrxsaF535NmoOmQvQoQ9gOyUkYVdHZLuj3XIMHvp3LsvfxtCGX5gLN1nG
QYMCpA+bLjYys2ktVPxWnpgVcowgt2ikgXEJ9jdhMPA//6WMcKVxkk9gOFaCP6oA
9NqkKZVKOcO4I1QkZF9V4m57arh1IcyPPDbssMLgAcDZRzhQUagKFu66lVyQEpWY
0Nu1DoPEf2ETkhoxEGsTwkcyt67KmDV1vArGyvZW+H+dNRmnDyM9hwz/gIWM7JHe
DrLGK2zN6E2qYSwJ0ux8+vl7kXOl4AINsGj7fPmhmbYmNQZt9UN0nOXV98Fols0t
fEvY7vRE56NS+CFEMYKZuwNIGBLVZobWXWnKgUbwYoIPLx/vQyriRWTzPNAvLDk4
e9xbSgUHDYplSwPVj6mMZs67b79807FBvrLYwMPA5igh80KoTgl/6W92WPAPQ6Le
2InWazUhm0ucYz4tNHQQeLXD6qB85+aj9zwbEvWHjLwNb/WodSI=
=XU9h
-----END PGP SIGNATURE-----