Windows 7 RC build 7100 Download: Warning


Recommended Posts

Just a warning for anyone downloading the new RC builds of windows 7. Quiet a lot of the downloads have a trojan inbedded in the setup EXE. This should not be an issue if you booted from the DVD and installed, but if you upgraded it may have infected you.

How to get rid:

Extract contents of disk to hard disk then:

The Setup EXE is actually a container, it appears to be a self-extracting EXE. There are 2 files inside, Setup.exe and codec.exe

Codec.exe is the trojan. Extract setup.exe, and then delete the original. The setup.exe inside the container is actually the real install EXE, and I have verified it is clean, and that there are no other infected files on the disk. Then put the real setup.exe into the root of the folder, and build a bootable ISO with vLite.

I cannot guarantee that this Virus is present in every leak, but it appears to be present in a lot of them

win7virus.jpg

Edited by warwagon
ahh well that just sucks !

some people just live to be assclowns

Yep and the hysteria over 7 makes it an wasy target.

The MD5 of the infected image is 838F96D945C9554835A96CF41DEC9453

Hi Frank

What is the size of your setup file and has it a digital signatures?

Here's a screenshot of the properties page

post-286512-1240873271_thumb.jpg

Details of Windows 7 RC Build 7100 x64

Build String: 7100.0.winmain_win7rc.090421-1700

File Name: 7100.0.090421-1700_x64fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso

Size: 3.04GB

MD5 Hash: 8867C13330F56A93944BCD46DCD73590

Torrent Hash: CA767EC8 D2D07ED9 ADDBAE37 89C45CC3 5761E4C5

Details of Windows 7 RC Build 7100 x86

Build String: 7100.0.winmain_win7rc.090421-1700

File Name: 7100.0.090421-1700_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso

Size: 2.35GB

MD5 Hash: 8867C13330F56A93944BCD46DCD73590 (x86 only)

CRC32: E8A1C394

SHA-1: 7D1F486CA569EFFFFB719CFB48355BB7BF499712

Torrent Hash: C738F422D 6C36C36A 655BEFB3 21E51E4A 2C84B7EE // A4835C20 4C7FC504 704C9376 73A8762A B9F2E761

Details of Windows 7 RC Build 7100 x64

Build String: 7100.0.winmain_win7rc.090421-1700

File Name: 7100.0.090421-1700_x64fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso

Size: 3.04GB

MD5 Hash: 8867C13330F56A93944BCD46DCD73590

Torrent Hash: CA767EC8 D2D07ED9 ADDBAE37 89C45CC3 5761E4C5

Yep, the MD5 of my ISO is different.

ahh well that just sucks !

some people just live to be assclowns

Unfortunately that's true.

Below the specs of the original isos: if the check sums match those of your isos you've got the real stuff - unaltered.

Windows 7 RC 1 Build 7100 Compiled

The build is correct. The rumor is incorrect. The RC build 7100 was leaked and it is the real thing. Here are the CRC32 and SHA1 for the authentic ISO images.

7100.0.090421-1700_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso Size: 2.35GB MD5: 8867C13330F56A93944BCD46DCD73590 SHA-1: 7D1F486CA569EFFFFB719CFB48355BB7BF499712 CRC32: E8A1C394

7100.0.090421-1700_x64fre_client_en-us_Retail_Ultimate-GRC1CULXFRER_EN_DVD.iso Size: 3.04GB MD5: 98341af35655137966e382c4feaa282d SHA-1: fc867fe1ab2e0a9796f9e4d155b44ea6998f4874 CRC32: 58fb2be0

PS: You cannot upgrade from any WIN7 Beta release to the RC1 (unless you manipulate some registry keys) and there is a good reason to that. Some new features are not compatible with the beta releases.

Unfortunately that's true.

Below the specs of the original isos: if the check sums match those of your isos you've got the real stuff - unaltered.

PS: You cannot upgrade from any WIN7 Beta release to the RC1 (unless you manipulate some registry keys) and there is a good reason to that. Some new features are not compatible with the beta releases.

You can just edit cversion.ini and it will upgrade fine. No registry key editing. The windows blog had information why this was done.

How can we check our MD5 hash keys?

This thread has me worried now and im sure there might be a few more people who are going to ask how to check as well...

I have attatched an application to this post for you. Put kukubau's MD5 appliccable to your ISO (X86 or X64) into the top box, and then locate your ISO, it will compare the hashes and tell you if there is a mismatch. Note, I still haven't checked the X86 but there are definately a few narked X64 ISO's floating about. However, having scanned the rest of the files, as long as you haven't installed the build by launching setup.exe I believe you should be safe

MD5.zip

Stuff like this tarnishes torrents' reputation of efficiently distributing large disc images. Obvious solution is to get the torrent header file from a trusted source (for instance, Canonical's servers if you were to get a copy of Ubuntu), but that won't hold with large corporations like MS.

I did run across this same problem in an earlier leaked build. Lesson learned: check to make sure setup.exe has a digital signature intact before burning or copying to a USB drive.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Honestly that feels even more useless than it did when Win11 was first released. In 2021, the uproar was somewhat justified, but only when comparing how good we've had it since Windows 7. Prior to that, a new Windows release would often require new, or very recent hardware. Windows XP wouldn't run (in any usable way) on hardware released when it's predecessor Win98 was released (let's ignore ME). It was time to shift the goal post, and the way Microsoft did that was actually ok. People have still had another FIVE YEARS of free software support with Windows 10, and those of us who want to have used these tools to bypass the limitations, all while understanding the impacts that may have. Most laptops don't last 5 years (sadly), so now the youngest unsupported hardware is 9 years old, and apparently has another year of support with Windows 10. That's good. Meanwhile, understanding the impacts and limitations, I have my 2013 laptop running Win11 perfectly fine. The thing that's failing on it is the hardware, the 2.5" SATA cable/chip is failing and corrupting the SSDs I put in. Thankfully it has a functional M.2 sata drive that works fine!
    • iPhone 18 Pro drop-test video and photos leak on the dark web following a data breach by Hamid Ganji iPhone 17 Pro - Image via Apple Apple is seemingly facing one of the biggest data breaches in its history, and just a few months before the official debut of the iPhone 18 Pro series, photos, a drop-test video, a supplier list, and key phone components have reportedly been leaked by hackers. Last week, we reported that Tata Electronics, an Apple supplier and iPhone producer in India, was hit by a data breach. As a result, it was reported that more than 200,000 trade secrets and confidential documents belonging to Apple and Tesla were stolen by the ransomware group World Leaks. According to Reuters, the group has now leaked supplier lists, component details, and photos of the upcoming iPhone 18 Pro models on the dark web. One of the materials leaked by the hackers is a drop-test video of the iPhone 18 Pro, which is due to launch this September. The phone is shown in a gray color and has the same familiar design we saw on last year's iPhone 17 Pro series. The device also appears to be quite durable, though it seems to be thicker than last year's model. One possible explanation is that Apple may be using a larger battery in the iPhone 18 Pro series. Moreover, Reuters says it has seen at least six documents mapping many components in the iPhone 18 Pro models to their respective suppliers, including details on chips on the main circuit board and on battery and camera components. The documents reportedly detail hundreds of parts that will be used in the iPhone 18 Pro models. A person familiar with the matter told the outlet that Apple classifies this data as sensitive and “is concerned about the documents being shared on the dark web as they relate to unreleased models.” Apple is reportedly investigating the issue but has yet to issue an official statement.
    • You do you, I've just said that it first appeared in "home" version before it will be available in "work" one. I use Edge only because it still supports MV2 uBO extension even on Android - I'll switch when they stop.
    • I imagine that was a review or something? My reviews mostly contain a lot of images and galleries, but these are all webp too, but yeah it all adds up on the page load. Would help if you were more helpful with your critique instead of bitching and moaning like a Karen 😂 Because then we might be able to fix it for you.
    • If Valve refused to let them make the case, I wonder if they've already partnered with someone else to do it? The fact that they didn't seek permission/licence before diving straight in is incredible though
  • Recent Achievements

    • First Post
      rosiecharles earned a badge
      First Post
    • Reacting Well
      Juan Dela earned a badge
      Reacting Well
    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      273
    3. 3
      PsYcHoKiLLa
      142
    4. 4
      Steven P.
      100
    5. 5
      macoman
      54
  • Tell a friend

    Love Neowin? Tell a friend!