-----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/jalu9uZGunHyUIFAmqv1vMACgkQu9uZGunH
yUJvjg//QK49QkqJZrUEKqaH8/w9gc5rqszQ5i878OG3MMjlBciM7DMzlLQnHyv5
U7paUGIYLNLN+3eI5NwUUjRc+Cox7UPiHaDEryzm/rhiaW/s99UEjwwEqjZ2RORp
kHlqkT3lqan0o7kFD9nwrYPlrZTq3eM3BXUDRpUmrlTxuDTmqZLk7ZkcF7IUrdRZ
TB1tyO26QTeiHogvpGhzXoMyuDYFOFyEMNorqj6YEp3kVPkDz39kRdfstWnFqYh7
GXkGHl0VW8P3ykiD7+qoRhldCWiS4deJtOZ6UYSbMKpvM0qleFJS2GFuFV4MUwSb
wqANY1EkqzsS6tScGK/AnKpVrW+5SLvkbqitSatdl6BLYsyazkuOhc2oFRCapBhj
SUpEaleqC8b2W66aFq73mk1cFA1W250pwQFljQO3eXWit57HgiNJq207aBONrFXQ
st85AQr7r28quD08qIcLPO+ED7iuiCQM/z2A1vLOaH88T7GVxiP2mMx767+3cKMA
OU3Mv5HsoAcegW5iv1+WZWyUxo3EvnOGar+D6OOuHjEwC8kuc5Ufieg6WRI00ZVI
BWizu7lWDG2Lpjhavrd1akPmPUTLZjwIjZ4wOC2IMVKv1UNzmXN1Dbix+1QV6YqQ
xYVcP8Dnogv0inc5aq9FdTHNfyxIF8z26iAef+DmdiJj6GVWozg=
=Zl5D
-----END PGP SIGNATURE-----