-----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/jalu9uZGunHyUIFAmov9FYACgkQu9uZGunH
yULTWQ//Vj62cLYBWqSzi1tqKeJweakQ4e9dQeEu8GMEa0okbeRQqRrJA9X0cAjT
VPCiZ3qaa/TfaUng0V80l2NiZx+J5uKYi67iZOKnG3Byo7ZStg6EIB/zDG2ZWdM+
LWSqAYPsHlSNrwbu/fjEN5j1aY0fiGqalL67Y7pKWZ4APV2xS0MmK5PPr9hWajPr
bp6VVBmXhrCTj2gHh6xkm4r1Wa/QgycO11W4L8n7OlfocYa+h4AZzkJarotvY4Hr
uOfgMP50DxdOO9UNUjRtsoseBzg1uWqWa/w3/TSlCzmH5OoTaPawF5p1RuqXlLBt
gNKmGp/P5k1d04Eeb3hM8JR/C2ZLGQx6EVu7AK4OKQOTq2xM5f/0cLddLWyHZa5L
Fvc6xa/IExxJQB7o+QnEGK9ytRr9s2Q6x0pJPBMqohaPYJWKNzxx/+5YlUQo99T8
bfKe/0WSmWe5M3iwDun8WW6L4CpMvBra3QUuhD4KVqZYEKDt8IrACXUCFo5t3r7I
d12ntTyb1iDU9CY/YfElWX2IG+xCsTVfhgB7Jrs/AowiMF1z5f7Lil1p/EM14YHe
SxfwHWh5/9SeMjhoWZhCP2tG0Xhbcisn6JyfhufwQ6kaVV2nE4y7n+BXm+Q4u06G
zHCVe/F1H1BEgoubzHiyYHcFX5jQnN0uHi12crMKQOA0BwArC/g=
=oCd6
-----END PGP SIGNATURE-----