-----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/jalu9uZGunHyUIFAmn6bmoACgkQu9uZGunH
yUJsvw/+IuUws1f22+1o9VsZLOETIG2uZ5FsQ75p5KBlD8ajx6PFNNOJiQYKV5gT
2DwhgoTqNQhzfWms2qCpw6GrvCPoZ72vgqHlwVBm4oT0ylsuKtrSCIj5FwJuNd9w
RpK6iTJ8ffrBR0ccLJzfCm+g6uOIG0HzBD2ikoFv1nEErEwcS1jwv+VEUL4MLCic
tANcYr+hbF3Ghq3iJzdrZq8lCiyeLoutNkUkIUXBWnbLue2dPzTWJ6MGtISsvwW0
ABWmecwZJbtZThdchp/x7sJhu0T88ReLbDWUujQCKdXpyIlOqAPVmr4I2f+A3cUo
DU75LkzeKEYykzhYoI2sBWc7YrFBcXBaj6Wg2OHZ5vDZGeG+ugdD66SFze6CzMQl
kZUYO+uN5Bkr4YOEc0MIgQVvtQhmStrYBav2+LGnB0lhc9TuW1pgQ0mL9N+JOWXe
duk8PFW1iESRTrMbaqpyKA+Z2qGe1tR8U4b0NcauYmqVyeYnuLKi+KW4uWJg3o/w
Ez5smx5nD0BKBB1WfkRFhIwQo1MbK0a4EP95mjd83mlI355yMQeNB2N0AZkUHVWN
Nd0ZRQihW+N08S+8MbiyNMKPbsLQC1FN/ZyOhYP/ITXBXxC1HlS3iRERyz94C77l
r/UUg0YxdL3aQwNJEcAckuhGoeJOC4ZhWQGpnLRVfDTqMFG9894=
=NNUe
-----END PGP SIGNATURE-----