-----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/jalu9uZGunHyUIFAmqxrTEACgkQu9uZGunH
yUKStA/9EDfmcogSiN/shSQebT4B01QDT4/v7dUMv6SUQY2WFQelElY8HAbsyXFY
gs+xjAejuyR9CbMb6pSTXIJmUfHuSIkJfxfRCQ0rP3K6Cmmxjf8f/sGEbqMzMyBC
gvr0OFA/6tvGHmeaBlOpgBb4hJUO/VUlqD8Oc1OCLrVSu6Ra7BsC6zwFwrQbhdmG
LDNElwChvi4V2T9LVKur1OVSBnQbY+uLoblgOmJMaeZFV0vXQZ1Z9Lsp+vh18hIq
BqIohr/MwDATGjhpOepV1kiQwOyUCLfQtiNjzoYOciOSKJ8k0QmvlcRnY69Rddvp
6ZJEVjFU0Ytnzsl2LpMwRur3R2rKusbCClp1KTCU4Jz0bTkS8DIK7kLruZobkQAo
z1LjCBbQkcfXfTpBnnENC8yG8mr4moYws9YuDZj+7gLV4lQ/QxCkKPv5EQ+0uk/v
K9B44NYfWhRdjEPxCdWggBR52txCkNiu8g5ILwggGd4CJe4lXvD13Vd7Ytbt2AdT
NGrlNjfpB3R1wZtCURpRgaOvlsRJ7PhdZfrErq2WTl6E9YicSX1q72Uq6UfloEwj
HkMu0P0baqxMaYgUfpGtrIiw9A263g6KvtxTyDYE1UdXoP2T2iH5gHB7rnFeRW1Q
ePr9KH2yz7phcbG0tia+nV6Mryn3xJYWbEPb9iDQFGUwI+fcBmg=
=q/Kr
-----END PGP SIGNATURE-----