-----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/jalu9uZGunHyUIFAmmzPa4ACgkQu9uZGunH
yUKEAw/6AymGQzWd5XvULBBtN9W/7UVyAlQo+MPEFhOo3tz9UUnIQ6vnwQ/wr2k2
P8EaFpJ8BALAoi/5+gPZG19HSSZTOp/ocrIJi0btR7QPcdshNfU90+fph787NhcL
FqqYxKByAWmreqDyIi5v8uer2pjTCYBCVE0HJxoDL1c9eexBwriw090GNVLnt5H7
VfVQ76QmiFCtkDdNWNnsZ49EGj7JzzTQxrI1T2WaxhNNvHfCvuYxVYqXNJIU/bTg
JJ7+ABAslSmknyah/53qzYxz3ntpUxRm4pQsV8c1bt0t96Av+v3g2WOXk2G3mw00
yjOobbaNxST+QjKZvfqASFV8Bc/F1j/1Pi/G0PdFanJfAb/3OC2f8VTCotB9w9td
3AwhcWxohnW/wIdLOJmkFidmXp3AtW290JyMwVzaJpJJsEw2MUuIH2QWawAPB4vr
cWsHDhoEg2MSo0VRAeEogcPB8BglWJzDKuUiHZ+EjRMXz52DoVt6Bc+tD/hmrLSy
cyf1v8x8wBrcoqTYNHhIy43tx2i+LXRAAHLALh+3aDif9rjkOAF0MgxRkmv1OMQN
qRwwDIax81uGjHNjFsZ/gb8NtgdZfw0vpX/2LNBpXBz1l/uuc/8NcqOfEhMY9jHH
d79noK/JVoj/0cXYovWxZViKMCs2YUqktcMKrxEh80ORWzXIrfc=
=rttn
-----END PGP SIGNATURE-----