-----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/jalu9uZGunHyUIFAmpDNk0ACgkQu9uZGunH
yUJ+wg/+ObclGBxJpDlCppSS8xo/B63DHFLhWghRWxq2xe7DpP7xscNepFDoEqxF
kKKOzlLJm1N5FSILgJAZ0vRQHTzMgRHu4YLEg8XVtIdIySPV7n0Pfc66nBjx1Bja
0Td64E9l8P210jfpMz+wIC2jAbfx9y1Qu6o/yIKAOfWdssK+27O8tAkCGD8BqqrD
4PXMYvUZTjm714VjVTL+0Jful4q5t0SdwVQdklnfOdLXjHIbOAvWTeT4LkAUKxSW
RqFPWo1N8Q1gXTjjpUOsMz7Eh9rK0vYvuQ4LCuTE1nYztZN+/jViXcyKmSFqLdzo
k+eBKNGXn1dnIB8CRcB1lgJW2xnLk2I9Pc2FkoELEg2m5wWmg6nm/yB6AbJXDTNB
ARIua2zFh7VnHgfuG7ZIMDfJWM33u3PG7BnDCgpsudai6W9HlJWq1qFY6uhPfcG3
OFX9Si0qgwJHafpJHsFMM9e61V9DVlWeugdRdY3XvCkOXVpV9ezmhA//OMqafz4u
1RA4ENufwQlH4VwKkdwpOBjST2GxHojf0QZg7vmKXokMCL8KDLsShZiGzkXP9+iJ
XhSeTALyuHhES1MJEK/w4nAWmaurf13ufgelEQQymft9OO9afEmyYpAa7no/7AzJ
ltVrQXB1BLazk8ta58k9j5YcoWD2Bqk0wYVW0NckPW1iAKoh+tA=
=I5b9
-----END PGP SIGNATURE-----