If geeks love it, we’re on it

Windows 7 build 7100 leaks

Windows 7 build 7100 leaks

Details of this leak are still rolling in, so we apologize for sparse details. The only thing we currently know for sure is that both the x86 and x64 versions of Windows 7 build 7100 have hit the internet.

Some people are claiming this is the release candidate, while others are understandably suspicious of the claim. As we learn more about the build, we will be sure to update this post with additional screenshots and verified information regarding the newest leak.

For your immediate viewing pleasure:

Windows 7 build 6.1.7100.0.090421-1700

Windows 7 build 6.1.7100.0.090421-1700

UPDATE: 4/24/2009 @ 3:32 AM

Amidst the leak of build 7077, Microsoft implored users not to upgrade from a pre-RC interim build to the release candidate. While no logic for the plea was given, the company did confirm that it would prevent upgrades unless users modified the cversion.ini file located in the Sources folder of the disc. Users who wished to move forward with an upgrade were given an unsupported process that involved changing a line in cversion.ini from MinClient=7100 to MinClient=7000; this procedure would trigger upgrade eligibility for pre-RC builds.

Exploring this file on the build 7100 leak, however, reveals a stark difference:

[HostBuild]
MinClient=7077.0
MinServer=7000.0

Either this build is not truly the release candidate, as the cversion.ini does not jive with Microsoft’s unsupported method, or the firm has changed its stance to allow a small subset of users on build 7077 to upgrade cleanly.

UPDATE: 4/24/2009 @ 10:39 AM

Reports for build 7100’s user experience have begun to trickle in, and two things have immediately cast suspicion on the build’s legitimacy as the release candidate:

  • Multiple users are reporting ongoing issues with Windows Media Center. Obvious bugs like this should not exist in a release candidate.
  • Many users are reporting an expiration date of February 3, 2010, while the official release candidate is not supposed to expire until June 1, 2010 as per Microsoft’s statements on the matter.
  • The feedback tool is absent from this release. Microsoft bundled the feedback tool with January’s beta and has repeatedly cited it for providing invaluable data for Windows 7. It seems obtuse that the release candidate, a critical stage in the development of an OS, would arrive without it.

Comments

  1. BuddyJ
    BuddyJ Wonder what the changes are with this build?
  2. Thrax
    Thrax As usual, nobody really has any idea.
  3. MiracleManS
    MiracleManS Isn't this actually the stage when things stop being noticeable? I mean, the major changes are done with and the majority of it is bug fixes now, correct?
  4. Thrax
    Thrax At this point the OS should be free of any obvious bugs that arise through routine use. I just added an update based on reports of Windows Media Center glitches that shouldn't be there.

    I'm still not entirely convinced that this is the RC, but I just report the facts, so whatever.
  5. MiracleManS
    MiracleManS I was talking less about it being an RC and more to the code escrow phase. I was under the impression the major overhauls had completed.
  6. Thrax
  7. MiracleManS
    MiracleManS If that's the case, it's pretty interesting that WMC is borked to the point that users are frequently experiencing it. Especially this close to the purported RC release.
  8. Smith There are no new changes in the build aside from small bug fixes and one thing in WMP and maybe some desktop wallpapers.

    This IS real.

    You can download a ZIP file of fifty screenshots of this build: <a href="http://w7info.com/articles/2009/04/windows-7-release-candidate-leaked/&quot; rel="nofollow">7100 screenshots</a>.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!