-----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/jalu9uZGunHyUIFAmq45GQACgkQu9uZGunH
yUKtow//dbxN5rEuuTL+dI/v2DTbDDwQyynH6bba4l1K5u2U9gfcwPquvHaKbCyc
iPo+krZLY6tDaG70pxNo2MJXT3vZdbwG8vbq4gJuGY/P0yA8TEuL+5Y0EiuMjpaZ
Addm2U0WB4ZSOaju5sLO2WdgfR7nXJomSaNPQs7JLlxs+eDrCCYBwT4FeOc3LaXQ
JDrXUg4WrIse/WcaWOerzfKRTYnAuTC46+V5ryySkVSBHfHvwK8544Sd3HDmvSaI
KOZMGlhzD24s7a2FVPJWtvtYklKI+qKK+XN0lW+5IE+Qm4GSKlQhd2Yp0JHM47Hw
Eru5j3lEEpE+bt0cwcdjxf9Y4PCtlv8HiQFb4NqeNJy0yv//FPj/nEmyKCOIjNp3
Wv3jCqM70KeZoB4kvGiFv8RHMqGpYjMYyAhH6niap/Lxd2M5A/NVYmi62q7Aca60
xCDDzKVa2JwR8fcjkDgzFSik/VwvrT08mMrBI4hCaZnsQocU6rEFeGP7gNvfOv4X
H5pkQx+S4Ki9Mg9/UW38lVWdRhz7Cze0JxqMGl+K4T50mgEoXZGK9Zc3ElZz6Ajr
4OVCFlShU92/cpjFs3kqg9MWCslkuHWrsrG7GLXHQ0vn3ZDr6lSTozSeVBaJxB9l
zYPnEZ+FFD+0OmFS3S2FdOPg/b2bCcIe6hzmlLxD2nDYeoQfTus=
=E3A7
-----END PGP SIGNATURE-----