Leaked Screenshots of Windows 7 Build 7227

Windows 7 Build 7227 Leaked Screenshots

7 June 2009 by Vinay One Comment

Earlier we published leaked screenshots of Windows 7 build 7225 and it was expcted to be leaked but Windows 7 Build 7201 leaked in the wild. Build 7200, compiled the same day as 7225 so both builds are just the same actually Microsoft splitted the main branch in three sub branches. Hence build 7201 is newer than build 7225. According to Wzor Windows 7 build 7138, 7200, 7225 were in assembly line on May 29-31. Wzor is down from past three days but will be available very soon. But folks over sevenforums managed to get the leaked screenshots of Windows build 7227. But we are still unaware what actual builds are running inside the Redmond based giants. Microsoft announced earlier that it will sign off final RTM code in mid to late July with a general availability and release date of 22nd October for Windows 7. Here is what Wzor published about the latest branches in Microsoft Assemblies.

“ If you remember back in January at the time of Windows 7 Beta 1, we stated that there would only be one beta and one release candidate. At the time we received that information, it was completely accurate but plans have since changed internally. The most recent plans included the date of assembly of RC escrow, the date of assembling RC2, and the date for the final RTM build. More than once, though, we heard Steven Sinofsky say that there would either be no further builds distributed past RC1, or if there were, that they wouldn’t be available to the general public. At the time, no such thing as an RC2 existed.

As it turns out now, the build we call RC2 is internally released via a separate means: IDX (Internal Developer Release X, where X = Client or Server). Regardless, it is still consistent with RC2 but it is purely a private release for developers and partners. Here are some of the comments Microsoft has made regarding these assemblies:

“The IDX Client and Server builds are to help with final pre-deployment testing. They will be distributed to TAP and OEM customers via Connect, similar to the bi-weekly RRP audience. Timebomb behavior identical to RC. Limited servicing. Will reuse RC EULA. Same languages as RC Exit (EN, DE, ES, FR, JA).”

“In addition there will be a Client SP released to a limited set of TechBeta participants (delivery via WU). SP will be based off the RC build and will go to a limited audience but not necessarily under NDA. It will be a .CAB file that installs on the RC build; WU detection dependent on a reg key available from the TechBeta site. The SP is edition-agnostic – it would install on either Server or Client, but Server will be turned off for this release. A Sensitive Asset test pass will be dependent on whether any SA components were touched (TBD). ”

“This milestone is termed the, “Internal Developer Client and Server”(IDX) build – it’s an internal quality term we use meaning that the build is stable enough to deploy and evaluate, but may contain more minor bugs than a RC build.”