-----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/jalu9uZGunHyUIFAmnNTLEACgkQu9uZGunH
yUK+KA//Rcfr3fpzoiioWosV1nUugOePhY7+vRWaW8Yk78R0h1COyHumrQ3lbySm
Y+WN0akAmnODZYUmOfBPVNGIRm4ANfR6G5OpaGSWZbHqvma1ekf2Cg98OXQZm5rH
Hy6cBUCn5KWZb3OGfkuFAPQMsl3kdgrxWd+LRvXVof14tWaWTl2m0tct24G3UcFt
OoObtOSHkDSiVWtRvVvlumTkgHbfT0+dMU0YSBz4B+/vIECEixQLyz6hpFBe9kz5
+jC2Q/qLvVEmoXH/klfbC8SOXCvaThB9dETOAE8kVkfOlKAm27p8FWbIpZpD2Ile
dlBUVe9v3mqgd4iSPRO9r9XYghABDiGsIF5uWmJmpyvBJZMoD5weFUFIhAcvRbSb
TKET5Gz4gW6fkRWcrrejcdGvmqkW/XdWt0TMnYqS3rNuAuJhwOjvI5rogCb4wh0B
ghXEUBXrJULQJYMJi7nLFo8keT7ek2IUM8jjzZfCXPsBPhdgbzTx6AIhHyH4Iqez
qMH+xBoRGMgJDacXl7u8YaurVFb/6XiQq3owCWnCGfyei/Hh9EhLBwbQYeMVVlx8
QOy1Z0zmaWfC3EIFCanvWJvpJdxOK6PX4ldC5C/RGiLnlhaSMteZJ4tMkfYWV/Qq
AHI5GyBpUeWajzK1ma8F29LYzZChWvySFxsqR6AXL6y3BuS7Gs8=
=rYqL
-----END PGP SIGNATURE-----