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

md5:
59e4df872f9a12e06e8078c808c5c0f2
sha1:
51d586c7efb059844209cfba5c8cf73e0a6da2a9
sha256:
527ca6b1731204b25d28e83bac9b30cabd3b5e2ad3081f82df81666d22919ca0
sha512:
5c504777dbede6fc2dd37b2c95b07962cc703c798151014b7efe752e4342c4efa9bdda1795ff3cc7ee01dd9c87f7675f27fa9b4299bbc010c9ac8be25d961b0a

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/jalu9uZGunHyUIFAmgMsasACgkQu9uZGunH
yUKfoA/8DYr2PRPexRlDyOI/Bmgy2ZnjQdrlju6+w7bb5CvXgeRKUJ7W29srwdWw
2qFI0ZULPHrQBQv2NOoN7blE1dfUrVZo8CgJA++CO9m8VcpGsr/UCdYEpBbYDFaK
GsovbfZkqPSQmAkZSCkUr+hyVrzaMkCB3XFabtjbuzUx08iZ1H6ArR3vTNJzgKD6
Nfb89u0SXyacqEgPdLlGILDywpx4AniJToJggc8GSBIW9TcWLS2wkxQVBKRe2acV
gEqQNVIjWNCsT8HObTCXU4MMYegaz0eNYisoqikw2t1EG1JPWQA82g+xosIuGMqF
2Gn0esCW9zPj02XIU9/69OzO3ARncFARPB+WPZq+TwlXDGPA46l76OT3FcMVmnBw
5LdE9VchaKoB/O0y7lxE013+7mU38lQNbrSTvcTeMY5WjA0/1h+TYFDHZ8aY7odo
u6R0x5vgLC8BkT1tH/2p99UcuzCgkTMlXNOLFesPhHNUxIoSZceSdT0odttIuNZx
Vh8Ow5j/UxotFpjFU2MluhyFmsydKJLlYYX2O9DE5n1mH4+EtbvCHTEK6sCLcebT
bKrOOGSv4jSwdy63ezF/dWO/KnmMVW5I/Zt75k6Uz4qcDlLriDCjTSrGUwcKKmpC
iSNAsZd/zrgbdIlw9LtdSKEsNOQzVVcCGr09MHt/Zj7/ddRE7e8=
=DnPx
-----END PGP SIGNATURE-----