Somebody please get a plumber over to Redmond, because there's a constant leak happening all over the place. What's on the menu this time? Windows 7, as per usual, this time in build 7106 flavor, both x86 and x64 variations. This is confirmed, by various Neowin members and other trustworthy sources.
The screenshot of the build isn't, as you can see, in English but there are apparently English versions that have been leaked, judging by the following build strings:
7106.0.090408-1623_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso
7106.0.090408-1623_x64fre_client_en-us_Retail_Ultimate-GRC1CULXFRER_EN_DVD.iso
It's unclear if this is the RC candidate build, or if Microsoft intends to progress further with their builds, but only time will tell. So far, changes to this build are unclear, but no doubt things will begin to show up soon enough. This build was reportedly going to be leaked a couple of days before it actually was, so that's rather strange.
















I was feeling silly.
Anyway, I take it this is now an actual leak, not a fake one like the one that had a broken digital signature?
That's what I was thinking, as well, actually.
Precisely. These leaks are proving very beneficial to Microsoft.
Free marketing, informal feedback that avoids the bullcrap and the end users actually saying what is and isn't good about it. Whether it is deliberate or accidental - I'd say that it is in Microsofts best interests with feeding the masses builds and getting the feed back needed.
Got me wondering thats or sure if so its a hell of a marketing strategy and proving to be effective to say the least
Yes, exactly. Leaking those builds doesn't cost them anything, the builds are being talked about and being tested a lot, and they don't need to support them - if something goes wrong, they just can say it was never meant to be released.
"There was some confusion earlier about it being 'fake' because the certificates generate a 'Could not be verified' error. This caused some people to think that this was because the certificate was invalid. This is because it was signed by a certificate stored on an internal MS Certificate Server, and therefore the certificate could not be verified by Windows, since it could not access the server."
From a post I came across on another forum.
Not being an expert on how Digital Signing in Windows works, I cannot give you a definite answer on that, I am only passing on the information I have seen. These guys are usually a pretty good source of information so I have no reason to doubt what they say.
This time we have a relatively short (?) testing time and only 1 official build given to the testers (7000) so far.
Anyone else think MS is doing these leaks on purpose? By that I mean they can't say here have it what if it just casually just got out like they have been.
If any of the official testers still wander around the NG you'd know how dead it is...plus they try to say these leaks aren't real with like 1 or two posts but everyone knows better.
I think the totally botched initial public release of build 7000 proves that Microsoft doesn't have as much bandwidth as people like you like to assume.
That, and bandwidth costs money; no such thing as a free lunch - they would do well providing localised servers instead of plonking it all in one location.
Not exactly, it's just that Microsoft (or Akamai who provides some of the bandwidth) decided to only dedicate a small number of bandwidth. Technet/MSDN downloads were fine because they are allocated much more bandwidth.
Macalicious: Akamai does provide regional distribution for Microsoft though I'm not sure if they did for the Windows 7 public preview.
It was poor management of server resources that messed up the public beta's release. The content servers were okay, but the ones handling CD keys just blew it. They underestimated the amount of people signing up for keys.
I still want to know who made the final decision about luna for XP. That has to be the worst decision.
It still was disgusting. The watercolor reminds me of the theme used in Office 2003 with the three-d'ish feel to it; the problem with Windows is the fact that each application uses a different widget kit which results in an inconsistent implementation of a given theme. It could be all avoided if Microsoft moved all their applications to the latest widget kit they've developed and leave everything else there only for backwards compatibility.
I used to ask myself the same question but then I started reading post after post about the EPIC "Ewww this new Start button is very sucky vs. You've got to be out of your mind this is, like, the bestest OMG Start button EVER and now I want to scr1pt som3 k1dd1e$ lolwth"
He had optical implants from First Contact onwards.
Maybe not significant in your eyes, but IMHO, upgrading to the latest build means I have the latest security patches and fixes... it's nice to have those just in case there is a serious issue in the previous patch. Understand now? Oh... and some people just do it to gloat about how they got the latest beta, etc. etc.
Todd sweety buns; where did splur said it was a bad thing; if anything I think splur is pointing out how ridiculous it is becoming everytime there is a new build and the hype around it.
Imagine everytime there was a the slightest kernel modification there was this amount of time - most peoples patience would wear pretty think by now.
It's worth notice there are hundreds of people involved in the development @Microsoft itself and many TAP partners with access to builds. Every one of these can leak it. Nothing strange for me.
I agree
Edit: Ok i have found it on multiple sites, BUT it is just the chinese one with an english pack thrown on, and chinese bits left here and there. I am going to pass. Yes digi sig still fails also.
English version has finally LEAKED
It's out there somewhere... in the wild
hopefully the original build will be leaked soon
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.