-----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/jalu9uZGunHyUIFAmqqXLMACgkQu9uZGunH
yUK35BAAu5KOqy846LMYMn+cxgj4AAHBJWxOEjB5veBy9nHCQ4clZ6kq4rgf48Hx
PbvYSdBnbMELe5avv5ScLM13xWImU2YJMoG4JZDV5GryAI0ncooDzTWpQKVt4ksM
QMPrB9p9kfaE8+/dVEx2O8hHaxiokplpPtPZhSvOO8lT8lBDhqyvEYgfelkQES6f
D7HPV+iAVV0bqdcJD+WB7VZWzWbEL2IggL+MvYyUuYQuGV5hwowRbaXaOtvLO0IP
DtDCIRYi8/1+gzzS+QKdRgDqWmFSUtDT6pQMmi+rNEUo/QwywRs4SIeY1miZZY7/
UVPmKtWVa64C+nmvcGYW2hHzviTr/bRtHfpoPZx4i0d7wNYLxdnB8FPKejjG2wrk
WfCFEi5aOYWY26TLsOOLPfie+IABrnCgTeifEDfU3O2yzXvyrGuYjZ/fMXjNGt3L
NPdfX7oft9Se5TubMWKLhnlOxMg+01Sbio1z8d/R7odW8O6Nd2MkGAf2Q5MtP9RX
eV2Ju1w1yyLfQwvkLrBOzvj9ypYJTIe7QNuliBiFkFFFKN17yv1zgMA7vLV24ObJ
n+BV8+fZ0h/QtlGRuMIb8P+9d+gAZZ5zy9IWb+Z5nAmeylfDY8AZtDWan7Nt8NgU
YymLD/yquIUod+LxMhif2EByBp7YmogM7CgTYg4o1FCEELyrYp8=
=mYzn
-----END PGP SIGNATURE-----