-----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/jalu9uZGunHyUIFAmrEOZQACgkQu9uZGunH
yULwuQ//WzzM1xgMKZWB1dGv6DZBrLhRsn61TwK60YHjn3zFCSL4hjh5qr4dTaPR
EIdK7rP7SSDiW2Wt+IGRPea1BBcARDhPkwb2ueKMNbTDhwENqE87be6WYTF/emK+
kbj362w7fhNo6wtB5QFSVlju1KvrQ5EFMnqDPb9+jIGyRba9TTux5Gdy6dEXjYEa
+xKmappHkkVy4Fz9WY260npiu+zA0T4uik2CHS9Y/QbXCA/PF+Y9nrlKRg5El/TX
M+hMGDh45/9RPlN9By1o0X9O885zlHVIjpITDIQcMkgKY5T77/nD3jJ+LrQgI5w6
M19GacWsHRx8u/a7LGT3Uo8VMazz6C+60E+9LGxopb6XX7r8FiVs4fqfxs+W9HCY
UPxWiDh87c5SIK4iOO4tHW2i478l3ktDXlZaEV4WZNreD2+iJ+Uy5hUvSFE4AHwH
qEqgEGedeLBqVrBMSRo+H9KVDkuwlvA0rGnujvI+SOwtinlP/hHqOqi/DnyTSW37
n7umaWPyh8YlLZ2+jVmQNhMpY564sZJ9Ox5sp6fbtRqZXBLw56tXH2+EpwekvHXZ
suCYbIycdGZnLGI2GsPdlJGDgscja3M1CVpgLtwmYeQlnUR6VAOCMBiMx+qA+95M
lpyquhmdJs2+L73yA1O6LZ6l8UXwHXyttoWuGbAjHKVFZZw7ztU=
=G3J/
-----END PGP SIGNATURE-----