-----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/jalu9uZGunHyUIFAmnqjFIACgkQu9uZGunH
yULPwxAAk1by47trNnHqW5H4Rvi5WekPPWeaV2G6VP+3cq6767glx3zuDeMp+eIB
cw1CdTwOUR+JlwjZ+LHZN/P4Dmc9BJzx3MIrxvDe1kgd8Y22kUUV4AogaT/PInYS
96Q5q1fQRJCp9cQnm7/yJTHLqz2MFfkFmW33p+TNlpd268N8yt/FigK18v9ozuW7
e7hD4WqH6D0pRjBz/qKqo5Y+9LTMhGobu2cHKocjH10XGSAdUVymQIxp5ambCLNd
fnieJFtW+SdXh9L9tKxVsfu7pwsATGGBmPc9/lL7r0bqa+MQ8U2jJlehZBa/CE5A
r1DuCxH2ADDYgoK6AX5rahkv3yW0oDIeI+AWt2hx3WrEStjiljfAVuVXYPnI4rkl
RDNDdNuK+VA3cJ/435OrO8yD5B4oyv0s4qcDiABeEX/HGgdHW2hnQLj4QTL82vga
8BaYgJjrM5dAfnqUKTrqqgdtv+ungEvgUrMUA1vz6fIRZruYXI5n666vreioIEXQ
6t1cetH68dLGFayqCf2wc9UTCVYDEMH7cAOIY4y0FOPW5eFPEz1bPjs7xtD33CK9
76zZuFwqyG2IJFLIpZVUdTiNoaJh6zJw5HdQ3ZpADPyxt9lX2g1LRXNYhDttB+Jt
O6840i60t8T0oCsJg6mLncuv5+852r5St0+IFxB4bZoXN43j8cQ=
=oSZX
-----END PGP SIGNATURE-----