Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

System Manufacturer/Model Number EXOPC, custom desktop, custom media center, HP laptop OS Windows 7 32 bit both Ultimate and Home Premium CPU Varies per system Motherboard Varies per system Memory Varies per system Graphics Card Varies per system Sound Card Varies per system Monitor(s) Displays Varies per system Screen Resolution Varies per system

Keyboard Varies per system Mouse Varies per system PSU Varies per system Case Varies per system Cooling Varies per system Hard Drives Varies per system Internet Speed 20Mbit

Im sooo glad i checked my hash's, once realized they were diff, download from MS and wiped that bad boy clean. No probs. Just goes to show.
Not worth the risk for a couple hours download, given that 99% of people have sensitive data on there computers. 2 hours of your life is worth it. and stops the ' holy sh** whats happened. If only i reinstalled proper' scenario

Any new/popular/wanted software is at high risk of this type of thing, it happens a lot these days and most people i doubt even realise until there paypal accounts are emptied or purchases of digital goods start appearing on their CC bills.

1) If MS knows that these are "Infected" - give the hashes for the "Infected" builds -- we've all got the hashes for the Official builds so it's easy to check.

2) Say WHAT BUILDS are infected. Microsoft has been burying its head like an Osterich in the sand even refusing to ACKNOWLEGE any builds other than the BETA 7000 and the official 7100 EVEN EXIST.

3) If this stuff has a botnet / trojan in it publish a method of detection -- some people will ALWAYS use stuff from "dubious" sources -- and in doing so can transmit stuff to software obtained Legitimately.
By just saying certain downloads might contain a Botnet etc without publishing methods of detection etc is just being PLAIN IRRESPONSIBLE.

Information such as saying "XXXX" might contain a virus / malware etc doesn't actually help ANYBODY and merely re-inforces the perception that they are just scaremongering.

If your build matches the Official one it WON'T contain anything it shouldn't.

Of course with the Official RC being easily (and quickly) available it really doesn't make any sense to download it from a torrent -- but that is a TOTALLY different issue.

1) If MS knows that these are "Infected" - give the hashes for the "Infected" builds -- we've all got the hashes for the Official builds so it's easy to check.

2) Say WHAT BUILDS are infected. Microsoft has been burying its head like an Osterich in the sand even refusing to ACKNOWLEGE any builds other than the BETA 7000 and the official 7100 EVEN EXIST.

3) If this stuff has a botnet / trojan in it publish a method of detection -- some people will ALWAYS use stuff from "dubious" sources -- and in doing so can transmit stuff to software obtained Legitimately.
By just saying certain downloads might contain a Botnet etc without publishing methods of detection etc is just being PLAIN IRRESPONSIBLE.

Information such as saying "XXXX" might contain a virus / malware etc doesn't actually help ANYBODY and merely re-inforces the perception that they are just scaremongering.

If your build matches the Official one it WON'T contain anything it shouldn't.

Of course with the Official RC being easily (and quickly) available it really doesn't make any sense to download it from a torrent -- but that is a TOTALLY different issue.

Cheers
jimbo

Well said. Again, I request that if interim builds are released, that the admins stick a Hash Thread in the sticky session that is read only. This thread will track known good hashes for each build released. Someone with access to the "real interim build" and is known to the admins as trustworthy, can verify the hashes. These trusted folks are doing nothing wrong by providing a hash value, so they are not in danger of violating their NDA. Provide both MD5 and SHA-1, so that we can compare both. (I'm cool with just the SHA-1, but to help the truly paranoid if both match, it is impossible that the files are different).

I will probably stick with the RC at this point, but for the others that need the latest and greatest, this website can provide some security and keep the malware out.

1) If MS knows that these are "Infected" - give the hashes for the "Infected" builds -- we've all got the hashes for the Official builds so it's easy to check.

2) Say WHAT BUILDS are infected. Microsoft has been burying its head like an Osterich in the sand even refusing to ACKNOWLEGE any builds other than the BETA 7000 and the official 7100 EVEN EXIST.

3) If this stuff has a botnet / trojan in it publish a method of detection -- some people will ALWAYS use stuff from "dubious" sources -- and in doing so can transmit stuff to software obtained Legitimately.
By just saying certain downloads might contain a Botnet etc without publishing methods of detection etc is just being PLAIN IRRESPONSIBLE.

Information such as saying "XXXX" might contain a virus / malware etc doesn't actually help ANYBODY and merely re-inforces the perception that they are just scaremongering.

If your build matches the Official one it WON'T contain anything it shouldn't.

Of course with the Official RC being easily (and quickly) available it really doesn't make any sense to download it from a torrent -- but that is a TOTALLY different issue.

Cheers
jimbo

Quote: Originally Posted by jfar

Good post and I agree.

Quote: Originally Posted by PhreePhly

Well said. Again, I request that if interim builds are released, that the admins stick a Hash Thread in the sticky session that is read only. This thread will track known good hashes for each build released. Someone with access to the "real interim build" and is known to the admins as trustworthy, can verify the hashes. These trusted folks are doing nothing wrong by providing a hash value, so they are not in danger of violating their NDA. Provide both MD5 and SHA-1, so that we can compare both. (I'm cool with just the SHA-1, but to help the truly paranoid if both match, it is impossible that the files are different).

I will probably stick with the RC at this point, but for the others that need the latest and greatest, this website can provide some security and keep the malware out.

If you get really desperate try this NEW version of W7 -- you don't need ANY AV software either or even bother with such mundane things like keeping Online Bank passwords safe -- this version will store this stuff everywhere on the Internet so you will always be able to retrieve your data from any computer on the planet at any time -- The worlds FIRST UNIVERSAL OS.

Pirated Windows 7 Builds Botnet with Trojan

Getting rid of a pirated copy of windows 7Hi,
I have recently been stupid enough to let someone install a ''genuine'' copy of windows 7 home premium on my computer and now it has all gone wrong, recognising that my copy is not genuine and insisting that I activate the account. Unfortuanetly the system restore does not work and I have...

Installation & Setup

Windows 7 Pirated version to Legit Win 7 ProI have a computer with a Win 7 Ultimate 64 bit operatiing system. I have taken hours setting it up only to find out that the win 7 product key was already used on another computer in my office. I have an unused Win Professional 7 64-bit I want to use. I tried simply using the new product key but of...