-----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/jalu9uZGunHyUIFAmmb+aIACgkQu9uZGunH
yULu3w/7Bs7CJQS3nnvJ6Rgq+bTpuppqxYJvSxF80Evo6HgLUxwK4g8UpPAsYvRW
jPUbbTc5GPX2r82oETDOJvfRqd8NtqN/aDkqkR4I4o3KUiWwppLKKUanVBWzDOWK
ACF1diyBlR86kggyzwymKCqHkU8BO0Xl4hwI2yi7SlZzhuDR10WtIX1aYk5Bpz7w
GuDmM+oiKc4QdLEgW903d+lnVcriQYnOvMio1jNJFqWQzM0OA9jluCLL0v4dyoR+
mJOZ+I5f5+al6AyepWmbXFW4uhxM/w+ypdR5GKrL1nT9Y9vjPVZRe0jLoK1W6ziu
Dytl+PtWb/OuF8ddH8lJgOa2GNSTK5ztykS1BxONFdx72wqpWJVoabv1VjfoH8Fv
187ME4YwxrWUoLiWTNtx9c+8DICwMt95fiXE3mWbGsWYmct1kAqB5sBjDZpAYnou
Dy/FfHjp82a88H3OmMi8g5YioH2n2LzeI/ktk8Ul4wjei0Sc84fn+/HTt05FC3Yx
VFBXKlMNQKLGo7Z8cIqBiu59nWPm52d+A01Pfzoc7Drifb2HxBk/4VYwwEwWORFj
Q2k2hKz/1Iy/Oq2wKb7CEJff34NOgyGln0BgfOwqdVRMuNc02F7E4DQh0gaT/ESl
SQBQsbGzhy0gOQWK6myQZ8zQij38I1qu+hW3cCvJwpEUx26koPw=
=5Jsb
-----END PGP SIGNATURE-----