-----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/jalu9uZGunHyUIFAmoFoUEACgkQu9uZGunH
yUIxQA//bfpUtGMmN9Cl6ctsIV6MveIuGAEU8jETjTqNou9uyOiQe6OS7v85xHH7
uZzhKnku2r0eKRqUZKCm84LV8TLcYLY+xEQCyEGfZwdqt+zPkROtKtv6UeOrMJch
VuE+XWFn3SWDc7IYStMAe4K/qGAYOBJoixgRVtaPS6oTmL4l+yWe3zl5r4E0W39W
Y7xFRwNIiJUdyxMw6EFl4LYFuPmd1p1/AWIahzxhrdYydUaLu5rUQqvBa1WOfLxs
foKtldsYirN5F13Tr3BKo62UJ3PdfTYa7nwR4+lU6P3wyc0e3b4+Cc/xuJeLZQO+
nCb5aETEWY0QfocdQem2Vp9FVDXVRfMYBDeYi3qiRvoo403zXd6gN8VfHUUTrQQC
T8FR6G3nnUuAd62OmXFUtswpF8OVl2tPBDwbm7iCgQa4AemZMTd+w5xcU4lon/F+
KwlL+npQnVbKK2Vqv6HelLIozfOE/ER+4mgIsId2U1cqkQc02ma5Fti8NtW54zM0
32uaoCd0L56ZpLz7yewIUTsWvIxQNaJ83ICxoOyccYQn3+cAmFTWUd9KyRgMjiP/
AYNRI1VGw3RSvg8F2+FNezs0J0boY8bVpC3o6RRxWfwMUPQ+zMHdo4bdq6Z0WGOB
85YjEbxkE70OWPuJSxWZm5blRr0v+7wQtobd1W8xOf9z1Ka82Gg=
=Bwbr
-----END PGP SIGNATURE-----