-----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/jalu9uZGunHyUIFAmotTuAACgkQu9uZGunH
yULKGQ/9H7cDcXoSRBz5MfHp/FmaT8v2SNsevHPxZx/yDdUIC390cCQ4vgUdqk7+
J2t7sX8jcUCBbgr3gVht8h5f3zo6+MMANbOMSrIx9+mwPC6gzyLgtBegD0gpCcLH
h3uI83sqUno7eWNfBxxN2r82jkbcnSAaQSHfgwJpV9o0Pu5T/3JTJddctLbFXa2k
hdd1u3Yhl7tCkhbgiymcClzzA61yJASin2Zgd8Bmd96lR0gX6CGHqjMcKrvZQxZN
CdXM1KrBsAJKTzRtJzGrmECj7XkABTW3iMVdt50nrmQW1Fms74Rv5v+EXujX4yS4
VMw4NWs9Z4IHL8cBtjlGipVZOS9F/plCou/uebglnoTtKL6ycMe1ueUz7RuFbcAc
97+B40VaopnbfLrNtmD78p0OXGDsZZnFe1Q1tfEQ5eBd67Qm9lcv/8529/VFyefH
33F4BNKCpkcmSFNsbEzlYbqX8Xjf+PodRMpUu24oTzE2MPoJh4ip1YCSkp0NtCbD
/XBhvzjeo8uTaM5nZtoflgoOYsJPB01Fp2uSBTXhwwen5Fq5OzK8PBooKLasnwZo
8TsrDLpF7/bi+GD/y2M0bmCS8Q8FwD3chkxS/KTr6RXUjHftCKYyn83ZwlktcY0T
pvEySEK7VyqNti+EFcVy6t2VmJr3NPgw+pmZ/mBxxxesKiXul2Q=
=OuV4
-----END PGP SIGNATURE-----