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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmrFjZ0ACgkQu9uZGunH
yUJkExAAgNqvlmbPOvCbVJfR3Lw05iZIkb/0BaA7ttQb6vZSGo4tcI7ERowoszij
8eG5m1nOgxkRRNSIf59TBE2l1AKLbD2hqKnCygHdB2A+MDP+uXSEW0RbQIdztGFi
uh5wPQpXtG3avT/gCBFqG2is0y0zr1Ry7k3tlsMzxebp5tVh9A9qUmiqicHBykLA
7DwjQxZa6f6RiXwNjSBC6X0wD7IexhyvaOf27VCPxx9QhvqfbOd5XXzmqG4wn/tm
vhtmFSY2RWLyqz8q2zN0fZ2eNnAlxuQ6US29+1Exqk1l6wwoScwL2pOSjKxV44Io
lwYS8i8sqCHFm9C8nLgC5jh91ZriGRFnyd5NICgf7jylnM0vyaritnts5LtwgWgv
7JAoolgH5b7POt5XV21khYZnSbyXfWK/fgzinE6905h7s0xPEDdxm/Ak0qhlCsuk
r6c9SmIbGLEZInkutLxUC3swzxVvn7mjVd0RXDgtp6158sFfWdiRnyHrBz1H26St
65CGMXt5gcMzpMg1cRWnr8jnD+5nwBhTUxpgHcoCRjTkOcNLf1horYJrFv7EbFeH
yCuoDrOxVE5vOAvPTFO9vHozKuMJ6sZNwO3s5rELLsDJDbLDYqI9neWOQByY4Xb0
FkTr8l3HbN2hZePgOexkYGottskid5q8B31eDbn6his301IOW10=
=wEWQ
-----END PGP SIGNATURE-----