-----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/jalu9uZGunHyUIFAmn1Fz0ACgkQu9uZGunH
yUIU7w//e7krmHGbBvE4hepmsHNyIYKcdfraSYxsCVTKulAGXConfywOAXk675vl
oeWET9/ENVlSShpNzTE8mWJ2eLZV97c2pgyVRTmo7OgUJ2FdyfQNC13ujnZjSYuz
ieeTkyLJK13X1/w1YmezYcYvH9uOOCxLlUhN+2EfhF5OE2fA++ehi7UmSeVIYJgd
/0+px+K0nun9EYI5UI/nVvxhQPVh+7WWm6/amVRaecM4czZpGNFZdghq5+t/pEMe
RspauLF0Fm7tWVUQcrUbUycrjLidBrpnDmCqHUpe0Yu0Qw1bhowxU3c6tT97MqVz
9Bz0asENVBMsJu4TVb1jUohA6ylHjARvZ5cpQrTnysaPCNT/x/+TeZ5hwK1oBrK6
WmTERMdLiiulI2mCATQu4HKqaskRQfD90vkMIEvFdzIU/kaR/ydlRwV6BUf8E7qI
u0yhiEraWSgZKBsXpQji71FsFN8XiqtMybCu5QyFIt5lktvEiUl/9wklXxMcPcrx
TX8RsHXbu0ajf6TRspaY377QKm/gp80ui0uOc940+mDj4+192yvvcGNEMJMzsea6
pjGjY01Qaa5WwdbDJi6Xnm1/NGcbUzohJKbDkkCpg3YhwOriP2KOOpnQwKaE/cJq
wKYc9TYo/WiNChiFQOAvG9QAmKsySr1HWdTI4rARttgb0f5ALik=
=G+aW
-----END PGP SIGNATURE-----