-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpAf7UACgkQu9uZGunH
yUKsAg//f3UcqlF9jWnUadijA1as19sTvTTU6VhmtEOXv8es8vr6CmJ/KsaNbouy
DjtSrG3OUtZFNu7vzwvLfRkhuw7sg07ggdweYHa9RqUx/f8IzRDNPnOUJvpAvBcW
N2ZGqnm9hR0bVKr59S6aKjqUMM8A8XK2lA3DzKsRdH8ufXfp0HFDnR+usLgXf6Gn
dYweAF9nvifhsoFJGbN21P3lrqQ26lOUsNNTvgs/0CZC6xK+4qOlq7MjZyW8djm1
UaBmh1x1Gtdk1Lu/5BSv9v2RllyMDqfx7Alaanq6jXi9NxdCEhvsNQNR0QR95Nyh
Wr0yNN3d/k3wrsudlGQc0QXKTFWB6yx3rhEaKJcGZcsaEyFanAdEOVHFwxLdv0ti
+NHvoTkyRlU2kZWtYOeTL8Q8hVpl+z3Z7UpVcABxogb7KhJEug1BQfPM+0uhDlcD
FLG0KCc5B3ADGc9nOFIwZ/rFL9pp67CyXmiEj6yxXL4rvoempsOOzZFHEHnFL58Y
hfTK9r4/Rp7uXCWX2+FZKX7ILmInHB77sqjZwg8HnPrty4vVXRmyJk+T6zQ+TDCm
j4bqe/8lqx3lmDPZigNk35im/aJASFzGOc4cFZvCwNJhYG/UoZuZaA8hiC31PqYx
VwCn+bmnG0QxbLO9XZbVyZ91cYABPbX90HAp+GHZwrULgfLDLN8=
=Ga1u
-----END PGP SIGNATURE-----