-----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/jalu9uZGunHyUIFAmkcjagACgkQu9uZGunH
yUJHtQ/+MLHzXJ3/bHOJH7P6O4Fk+XEFEWEee26OpYeu8UlHIX71nHJI3iHD8eZn
Mq2QTG5fCpiNA3ujok0GZTE6yJE6utVHuE+QUfSbNYp5QFhReIWdgFMk0qA5VGab
Uykvsar07/4I/Z1IXBuzWLjpxCSyhoumRaI8Wv2MvRakQNhxdKK9WlMi3K5/rUW9
E9txZHWcvtrhT1WYb/aY0JiW0Nq+XDDE/MlF3WDjm5LMzp0rKG9kmJo/mWhyZkAk
APjhv7RM9QfyhdlwOU5EIA00pyM6YU64RVTv7yhh2kjn5uRzUAzqSyULXyFoFNlM
+OdZ5jbQrGcVFeILK+W62XXqOQkJ/QsrcLL9ff/Mhc7nsTDryGRtx8hzoSoTtyP6
7bPIEQZMpXBtdiwDe9vLExUbnv6GYhuQjw3aA8r0ybVxtIM0e7oYNc5BdUXuVcf1
x5t+vSQZX5416s+S0sJC4YxbEZJ9jykZMJzMzbaN7JJIPvLeFT/0g/KkpI43kJOM
FGuw3TFH+YyU3owteDTrnhV+x8Wa6ZEVkIP2i6nuZNd4pHOIISXNl8sx6P6jwWsy
wVWR0IJpxSnAwq0RJd5iejTT+cqla5wC3yo976KUfdfewlkMOHRO0WaVoRsxUhir
wemfWRx/3NWoGQ9z2FnSq59npjycd1uRu6vLnleSoo9oX1asnQQ=
=5MOk
-----END PGP SIGNATURE-----