-----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/jalu9uZGunHyUIFAmnYPuIACgkQu9uZGunH
yUKtog/+Lizmh/3ntF6bq2ch0VcRUAYHAVDOr/Cdogz/DYbAxhXJGYpmch85kUKz
aS9Y8H4gUULkGJ9zYdgu8nFOX6UC+GFwSwu5eeYqfh0xoQQt2vaKYzZPsGlbNY7L
Ftl5ztxkQgeyxh2Y1s/MbL7O6+suBoJ56WzmlkdDDR3qZ740NmBF8MlgUn5LlFJk
qlrOYPTcaMVN0YEjMxZBg16xpVsl89ewhds7hNtxmG5f81SOKOo1miUa0jio5ACC
GFwrgKJKkhFKJyZkzMnS7wyvMHpssLTbnj7mRtMK1N3heMHgPNt1TDkusJbSLzP3
J4Mowq3ssDF1b0BfeGe2I867h+1XVjWa2Oz4zlenior8De33TwmTLI6Q/6cnjEyt
MCORgpLkLffmpdsp+8vMb4ai3X1DoJR2thUBJLDbfODEZsBwZ63pYvHum5p3YHGf
aEa7RxpjGV9bCIKpY9OdHdDjSkF/SZuonRmKkh3JEDTlAZvTT3grEC8mKCc37xv0
pAN4rp3FhYaMkMKEvLw3tUyUn7sh0Tqz4UscVwyhr06e9Vg/JgL7pafiSAR0WNTZ
df+6qxdELsi+Wql6+kTqkF/SpzLhI885JGM9YE15TDdB9+EQvV6MWnHMWSoBbPnK
bvLGCp4RXHDXu9FooxnYUAAFoIIzEY1qYln/ItUPRe/e7an2r64=
=xs6y
-----END PGP SIGNATURE-----