-----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/jalu9uZGunHyUIFAmnV6R4ACgkQu9uZGunH
yUJdbg/9HETcYDifS8+g26bjvI4yCEY3yHEwLSv+AA57DSvkWFle9/vne0u7Np90
0VqLAKbMsHOYFUuxLZQ4j2fh3xpS9fJD/5pnMNfRFZe7nTtH1sGpYKcuP8ebZbzn
ak5Vz+0RQYbjMJU2xZ80v/4DoS65qh1KkxEfnbNSOUzHWbBMYYElJYMvAu7A/QyW
KpPKIAhVFtxm22DsZWw8QbhflE3FOMCYeIvrrsqTb1y9ERn0ZJG1jFZwfrNOARmj
X9bwhLpG1AR+7eZuKPODhBPYVrCh75Nw1Cjw4ZtPtHV+KwO+6B+y7XCVFHnJwxz/
gpGyw4DZXyjdZhWTI78/MkkCdND23niaQZzix9GNzt+8keMSXxUNWh5sjAI/cTbI
s+ungl9nE68yc+m90ICDblitGXfiZKwU5jsiqXoTtrYiSS67n3gURLrXOTAbZpWh
Jz1ByGeqEmDHjjW79qzV7dojbwrI7IdrCDvg25VDYfYkhHnHNz9dQ/ZN1arMV91J
Gx4E0yl4hMA+V/C4imkZkvkPZvev+xEEAsXz+kMY91Qf0WIj7pUJ/lpnnV3hb8z/
eb1luE0cUS5Q2AlYnKn66Qb6olR97lPjtxQ9jxAPhYsLVVeBmWMoueCY+mzj4gdi
+5lSTCcb8GwE1tbPA5mh2Smq5zFsypmRsvOm73XHVL9VdQRMysU=
=ySAt
-----END PGP SIGNATURE-----