-----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/jalu9uZGunHyUIFAmoNT1QACgkQu9uZGunH
yULxYQ/8CAXr84AqX2b96Xaheaz5fzN/Mm59bQ13X4y1s4y7jHGBe7K8gOjiOl0f
8dEI8tcXA6yZAklN2o3c+rLYXgUMUNaO4epCdw2drmDXb7/h7UYyJAK4qlh2/fmr
C9N/4BxpVrMoYZeHcychy5I7VII0vsf3kwsEboOZsOlG6imfNXcTwa2ZQiADD21R
7FVDTFTcEpbmj9sdYp7kun5Cw7Z8D8by94zq2UYFFZ8jSVz8vi4odXolpB7qhEtd
mrXjl3uDgFRZ7EfE3uRpFbs3JCzfFPeWahtPNGRaGqlSiV0Et29ClubW2/nKrx/0
wzIPj6ub6qKIaKiSO0W2OEwd6CVbYJv3HsSx34XpLIMGzqUoU3Ljok83jYl9tm0v
rXcwjfPJN0poVxiTUYn1ixOxmOVd9Yfj5kDOS/JyqXIz/f8BLFx73nWmrzW3Qojr
CYnpCx2AM/vfOtnmsXdtv0+4UutQFoLNPzl6nGLEL73UOHzlR5YewFh8rYxn73gD
B8lOVtavJLZo9S0i0qiG2Qu6GwMsR8wmit8TEMbM/q2eHB2CA3rCv//W4iHcBWLC
zO/im6WHl36s+ymMCE/q6XWtQ+uYjB7XiwQi2rdqhtgzMtQPyoOJkcznfAZdjXzK
d5895sbAc38LTpZ/yHu9eu2ujlHhTdVGBNVkBToY52dK4TIriX0=
=T1T1
-----END PGP SIGNATURE-----