-----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/jalu9uZGunHyUIFAmrBbv0ACgkQu9uZGunH
yUKFCQ//du557V4QYZbHOgyECNuh2Fgk4eLnVfQGytX6EdExYC05MHeHOuo88ehu
W3kQdQkyac6nA2+cJJP+Yia3bqIfZuG/DxWut8uzhawK9AkGHCD+JSUhHRzYFrY9
imD0Xfoz8PoXRJuJFKgraW6tO64DR7gjzZvUIklxgIzOs5v/lYtbZTUhlB514Ia4
MX1xWCqXFnHiqGrYJaeBGrQIpNac9u3mEtPpPxauuDg9QZ/Iv4wUuquAbEhpwj/+
Vb8htzecha3LvVZw0LRItDEGW/E8eVi+Z2tz8khpvp8bUjdxOk9h1NBC0Zhh8whq
NdZpi1UWqEqdXwSKHagkgAQO40jlQasd2cq1ZvEM36ksSFtQAgn/xn5VhQs7UGbs
u1RIHVOcNvNkuhtmRpYhQZOxClTI2N4bVjVsSRuubv4Q+EFn4QjCZyK3yYEbAwx7
tmdbu7clifMePG36EaWHQTfUAxEC/qpeUHFRucfJB0rb+RCALmCvrK71L8Jg3LGi
wl9zqZpx5SmP6KJkdu+Oo3piJkbKHe2sZ+SY2ugyTV3rk1b4az9044ouEQvB3VFT
WbhGf2+oUzFR2hcCWGdwn5c+T9a+Qv9gHbWR20lkmLv142VWjpMz7QODpfw+0qdd
Wzzoh82EaoXC+VTQ/QAbOqXNAXVnt8mupwdPO6o11bNBxENZn0M=
=LteH
-----END PGP SIGNATURE-----