-----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/jalu9uZGunHyUIFAmm+jp4ACgkQu9uZGunH
yUJkIQ/+NaueFw2bGSDnOedR6tGs+9CSndffXODBDcwdyd7PUGc9mDt7DSpmIVZO
toJ1JhuTL/A63xhK0oJeUd/zANXZwAQoqvTRAJD9zrWHCb8jKb32O4X+9/1vcbH0
jHvcyKTnipJCBsHLtbmnyB+A7DEf9Ye3cesgOyDWZsMvt1JNN03coRa55vNEbd6d
JLzde2YLjn+sETSkCuB8VDMX4nzvdaXzjIS6Twk/wlagZ4zc643wc8XkEAXky0Qb
SlyJP1CMJiaHWTFfW2+qXi0MKDPZEC93NS+B9Qo8X6tgcsfby+Dr863Rjxuumtln
dLmXdU3ilq2DpngeSQzy/NO+dToG91uZ5EtORlh3VpZkkLJ/3rvvwMwTVk4tPB/b
xXRgLEqFB/LiRRP516X/bYnyDqX2N9ZP00U424SbZOk/24rAQljCGASIvegsK+Si
b8N5fDlmUog5HeiVb3ab9KdtHkptNVoQYRbpOqWCjmzYckWUXeiFzK+aQVrkFUGQ
IBrMu3iOLDs4+yvUjuDjNGlEpXaV/T46vLyme4DuMnix+Oo2KUXATothAz31Rc+X
XXgjQILcTsBAkHsTIoJmQFibJxZiixZmftbRQEHdE52N+un+5gYXWTbq4EG1MqN2
BE/UR6NvvKmhI+M2HWygTMeifmvnsQ2aqQzldA2LNvkl24TqlEE=
=ibd/
-----END PGP SIGNATURE-----