-----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/jalu9uZGunHyUIFAmqbWhcACgkQu9uZGunH
yULbOxAApNvbjoaHV6EEniYsCLNGWVevVH1p8X/HXVAHWb47s+ixjTR1uPRp1aXq
jDyM4wfGKu+bvRR7n/T6OX3zSD2nYEiHAlfu0WWA/hG/ytK6uzAMzCwACKqtYb/E
Sw7KooZ+9Of3+46dQLiyi80HMtiA0SUVZxOUm2XDDNHHwoUVy1WjcGjtImRPSBR7
kkfvgu0JdObhNWyQbzW+894hfN4hT9Kx4gRqdtuT8DWxS0X5VFIa4DSLOvKVd1Dl
4akrlDKsMdtzP/36V9721d2E6KKh4BYDKstcewrILakBsJHXNx+/4EAZdlfhmMS0
XxkKIdDNd5MJ1zkeU5y6Rd4yJN+tBse8qf6rz1vkmoTbcQU4RGnu79fBNUalQ421
CiWOkL76lDmGEBW0vwQPARA+MHB9fHqwDO2kJftQ3HCvAXt62DqWNIfSTK9Ks6ND
YGbuxK+U4Xkb7Gkssd1QD77uy79BWA5ab4dESokf4ocedJVSSvShokktnnCubdkp
murX6feSimLdA5oVzNvpFCpVfmNz4GgZgy+yYOXIFuZvUw4jhvS4Jmrvso6OOpsB
cGcefn42FiqJfFEUiXwWtF3/MAjlxkFL+4+qpMQYwZhmdYmU6o4Cjvg5jhRmQR3a
2xqWd19PSr3rNUntw4O64bPE7ltsxM6PhaBnSAkzr2AD6Opkl3A=
=jG5D
-----END PGP SIGNATURE-----