-----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/jalu9uZGunHyUIFAmkMx9sACgkQu9uZGunH
yUI5FxAAmtrOzInQN6m+0txEiSDA2c0jXhr4QTRSQi4475w7ayKTUQ11RZLjEa3i
Z4ZLjIn0sAgJqGKqtXuD7q4Bz7lGqG+UV9sQPFewwlWefP3fSaN+HiJSDKfz83iN
as1pmXre1sMiaccY+2fS23KmVUrfPv7ILT35rxzt0WgZ/1gSoVgc7Sa/nxTGbYAu
ikczNckxJYrfIWZRNZmFImCTD5k4SbRPVJ6JEGGUYY43tlqVsiAl5A1BoLEN93Vz
/yIcamnQFwFQsUmM5Rin3SmbG6keb0jNpDD/qjFUvyxU4as2y7GA3V0P44/L6q39
tGhB3hZ/SE4Fa+G3jG8d/K+u4iNH9PXk5clUbs8hw6yeNcc85fKmCOjznMEWBn3z
kyeNFRIcQ7e1VtJhvTWRBGhH99Kc5oozpPXNtG04dGV7ZMhIKggMP9LCQLtgN8Fa
ZNKEGctTBB0EOlDZo2WkAp8cozBiva0OGsVhs6W+zeMk411UBtFwSdQOoWP6TBCT
KueT2pHFIYWabanG02bnvDeYRonk7FlzgsZJSR/U9c2mdtlxW74Gi12LB29FxC7g
do6wkGHapfs355uAO0D8kBqaoYdrGm8c136qnmg7BZdD1zpKOxgqbM9eR003JUCY
UPdgJJfxYDx0Aot+cl5E57HrfsxVFp93bwNiyswqIk6kf05j3Wg=
=pYnQ
-----END PGP SIGNATURE-----