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

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmmxL68ACgkQu9uZGunH
yUIGiw/+LX0fOoaKTi+evlywGgMMElmJaAwIrO1NmYLHp8CxGwBjD36frtFnH75v
f3adrmOB8IR5OU1K3UoPh8cBSt2B16lwMiP/DRlL5XKIPAbP1qdHtpnF7OTTEOBr
I2mZpp5mXyrCZ5D9ZDH/YEaixBxcBIWJwJO0KcbrIskcvqSNAHPVH/WTpCuoKHwg
I2GCbTAKYVZOUoY8IKE/bhTYmDBVf8mo7A+GsJPRKfQP4YjA1PDRsUHgUxWL33Ve
FOsoBUXsstpRlhueq1TxFvG++/1pdrQrfOjzuPc/ecRNV5mel4M0MuiUGFR4DhV/
+iZ7ZOYG7y9V/co0PzFTSXaNmf5KuFB/zVLjdACMSGjEDg4HyPXXRkdtd+kgDu0n
wXzFArAmWXRbLaeeCNC8Qp+hqhZSWEwsxSDz8kMcgi4yL52ZWYTtWBc1OWHMS3wd
WNZnveUQeAu5ltISkn4zQOQJsKs5q3JBZGAPx5n1q5FQme+ALitNrmK5+ZRTlLoq
K2F+CNZ9RveonuvWht0PcuN3GtfSho8s24SFH0c39s1omyFwi78TdgmznamjhPRX
R0BoPGE2K1WQM5FjVfifzUsc07oJ4p1oCd2JiY5MrvRQjrtAAgxPA5CGrrtNM2hw
Ud6Oly/YrjDe7NNEoOy9tfbrhZvYOjWduMNRWfPo25cnKLgLkBc=
=U9SD
-----END PGP SIGNATURE-----