-----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/jalu9uZGunHyUIFAmoP9hgACgkQu9uZGunH
yUL+cQ//dUH/8d5/7oMzwKPyR0pgY3mRwEgSzAqXxtkPNK29txGpTjwFU3CsgWch
L/x1826gt35KsPCGZSngGtV5V/bqn9c7rbOwXgJVSYafhcoWbMbk6npn7PXj0vFi
SfXWjYmhn0bzxFIdvPDCCdOk58gUv2MiMe9YmifhjZTvc2055ROI4sYp0CM4KXxW
xvF2CyC50eyMy5sawZK2NuFZ3t8Y/kCKFUcSAGvy08s2SYBGTVoI6EkPBibEZmPL
xz1Zh825CvZuAz/A9iPhb3ixDl8fC2qg1ZaNyqQqQlQE83oJYF+TaI8RjmuzYI4A
ykV6hDO8CwDuGynYygrqB6ja5Ktynkl9BnVU6L1uuZdx3CN4gSI47VkZo0aUJbbG
lL041c9yqnlJVe+Hn5jWfLJ3t2+p24s2Fi/WMWctvjpP23UvJjPHIYA2MM/MXNof
ltCebSxxxss+ePupDvPQjDi0re6SJV13XNkNjk2EruxaPUTAwA9tL+I365F3L+/F
O7SJgvtOw3Zx1gvbcnesijBH2lgbanL3/olcpTWCxbJwF+kaq/RnI11wwfNsjz3X
L4zGxJhOu04leMkD7xINamtMRe5Iyt+ZmTMOqxIdx62IibkNW1Bbd7ZRdqyRWzYx
juKVBr/B2zuVyNi6FOwAHkyK8aNO2rK37AAN/hn2ik9pZLL7+dI=
=pQgo
-----END PGP SIGNATURE-----