-----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/jalu9uZGunHyUIFAmmKslwACgkQu9uZGunH
yUJ2zxAAuTbysgW05mwILOcdCu67148Oc0xqmsF2SqED/Rlb4lM6912OloNJM3Hr
UM00yeIpjcMFeI9zRMFyto2yssDKeLsI2g0T2y+avDIzD0wAAdpNLAGBize3frT/
WRxQH7PRFgu7P00oHXpl8cfXD5Q7AOjl0xX4XIPnZcBp5SYOlDEQHIIh6riL+DWQ
J942hRG1dPqgWuF8FaZTxEqW8FDR9sTxT96xjq4OtgxtDejuSpxV29taT22Kui0j
JOxvmbHQGGuUiK+O8wyHWnkfRXftwbdUCSWXFGtOxtbu9be3D4y3qmtS46k+r7cS
a5kMurah7UqhlR9XTt0zF+Xq1FQc/xDzaOqzCKPS3hflsKQQdLCFBMzC7HMuo8Ka
CUHBDiAWfiKixmCVdJjHGzn/TGdd1BSH84Y/5pBtaq6ojDZfJbZAWdcL/utN7Oxm
5F8itNCpfs474nc/GObVQwrK18vqTVyRwV3HG0SIgRhEutftFCYCgup5FbPO//VO
wTsYT0NYEcVw4E7qt+gYQaQ6yYINCtRK2jWRKX6aP8K+eZslSQWvVHz/skdhKuv6
tZqKg3uA8ARHr02LT2fxZ4QHJHeoCoPSa7ANU34J0LRGC5Q90srYG6Y4f08kYHKf
lJ9qtcj7OZsk2B3CcfSFIY1xLUfhN3PsvLZYPzRjpON6yyoT86k=
=ydTj
-----END PGP SIGNATURE-----