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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmqffgEACgkQu9uZGunH
yUIUWw/9Hi/1BGA9hRBtxDaOxo0LBFMXql1cxshBQOi9STQK05EoLAmd6TeSbzih
xGgHM0+et5mbgeAhXRHUzEuJHLMnWyXk4JiN85pue+rLsr5IZbWB3kOALbh8a+Gu
pQg8QqFdH7orqva023EePSk8/E7fBxVmtYlXSBFfEf1sUoDdWZojvU7FUBbg8PJS
lQKAq8aeKMX5m0zOmYH6cAj5VhzhlhEPy+LFHXdmFCb5iQxCn2IIQ2Ymbg8rDNqH
kg+irlUDF0fiIUVjP8te7AzxZpY7U3ObMUsxTpCOD2maM7UmFAysu1idmuKVdZs0
gO/oQmEf0tCC3/j0UmPj4UxjHxl3ywlrKVqKUnhnGVSzdrmR8ljS9G3NVR/G2uwx
3TFNQHVaXOtDNpWvJgW81LccaWh9oAms51GUjNnpSZZTlL40JYs+welbe3Ee0xTV
Mut0+qPmFmPN2r3NPFJziaMRyLMFAOK2xmQHxxZa2rxrNI635Qo5xSrxbh5ovTwv
BGE+ioi7s4HHrGUvXWz4eAgnsvPUsOVONeOuHKPuenvxWSSDfQ/kUVo/mB/mypHu
KjFwblOgrkKzuGCAzYAIXJlB9SXrcrdFMQQYD3UEGmunHqejqkVSvURtlhydStSI
mESPveiIO4MFrgNmrdkDdbxzDJLyfgtS5+Ar5ztbGrHgMYjkJHQ=
=eUB7
-----END PGP SIGNATURE-----