-----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/jalu9uZGunHyUIFAmqmNrMACgkQu9uZGunH
yUJcMBAAtmdgusI1jZwCwFbnPN6ER8UcLpuDOG6FyMn+G2Sq1mTnDLUNbt1EGiqp
fMV+qZy+BAABybmCWelr5gj910THhFS3W7/J40vL5XCneRB9ffYUgC0VIQxz5dY8
nUHMzC26zGO9ayiSeWBXmA2AmTKxJx+v2aw0s2QW0ynuGr4QDUOuRXQPf4JGlWx8
tSmdur0Ew/S8mZ25BIRTzLqgtQ5o8NShR3L3tqwLNzJdbK7RFtC1rzi7wfIVKAJs
UFByExHxHyX6uKjsWnzHirzP6ZCQPYFbonwD4C/7cQgaQosfI7bgYKh7be7sRes8
7H2mPes5zFPnrvaKxIboP9La6TlkNHhkUwfnLFWr3G4fa6+Qe/KTJzOh49hXYYzA
sFuupio0BZx5UVZFm69QRMICBTnVcHiBD+LIdRMOaVIRaUxGOQa06hxqvwELjc/L
n5W3C4ZlaAhx08kpoorVXFOtaphB1jUlfu2cV/V+kHnizWGNgoFEHdv9NRqSxwOX
NHw2RvWBTkr17StlneuUNUdfutcjEJij5s1EalETAza5I0ZPiwv76e1mc4pfIkR2
Q+0F89iwwD7KfWPgd5FDZ/Sbbr5fkjI2FhUsQRhD7fBzkCND6kVn+ZPSM2PZJesR
aemS0gvI8i4G/KwimrelzoX6dRM8WqXuXmQd6QC+ZBlQ9quiTpY=
=xVPZ
-----END PGP SIGNATURE-----