-----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/jalu9uZGunHyUIFAmqGwSEACgkQu9uZGunH
yUI3aQ//R6xi/mUF8dJxHQVBLhVVs9RXR5YnutB6PGV7H9HcSR4tKpWVnYK+02h7
pTOUueZEYieXyP4rz3/1bOqjevMfU62RGami/g5A2TVcR+VugFNF1zkpk8xcqqOW
jAy91Qu7R9p8k62SDoLQ65ROTflRUE6JTs2ylI1El0Sn9mZFHPpPMCAQp+2NSjrp
qQ/b9p/GBawOFDLct4ReC++TvLTxSbP4VKgpgrRU8vlUNRP3gJybqV0LQEEmuu62
OBJvIrQDe+DbxebeWrla3/vqGi0FMM0ynsxadAS2Bka7lkDhgKBXpz0tg5VRBRkN
PWy2Ad/rVfk9mBBcDE07rChljx/UIUxpmkAh/iJGmRLzIgqXDeJFZD1zBz8H8RyP
HVS0Qpt3eMzZZkfflEMXXiYOyHdHialVIrIsn7Yi8FT5/d93UYxVayXv6JOGT1HP
JbVsTvBE7ABWo1Jw87mtN5VDhk+pYPlg6MVMJ9Jx7WkqnwxPOVHnPBpTkA4IpIqN
IswedTM1Qc13CmQYCQR7EgaYLyGZ9XBWq0Es2xeC+v3VXOaiRcbsWayxt4ECG2An
SqtgCMxSx8dgWP9lQ0o8wz4JdCwwM6FHj/A1pDyQcuKWwYCh/Q0cE5a7NBRJ56iC
Kazlm/0B8E2nnVrOlfLJFMcJfqBeVuR7Gzd/yG4IVHlhG8wEa2I=
=g71Y
-----END PGP SIGNATURE-----