How do I know if a Windows ISO contains any malicious software

>>60179836
get it directly from Microsoft?

>>60179852
he doesn't want any malicious software you nigga

File: ramen.jpg (65KB, 529x768px) Image search: [Google]

65KB, 529x768px

I have a friend in India who works for Microsoft

He called me the other day and helped me install the windows activation program. What a gentleman.

He even helped me enable an LED light effect with my laptop. There's a white LED light just next to the webcam. After he configured the lightshow, it glows every second. It's beautiful now.

>>60179836
Check the SHA1.

>inb4 collision
That has only reportedly been done in a highly controlled environment. It *should* still be okay for at least another year or two.

>>60179836
>We don't know what the SHA

There are SHA1 checksums at MSDN for all microsoft related ISOs. You don't even have to log in.

>>60179995
>Op mentions SHA512
>Moron counters with SHA1 and talks about collisions.

File: 1493548095487.png (698KB, 929x675px) Image search: [Google]

698KB, 929x675px

>>60180030
They all ask you to log in.

MSDN doesn't allow anonymous downloads anymore.

>>60180075

Learn to read. I said there are SHA1 checksums at MSDN. Click details and you can see the checksum. Finding a torrent by searching for that checksum should be trivial.

Case in point:

https://msdn.microsoft.com/en-us/subscriptions/hh442898.aspx#searchTerm=embedded%208.1&ProductFamilyId=0&Languages=en&Architectures=x64&ProductFamilyIds=547&PageSize=10&PageIndex=0&FileId=0

>>60180510
They could just paste some other SHA1 in the torrent description, you fucking mongoloid.

>>60180551
That's why you check it yourself, you fucking idiot.

Hell, why are you even torrenting it? You can get it directly from Microsoft using the Heidoc tool.

>>60180587
>He trusts the program that reports the SHA1.

What a moron. The whole reason why they invented SHA512 was so it can't be faked.

>>60179836
Scan the signatures of the system files and compare it with the origain