-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmmnfPAACgkQu9uZGunH
yUJpeRAAu972TRSLOdxDHMbn2YP4qNLNo6eFVGH4OpUFwsoTgRNu5ZAysnAekW15
kA6LOPS77VahMH9pohaFn6moSll9S+ktP4qOf0y+IEEHsf0nZCjXd2arqAKjHyJ9
3VzL47Z4UoqZjVX7WOMFlIyw060x8PRy1849+duP7E6nn8NqssJk0mceFCBgFg4h
DqtvzB/FeUt4Q/se9hTOk/0fMFFuxtCPVmSZoIs79O8GFMAiP9JP61cTcal05p1a
E+E0ojI60JupFc1d3SRblKtZEEqwzynNjhIXmB0YqJjWl/h/5CeOiYD1coNKQy4N
Mq26X0KtbrqhyCQmH2iVm12esq43Y45u/ls7cOwbXueZJRVBiYHDRCs04GeO0Lj3
rEOOXSGaufX8hi+KT1MENHTj0k+IN0aahTQPLQYlVIf9Plr9O4rTiQF6mAH/3ath
2IxplaEAZCTdzVNu4rlLgZk7DMvWTrrMo1LBK7aVts9Rv0nj4Oc4+jBlhvuJAQrs
khR7ljGQq1nlbqzVy8y0u9kd2m3dp38+M+dhxm/649+3CzPpe3MMRJDYbK2MD7Bw
PZseBPIsN/uvqs5NjpUDE0gQmVQ9unj0EXYXjkKpYZhoNB1Uo6JSC8C0Su9Jb8Ug
rdNY8pQB548DnTtY0iDr06VqBbLE2FxikkIPwH9DukMAlycePkg=
=qabK
-----END PGP SIGNATURE-----