-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmr0dUcACgkQu9uZGunH
yUJL3g/9G+ZIDf2mZ/yTvn0MkaiEA5Qg0c1w9e3gdiGpqH+PoNbENY6/+rwZURLM
6dPYVmJrV58TLNUkRO7oEmCIPO5Eo+M9I9IG9/fDhk4cwQARC8GWLrCDvqguzwp+
6sbnctUKXD5KK78GLqRSuElkI6lgYjcKrCwWy9ss8JvdCTOY7r6g+Oja17A1QI6q
XjYxLlvo+m0Ihp1+CqaMepfTjfsoIaYDUbT8c8OHpXKfFtGCXXMSPGtZDM+IihvP
hW5rGwD4ltF5Yt1Ul2MpqrsFGsgCbVTQe2gVJBNwHRTW5PNwTS6v7yJAGf9QItlQ
am/lJQ1HMH5ghQ0l9yDTh0Vr2L4z/JIdRyaGvs9NQwqzfPlBqjCOSjzSsS9yOLYf
JL5RM0l7p27rV1fVHJ2bYPuWJPS5TlJejzEZDxWydqm0Zi4rmO8Cd14/Mnzd3jgf
w4eupnY8sSAHKxF5MkcVXVaKRoQMioH0Zby2Yg3yyiOLg2EGEtgARkN5/VU7yDub
SpEAIw61X1EJsMtL7rLPT+pFlSQNhaRPu+VGa+l+hnuz7OzllKVw3X0ycBdivRNa
f3fycsq2v2gzOtYH9xnPZ2R9moadErqrmOnkOsIRXs0ONeJIreLaBzwTZxCtE/Ni
iiEzKrOsOigNMEb1OeSyFU2d1YqJl2QERIjtCo+e3WmYpP/SDUE=
=KoDs
-----END PGP SIGNATURE-----