-----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/jalu9uZGunHyUIFAmq6TtAACgkQu9uZGunH
yULuGRAArG9jm+0nexyG7Jvax7F0JIeuOpiQJW56s5Mf4PUGG2ne7gOx9T5711H1
QFSaICipnCAr+MxagzexkEAGtiQMM5w5j/sy4TXiD2p5Uao8k5w/6s0tgryOIEeT
M4ygBiCTzfnYddE5yBN+OL9joUuEBXP0aWZDWAEXBuUJk7LV58WPXOwdmjregsMu
rzYxsxC5Zf6WrJmPNdFlMuRwZjoUhTjv/UzQ3f1SvkHZ4jysgqPUiSyAtHFytWe1
AiXKE+jm+v4ppUgjRd82+hAQOgB/xZiQ4eB0gL0/bcIqkJ+K5Q7snBSKw3ye5UHQ
YvvRyIgco5VzkZxe2vXH0iRMQ0n8GcJfRBJXK+hzAXEVHLBxwiFyu19d2S4h9MTd
PXSYs9A0MSWIoJDBgV3dhc4TjU1NvdQogHiv+mPpiEUoFbdD8tO14LbmYXjT9x9h
Ov2PIBEKYmU+w3L7f9P2UfjUqyOBw0IyO8yApSg1hQJBQoiS0M30+mxHLChcdiPV
q7j2OgVcWWaZ60bBV5VyibCGmwld/tDcFOvSV6uKT2Er5ct/DiJCCQAWAdM7PrZ/
Vv9SSPyVTC8S0AzbJRpr/F897T7Sm96OnpykB6VcY8GTx3G2DZm7tZNnG0zpOZP6
mOgzMNaOYVJqAmUtCtRfjjOfhiif9zC1lcrQgdbCxUJ6uzEOWgI=
=bmxl
-----END PGP SIGNATURE-----