md5:
2fe8d9fa15845e685720832e45f150f4
sha1:
93638372fc81469a9f9918d5d9d9ab8e7eff8bf4
sha256:
a7551f70e774eedc171b582a514603f6ecf173dacd5739b6334b16eb7b6c7236
sha512:
af0fcdaad86dc0c110e9433e3fc36338374a3ee733b56f04af5e009a501f3ca573833c76eab860207dbced620ff5d25bee1f251181c6fd02c75e5840f977dbbf

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.