-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmkpZBMACgkQu9uZGunH
yUJi5w//f5pIKEvUwDwMCeyrqXdBVbe8LpF99qskge/ePmtmMbxwjpWWpET9oxGx
JagXtwiAJlJFkPkTc/j1sxVGAjxyJS/S1bgyruxcreXWwVkJE7Yh87uMV+zeqnUB
E7GZw3eCFyS4Rg7bsrUhS4LCyqCPeRPrIbHr9ggZ6WTiSZHA9Dcl+FE/lujeNbu3
Knw6jOTk/J1hCFc8HVhHUc8zAElgEWplzYO0Ex0xKrDkC0Ky4bPUdnVlj8YBi0Ho
wlSLiQTABSejRDmqHv+wIsSTyHyYgGinJztj6bN7Q6TVAapTlx7GOCaOEZkgDpdk
XpuyJNtZHMPFe5t1+686zLombAkWFQxTxBbBpZQiJUesGhWdguiUImUg9OiN1cKL
zDlNIO9VAwXK/nFp0HB+5+l85zQqyWUwzi3jQgRFhK/7qUInZxVISC+KLEjxZJrE
D2whKnfSIO0jia4ruZKNqrfu06g7n9JddZnx1L/1aZSaUPRuR6nUFHZegcPmHP8a
Evp8Una9VMBF1gdsmsp5ZR0xb4YqzHIxscdb0yrjBMiImnP72/Isfvg0v1ngN6w9
nKt4H1/aXE7eS7KD76r1l5KGqkxhcHsnDVWMi8xRaIQ9mw1H+fH+3aps1OPwkmcX
M4AuEt/j40S+5hLsaRyItWuH6Do4m6Qk4vgaToMeAN069rfrRG8=
=ty8a
-----END PGP SIGNATURE-----