- Feb 22, 2007
- 16,240
- 7
- 76
Title changed to reflect latest build 7077
This should be the RC 1 build expected to be released on April 10th.
7077.0.090404-1255_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD
They are telling people to not do an upgrade install from previous betas with the release. Only clean installs or install upgrades from vista.
So if you have a beta installed and lots of stuff to back up I would go ahead and get started
This information was released today and for all intentions it looks like Friday, April 10th will be the release date for the official RC1.
Full info here:
http://blogs.msdn.com/e7/archi...pgrade-experience.aspx
edit:
Title changed to reflect latest build 7068.
32 bit and 64 bit are in the wild.
32 bit
Size: 2.52 GB
MD5: 9dbc20dc21e09f926c530799918215a0
SHA1: fd1f67a2727fe6aaf1c141ff34ae9af77a24a172
CRC32: 26312514
64 bit
Size : 3.23 GB
MD5 : dee5eb9c8cebd02dc3c4e6a91627aa3b
SHA1: f663ec7785bec5d75220dd73cba4d75d5449a76a
CRC32: eaf4001d
How to use MD5 to verify files:
http://www.fastsum.com/
Original posting regarding 7057
------------------------------------------------------------------------------------------------
For those interested. This is the same build I got from Autodesk two days ago so it is legit. Only difference is mine was x64.
X64 can now be found in the usual places.
http://news.softpedia.com/news...-Download-106605.shtml
This should be the RC 1 build expected to be released on April 10th.
7077.0.090404-1255_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD
They are telling people to not do an upgrade install from previous betas with the release. Only clean installs or install upgrades from vista.
So if you have a beta installed and lots of stuff to back up I would go ahead and get started
This information was released today and for all intentions it looks like Friday, April 10th will be the release date for the official RC1.
Full info here:
http://blogs.msdn.com/e7/archi...pgrade-experience.aspx
We?ve also learned that many of you (millions) are running Windows 7 Beta full time. You?re anxious for a refresh. You?ve installed all your applications. You?ve configured and customized the system. You would love to get the RC and quickly upgrade to it from Beta. The RC, however, is about getting breadth coverage to validate the product in real-world scenarios. As a result, we want to encourage you to revert to a Vista image and upgrade or to do a clean install, rather than upgrade the existing Beta. We know that means reinstalling, recustomizing, reconfiguring, and so on. That is a real pain. The reality is that upgrading from one pre-release build to another is not a scenario we want to focus on because it is not something real-world customers will experience. During development we introduce changes in the product (under the hood) that aren?t always compatible with what we call ?build-to-build? upgrade. The supported upgrade scenario is from Windows Vista to Windows 7. Before you go jump to the comment section, we want to say we are going to provide a mechanism for you to use if you absolutely require this upgrade. As an extended member of the development team and a participant in the Beta program that has helped us so much, we want to ask that you experience real-world setup and provide us real-world telemetry.
If you do follow the steps below, you might run across some oddities after upgrade. We experience these internally at Microsoft occasionally but we don?t always track them down and fix them because they take time away from bugs that would not only manifest themselves during this one-time pre-release operation. From time to time we?ve noticed on a few blogs that people are using builds that we have not officially released and complained of ?instabilities? after upgrade. Nearly all of these have been these build-to-build issues. We?ve seen people talk about how a messenger client stopped working, a printer or device ?disappears?, or start menu shortcuts are duplicated. These are often harmless and worst case often involves reinstalling the software or device.
So when you try to upgrade a pre-RC build you will find that you?re not able to and setup will tell you and you can then exit gracefully. You can install as a clean installation and use the Windows Easy Transfer feature as well (run this from your current installation of course) if you wish to move your accounts, settings, files, and more. To bypass the version check, the instructions below will use a mechanism that is available for enterprise customers (so we are also testing this as well). It is not a simple command line switch. We didn?t make it multi-step on purpose but wanted to stick to using proven, documented and tested mechanisms.
These instructions will be brief. Since everyone reading is a well-versed and experienced beta tester you know ALWAYS BACK UP YOUR MACHINE before running any OS installation and NEVER TEST AN OS ON YOUR ONLY COPY OF ANY DATA. Testing a pre-release product means just that?it is testing and it is pre-release. Even though this is a Release Candidate, we are still testing the product. We have very high confidence but even if an error happens once in 1,000,000 we want to make sure everyone is taking the precautions normal for a pre-release product.
One other related caution is INSTALL ONLY OFFICIALLY RELEASED BUILDS FROM MICROSOFT. It will always be tempting to get the build with the ?mod? already done but you really never know what else has been done to the build. There?s a thrill in getting the latest, we know, but that also comes with risks that can?t even be quantified. For the RC we will work to release a hash or some other way to validate the build, but the best way is to always download directly from Microsoft.
Here?s what you can do to bypass the check for pre-release upgrade IF YOU REALLY REALLY NEED TO:
1. Download the ISO as you did previously and burn the ISO to a DVD.
2. Copy the whole image to a storage location you wish to run the upgrade from (a bootable flash drive or a directory on any partition on the machine running the pre-release build).
3. Browse to the sources directory.
4. Open the file cversion.ini in a text editor like Notepad.
5. Modify the MinClient build number to a value lower than the down-level build. For example, change 7100 to 7000 (pictured below).
6. Save the file in place with the same name.
7. Run setup like you would normally from this modified copy of the image and the version check will be bypassed.
edit:
Title changed to reflect latest build 7068.
32 bit and 64 bit are in the wild.
32 bit
Size: 2.52 GB
MD5: 9dbc20dc21e09f926c530799918215a0
SHA1: fd1f67a2727fe6aaf1c141ff34ae9af77a24a172
CRC32: 26312514
64 bit
Size : 3.23 GB
MD5 : dee5eb9c8cebd02dc3c4e6a91627aa3b
SHA1: f663ec7785bec5d75220dd73cba4d75d5449a76a
CRC32: eaf4001d
How to use MD5 to verify files:
http://www.fastsum.com/
Original posting regarding 7057
------------------------------------------------------------------------------------------------
For those interested. This is the same build I got from Autodesk two days ago so it is legit. Only difference is mine was x64.
X64 can now be found in the usual places.
http://news.softpedia.com/news...-Download-106605.shtml
Windows 7 Build 7057, a development milestone officially labeled as Release Candidate 1, has followed earlier releases of the next iteration of the Windows client to torrent trackers. At this point in time, Windows 7 Build 7057 is up for grabs for all users with a BitTorrent client, just as the previous Win 7 Build, namely 7048, which made it out of Redmond and into the wild. However, 7057 is not served from any of the Microsoft official channels, as the software giant is keeping mum on the development and availability of the first and only RC of Windows 7.
Delivered with the following build string 7057.0.x86fre.winmain.090305-2000, Windows 7 Build 7057 was compiled on March 5, 2009, almost two months after Microsoft launched the public Beta of the operating system. During the installation process of 7057 users will be able to feast their eyes on the first mention of the RC label in relation to Windows 7. The End User License Agreement for Windows 7 Build 7057 reads: ?Microsoft Windows 7 Operating System Release Candidate 1,? as you can see from the screenshots included with this article.
Torrent websites are currently offering just the 32-bit version of Windows 7 Build 7057, and the leaked release is accompanied by the following information: MD5 2a3863afe3453d1be642201fd3260ab2, CRC E34E099B, SHA1 0f32dfe92d544f4690ab91c02b59dba665d4ca0f. The Build comes to the table with an entirely new logon screen, and will permit users to run it well into 2010. The expiration deadlines associated with Windows 7 Build 7057 indicate that the development milestone could live until the end of March 2010.
There is no telling at this point in time whether or not Build 7057 is in fact the fully fledged Windows 7 Release Candidate. Microsoft is certainly hard at work cooking the RC build, which is planned for general availability in April 2009. Still, despite the EULA mention of the RC, the actual Release Candidate development milestone could have a superseding build number. Still, Windows 7 continues its evolution, with additional changes implemented on top of what the software giant integrated into 7048. Windows 7 Build 7057 features changed UAC settings, reflecting modifications promised by Microsoft a while back for the User Account Control, but also new wallpapers, new logon screen, and fresh imagery for the personalization of user accounts.