-----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/jalu9uZGunHyUIFAmkfqIEACgkQu9uZGunH
yUL69BAAgJX/Ylsy9xtHE7XI3RRozqSScqGxDGQ/M4lerIXWF7/KiIWkdGLWvsF9
h4vdr01/T4cdtdcdgKTQnzOtOEGS6wcJatO9q8Mo5dSEws1QQCsiNzLMNZg2t/sS
8hisl+JKAMjVMRdxOFvsb32oMQQ2VL1qHdshW8kaGZv1ZGrn08UIvb9wMrybguir
D33EVRtTksErUtNFTEotrki44pjQDNRais0eeaTAA95tCNRLdMQjrwTBbBh3oJZu
YCNgIgXrmHD9qJQTnrdmAEZXWoq3F2c+PefM/rQb8kAIs4T2okC4uHK9bAQ5rLNW
DmOiAtRxsYWnISkhw3DfX9lxoJqgIpJm0Nk/ElH39Z5MEGmJIJjh1gphklu1PNYj
tDoVKvaYyjJHaurE/XT6l3OzhYkmusp/4f9n4iOvOo5lByEMJzTgWdE0vxmBUhh+
wp4E+cXFARz0A3u3IklXmkRliGUUDmTkXPsGzvv0keKQgWYL1tQRAS/cuQYcReW4
yWgTLCJf7z72y1dyuHfJ8/SBV0Uju8rOuKrJiUvJAFBAesIhPCVPEARwDSSg3xJ1
zZm5849cgHJ+SH+QL952FFUQMtq2m3GZ/47d2DK3HGANOtgU/JbQPUaCIWMdmvVU
csSXKTX8f+3QNaqbJGzaCdrYeQB6ScFFwXFg/naJzX5KqyQACiU=
=zuA/
-----END PGP SIGNATURE-----