-----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/jalu9uZGunHyUIFAmnnAFoACgkQu9uZGunH
yUIsMRAAm2O6HkIm9GYVKBkaT6RvafGEv7v2YT8Dwbd5iZkWV34L8XweZoV4hpjd
HXtcPvRp4zhjX+hY/ZIr5RQrpLRpOIAyMG0qFrxrpUc/CnbDLBG8+xSrxNClHnBl
atVX4GABaPAMeXeLps7dtLml+Rzu+IhM8/MYJfCFTrbMp9SnXtGtQwyGiODBp+A2
v0iefte4Hom86KaDH1nX+b3+hf5SGwA7WbWRh4oRPmlHuED/bWDA0k6rfMm1OFfn
xqCsPU1Uu24eKC5NpCMHwdBNLX7uywReKtxIQ6ClfiKttqZgr1gJp5nV9T6AMZNN
og1/Ilo10Yg4Ps0BlWY77+sq2no/6spHOJBm4R8Expm0Te2Yt9xm9AfR8TxW2Ff1
Ym64dqWlzoBn1P/vTXsVWpaibAUq+TjmsZiiRRY4iRRqdjx8BCFPbK4eDjycml0M
7+2YZh0iyemrndRLjgAlNk0CfZKiu0aYgXuz3wzVfUeV3KDfi3cRh87wdy9UHThM
9ycrX5OVxpQsEne6rad+Qn70CPrapFQ+LQ2YQUdbh/jHxy4Yh0SSiHVHxtYdiizS
BtNx+x1hHQbOrfXGbvAvsahVK6X9rKQ3vPBtprgoU0m/jbRzqcY/oiw2G8NyVD1M
mLjYlB+f7QhinTu0/qAAa+KDozNjJxb2r0lWAun11/6XFVghcCo=
=v4+h
-----END PGP SIGNATURE-----