-----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/jalu9uZGunHyUIFAmkeVkMACgkQu9uZGunH
yUJLZA/+OYFWM8hA40rtkyJuHzPGXteFWQrl0Tl+a1dy1XhDRtHJZ3gVLR8Deibl
xJAwSSDOwq0PvQipA2IXAmUGrHCXYphdofQba/rm0q0MgLhlQtNLymAf+9xqIaqd
3J+3aYNz2OEXfTOTlHWnnj42WEWHzVO+D7M3BFMz35l3SomQ+lZ9bp3Yspee31VX
DSxa9o15yabg2V5fVLhLD9l8uFE24fdb7zNU4kTCrQfxyGkll+QDlGplYwqEvOlR
lQjhLNM9sbuR3+40AR8R4NIIYM+emJKsfPKwKvL9Zo+TZ4h4u5RP8oZHUoUyN5TX
ZMfUq7c+reFS7l7GvsWtrMAO1jsdzj/Q2kZAwphASgGKIY2CWwBqC6qpacIZo6CY
uFl7nRt480JGvszF4RTbr17/TPjHHzya7Yd8rdE4OE5XG261mD8tbWZ+WW0MG6Qn
z0O0M4i+G/lBf9LP/vfMyMBpTbRbrlSa6KHG3KkqomxdU6UCyFZBoqgO6eqgvKYD
/PG+sl/0j5n1QMDtW3NnouRuQM1OEeMBH7HLDQbnP/Urg1HO79Zk6HAl0CX5ckmC
wBxToqV/G6WO4eyMOutEw2UD4eK6f9RXiKXBx1YbOHltr3KePU9hjrQt9e014vaG
XJM737kEK7NPv10T3IXTbxGaxMbZncdf3x/SZteGmBXbEBVSM0E=
=Hqo6
-----END PGP SIGNATURE-----