-----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/jalu9uZGunHyUIFAmp0kBoACgkQu9uZGunH
yUIOIg//X9vYUvRepV3jc5zcP+NALUqg4Akcxvu0R0KnmNGL0RjFIMJt6KrTdGsk
dcxgl5SWFmExgw1b/hkO3Re8PH24+YgGTD9sNbe4LL9Nc5rJK5IpSSNX6ka3LIua
qnsc5z/zjhdUDbrCJsYqd41UQ5Xyqtm9p+sXRLyr4fBxcERHvPIc9FremjYEyT8E
ob+bJLMcnVxhjkxcRufXgz5KmsLL5dDTSqyBJ2zyo83VBgfmyQKODmBfpnCWLyST
QTZB3F9dvOJBNe5aBleTg4hgfK6YE8QLKopH6cNxK+OPwxxABBMNobU0Fj/OeHse
ydu+EYp6nflt2CtQB/P93aSyPH/VUO/PWsHOk85RqbIr75XY6ky/1yf0KpU0hHeT
/hRk4wLfYXfmR8pCNjR+kG+nfYFz0ZHq4ErOtx5XTl7hEtaKPq4G0i553HdhOqZT
0yEuvSPd10Ar5OFKn86DsZMWVRkRt3Z9Hkdba0Fa94nKkVjjzyGvx6XllWQ6h9Ag
gCTnTTabAJ3kEH313YCTEvZ1VKbo9T8ufynCs6GpLS9UtR01pTMOhNuk1e8WJrN4
QAwzoXmqmgwk2hscNmD8VDplWUwASJhBvNOU57pNSBp6AqBPQbD+ai7l9pUOMZlO
lnJ55ZDQwFtKH6E5JQKyGVRG5VxpTnK0bOVQC+HO8tOKSdC51n4=
=yeIf
-----END PGP SIGNATURE-----