-----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/jalu9uZGunHyUIFAmoiU98ACgkQu9uZGunH
yUITpBAAviLgxbV/t2Y6GvutQ4ZRtadOgYEv2xyaU7B/zS6P2es30sro1+xgS8aZ
7LDED8JkWOAqLoiHmRaXyjtggSM8LW/eNbF66dEEvrpwgnUYOvL3Z48s1bf8Ub+2
+JrRYJPlxyW4WeCElCB/TnRKLcAEgwXXY2iMD1vgtroDFrHrl8zstQN7cwiKxRuD
NUJqUIVduxVQCG+Rql//CAY9ntDXS2uplTTV1L8DJx8VlUmSNgFaqC7zyMTOtMv0
iZWxC1LUgQt2OBb/SAsdjc0Qoe37TBhrqYtz3lQHqCgYNnYGurO/GEyoAoFisjAm
OfGRp7O/rRgtkjX6TRuI3I6clwjUt/2Xk65puSCXqnFSg1xRxYW8XqIFbo4ZJVv4
4/kLgWwXTA8vZzbm5uzSo9nRKKSyyxXoGX9OmVCpU4luvQy8Wfgca2PYl0b0BTxV
NmePY3Ivb8aOsNm4EFve8qTUbCxuqzQH5KA4PNNmXSG41XI7jVwRf604jdrGaIAG
ExDjqWmcOeBGX9w6aGcqcKcf2kYXbpR5k0UewoCam2pKtoP5Hvn1s39qrF2MIJE3
rP89ehVMATfES0rtlLvQzNPW0Lkb11zbcnCvBLkAEhd6z5pushoaR7sQHz6hlfi0
+4cZPD+AZfhcjiJmkMsIfJ3C7O+/DM7eKHVsmV2K4C9fY+rmjEw=
=I3+E
-----END PGP SIGNATURE-----