-----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/jalu9uZGunHyUIFAmoeUBcACgkQu9uZGunH
yUKABw//YrnuVLepl3cklf002H48EOzGq4lQ/HUnQB+Y2ch7uFb8vxRrD7TAjKjl
kbbq0j1UXx1L9a+QDGP5gKKLJebKliKys7gTPso6ZOFYjvPF4YQWgAjChzwBbT+f
yKet6dN56LAcqaFnOLAC0XNh0Vnka/J56vXBbFxtYdWeDztN+COzFQlvqUqllbL2
l5OydWgZ9goVLBON5JjG/5gY1yi6XNXPSM8RKrwUTqLfbCrCFyws317xhQ3/hdI9
azH/qlc7TM61f2A0FpvVxeCbiOkTIoONaKYBZnE8CB5ZdcslSlBSSx3CwnGkmssl
RY/lY3VeirRWT/R5ksRdSaqa+OM8q4dmRFEuUIXLAbO0Vtjz6gudi+BByMTc0bqB
oZBISVcnOEIixhOcQVmcnRLeBsNqvCpLkabIf/48jHbm+TTUS6r2LyJsvzPad/9w
MhHX+rT3FziNpqGc+tCnWHZGGK6B+umQ+Xf/F57UhUIqUys7QJJ/YfGykOvPRO/s
5veCwo5BvJLa2nrAoYBiU/fNh4LfOWvQkfN30pPll0t4/mOkQHbWG9hJdyc1EmJQ
1hDfnXMPldi/WS28AszCP/e8A0OXUVDJMXR42pL6fIyFoT6OjPTU4hZNkVte71hs
qItrilly9cYe0HuhHZaWHU9CbTnJfS0S063o1hLpw3ebgwRHimw=
=Z4hI
-----END PGP SIGNATURE-----