-----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/jalu9uZGunHyUIFAmo0GDcACgkQu9uZGunH
yUJvXxAAp9R3HzPC55f3DW/NuxMHxanRGP/IjIKcgTzXYfL3WOPV3UXEcEscJ6x3
74VEn8Rodfz97hx4fz0rHiqwuE9bPqM9eJik45sldW/OVU1S9/8roqKskMI2ms5S
niOKcMdElh1CqpZMJLhI84Nknt8er1io2WR2SK9PrzUPVfAiOZhSQm2ec1eQaqtI
SyogHN7P/FffaLxBJtSQiP6/J3l8FGnP/t6E/FnxOQuqUGwJ6YurSnqGeeiLxKUv
X0ylxU6nm6dU3VAHne8bNfsWHp63alwuW995aBTkQLXTOzMXR/XuVWBOKqUKnOmP
uOJQixwiqG2DUdFo2CXubTvcdb/RQTXhDPUlvKWGBKoyA9DPyotS72YHTVra/zzl
4kDu5JCsjUgV44k4L2lYDfZr/4HdVJLzkjPjPQSc0QW6m2hEq3H3kOUf2JS0OYk7
6CMMxCuL+GfLYx/ujL7ZlTocsyf+VccriqC/OuqYtfQRWQlxzn4/TNMxtKs7H0/n
W5IOdbkYsvRzI2guRWzsjCvceTsuk/eoPxJd2X8+HVgS2YdFfzNwy1BVt/J7VWV0
lwZ+ADtqtht399j6++OC66y2PVjt3FZ/HdsVYA7ld76CE82DS4IeNHUsgEuwHtJq
SEaco1m4pIUwWx3MwhjPEqk+YYWSnBMPgBZgOrX2e4xz1yDb8dY=
=KN9B
-----END PGP SIGNATURE-----