-----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/jalu9uZGunHyUIFAmnlpqEACgkQu9uZGunH
yUJ0HQ//XXwWbEIUmcK07RJpZNDChSJqfyjljQdmFGMLNOjUJOKkZjVkwP1hKAfS
V/+5B2ewp96xVOwEOyT4CQzJk8R4lyKCh6tZ4+LVl24v2KSmQxizrhpDxkyOzzwY
62+H4gyE5gcG852f7e80q3NxzEq2ZwZ06eTP11X2iNATGCk8zeJLyjCDGHigrCrx
Im8RRd4BxqlaWxBL8C4mCwg0KPaADFzIzHk4qO56yoFGtfVAXcyUf7NHTQM+kfBR
rceqxptdUAjY6UBYqmIJ+bd7HcbslrPHgidT+FkVWQKbFokAQNzdb8bs0CyyDwqr
2uRk9BqKwuHBwqIc80NyJjLqD0825bT8s5cY73kEJxqWRdx4waeHQqqErcE7BJzW
WOn3P1WUA93GeYVFmcn4zkTruS6ie+K9lGPTFS5Up4SYv9Ik71iyiKVq758OK4D0
v1dWR5RhTsr3Hp0v9r4NOxEUocwsNDEO80sL8bzP4NJrYbGKS3EBWwU7B4uY3TmH
ZkYNjmVWO1v88tSNGk+9Y3/zfCzc66obhZxQ0iC/9bI3GJCYzu24H7HQY4XFNSzs
VOodZr7723C9maeUBQ62YfFC2AUnuKzwx6twBmgofc/cqZo1B128SUxF11jFm7e5
ykvK6opLj2msb1h/5UoSZWAAw232gIcQykdfCNI2rO9CDrYGwGU=
=A6Ok
-----END PGP SIGNATURE-----