-----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/jalu9uZGunHyUIFAmksHl8ACgkQu9uZGunH
yULs2hAAuT3+7ZQQRlzalgXwGNrnnX/u98kVBFcuH2dVTl4vD37BPrR371OrDSGl
wx+KmQHgfJPCwQH/fgO2wdTDXfFEEAg3lwxp1o7hHnfAYV3X7NzuCXLMZ1TMGhAC
Fs6/o5Fllp2wLY7Z79h7NwsMCAx0CXWQekOe04lm1TQl/eGJx5Wi/pnGI6r4a9UA
dfaDtWr6JoqZdvm6JdoYQPNsxxu9Pg0qutueu6H1pALqyzaRuhZM0MeQi2uEuIBR
EquRcbFiFQEZrEBgrQWv0xHPlgICM4vB64uxYbD5C+w6ulkgltzJSCx9JSDMLcSc
2kCEGyUi/91AU0ZmnA1XyrLLhiVLmpzqiaCp09pq+P5NSNiAmcc7KeRycjSklgqs
+F3e3iPvSFtwryyVLjl87KA3DbkT9FQvF3iaNZxGw88VJbFHhf7Gfne/wJV5+P0b
ZVLrS3iA8OzlZjgqVXjEmUY/32s7HG7yQWR7JB5LMQP5QHtm61kIAV7ppRsVtJUR
76jYt0pMRy4Gq34fDXRobevSOv5P5D56y8ImLnNQQu8BtqqZP4BC+4pXsRHGHApf
ocJBynV/110UQwBA35SQFmsVtPO3sdWxaYLTdJjfpeEqlFo9XEF8Kidz9iF/jpwo
crCNVFv2XDNxNiy4qd2G8/uCFuKLCdnfxQkUmo+F6gJlQC54o6I=
=TcH/
-----END PGP SIGNATURE-----