-----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/jalu9uZGunHyUIFAmnmJcwACgkQu9uZGunH
yULa9A/9FQb33Dof1J0NMac64bRXrgjM9bzKkTptCvPFiJUm11ykDruMedl/PcdQ
CM5XDBSPStLRkfj2Hje4SRw3WLYTPOE9/JmnDoH+ZFf5EClawxgx7+9NaR2HWE8l
97kgexVnj1XImmW87UjZbPH6Fbj/BtZ6aGPAAqlhTa2skBhUSRNkDanGm8oHCd3K
ZEjp0CNCIhPaN25RM6t9WpXinAlmEPe6WFkW4Ou4eX3t+jALNTaUe1+uTTWFCqgd
MV79OfPJWbBRm4uU7qvNlrVA06VxS5/8046twUc9ROKa7bCSx5hvF0OIGijJO3ll
ggwAf2doDjHiccFQQ8PH2jIC9+7EgF3AGqbu7LH11TlebBFtg1UO6mjh64nj84O+
PrFW+kp/aKIA+uGQmDPAiOAhWc9a0F2XzFz4K/dlyiU18tXSZMCs5ZrEJneZORBA
DxSFzmCYu04RbUrPqfh7eTg0GPn4jOnRs3z7FPpJqtry8ZgL/LcHBX3d25H5IsPL
GzHuDHJLbe7PpFP8RweB69meRA0Z5yn7qjDPhExN2TpJZhK+/jp0zLHP8Vl77+eQ
/GznUHP09O7gAidEAF6q3gEq+51iag7wWIbGzNANSQ2ZT1cnGbtLIA6T0ogfJZbS
onlDjLGR+0eGR2XXsvckaFf5D09KDmgjdAvoSBxozSicIsEsY70=
=t6y+
-----END PGP SIGNATURE-----