-----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/jalu9uZGunHyUIFAmnjzfAACgkQu9uZGunH
yULtWQ/+O3E8hbdwZNMTYTImwR+EBo7AU+4xe4Dt7QcMUibzKAX7HKZCPM0KUcYu
YzbBBz5dCkKsAdfKD0t+Zuyq373oKZi699rsGId2wuaUHvXw4MUbwhc76r0TGdCj
Uh9MJD6QihXqgsVgOFAQZALTA9npQ1t0mw3E/tm6lAGd+XZpm9pcWL7rOffpr9Ky
cZMNxmnLxsNyvaYVq6kmTLipqZBvRgnWwi7mrw82QjCso/2aimY08yrt0Nprz05P
PCTsURqDz2PyEWrJ96eK1C66jozuMU3TBaUZsY8Yh1vF5DQqmA6V7MEheTY54LvE
7J7sGPZFqql/X+VtP6j8exQs4If4NuQG9UVZ0kZ+7S5XBF50GAPYu+dfnfmIHvkx
ReVRvdz/T//IBApNHZGukHX9Y4Q+Wwt/yMNS0g7iTttOap3sOWYuFUsczUf8cKSU
j9RG/lHlNiWUDpiyzSq25V77tsjpQacKtQD/fBWt2CStlCNN4xq0sbl06FLHcaYy
RArYFfza2yfh4k4zp5jHaH5Vfer3rTu7j/UIZDmXFgtsm7ZC3jaUKM0mQZNP2R6j
3BvepaV1FV50xenBUmaZjKKmjuBJf7DE7wsqT6UW5WVniBesLAZV3PmKFmq2TYJb
B/OeYQPwyCdtWOM2ZvvJZcfo+0/c8JdGrfsOTYbUe9xdfWlEDns=
=AEMS
-----END PGP SIGNATURE-----