-----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/jalu9uZGunHyUIFAmqcsLcACgkQu9uZGunH
yUJcdg/+MRis4T6YO5yadWH1aSPbzVynn+KrALhcfJuAWQU1UmjvuJkoY0kn305m
YiULXuGIBEfFTHG81QGy+rYC795JTzlqlnJ4kMbWKEZ3/lBLLjH53OmelkyQtJMt
QBBj3BX6fk6MMj4/6T4AkZmsIcIlGL0ufdkFkC6WWh0tenqzGxSDULYOfRz83hIV
mWhkUDlESJAKYlAzCeDl9khhdHQwJl1l9jCGdzT5FCLfJ9fjm5HDkTFbJnF1+gZ6
sB8aUnkHKWjdPgZRIcYnBGGNwCF9mEhMOapyULx8GLGP9ByOnk1Jflw1BRGxfSGV
HoivKEeI2qvzhJdECbqyYwc8MR0+SwngWLA3UYF3xN5d2kprtvr+rZLK2uDfAN5D
OZlkHN5lOdzetTBamdLKQo7vPqV/jiQ04WczQ1k7X8CEvFS3G0W8Vaebk8LPBp6A
L+lX5wdUWCu0/vsiYBowi+ItwDk92PXOnR8q+KH+TP/2/e8CwQDP9OlOwi5m/hSF
y73HTgAKQ527JF5NlHMaB5xcRzEO9HMDntIWItayyIf9GJvDlXWeIm+3nzLLtDU3
RmgkvBR7Xi5UE/nj+IU0kht6LlfenZ80vZLXUClAH3JsnGax9RTApmIn3OmDQOfV
WoZTzurA7Nt2qKjlFr8Eklmu8cVzw1mKdRu0fYuGk4Rix6/pOZU=
=wGQS
-----END PGP SIGNATURE-----