md5:
70199447bb412286ad66595c4e04f3d1
sha1:
d1947844576c7fda12ba6672376ee4e89ff9d32b
sha256:
ce113ef8179bf03fe5c17f1e50e59a22884d195522a3bc457cc54f741501f249
sha512:
475b69662383582a86138422f69de05eb5686a3373b50697df60fae0cb7007eaffa1cc52ae1e27a5ac0c4e900fbf854f22979a6c902a8faa05e2831598bb3b09

Use https://sourceforge.net/projects/quickhash/ 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.