Notes on comments.
Welcome to our blog dedicated to the engineering of Microsoft Windows 7
This is a little bit of a tricky post to write because we’re going to be asking everyone using our Windows 7 Beta to help us out, but doing so is going to take a little time and require a bit of a commitment to helping test the next milestone. This has been a remarkably valuable and beneficial testing cycle for Windows as we have had a tremendous amount of very rigorous testing and usage. We’ve had millions of people install and use the Beta since January and as we’ve talked about, the feedback and telemetry have been of tremendous value as we finalize the product. The effort of Beta testers has contributed immensely to our ability to deliver a high-quality product to hundreds of millions of customers. We continue to follow the plan we have previously outlined and this post is no announcement of any news or change in plans. Since we know many people are running the Beta we want to provide a heads up regarding the behavior of the Release Candidate (RC) as it pertains to upgrades. Of course we are working hard on the RC and following the schedule we have set out for ourselves.
A big part of the beta process is making sure we get as much “real world” coverage of scenarios and experiences as possible and monitor the telemetry of those experience overall. One of the most challenging areas to engineer is the process of upgrading one release of Windows to another. When you think about it, it is the one place where at one time we need to run a ton of code to basically “know” everything about a system before performing the upgrade. During the development of Windows 7 we routinely test hundreds of original OEM images from Windows Vista and upgrade them and then run automated tests validating the upgrade’s success. We also test thousands of applications and many thousands of devices as they too move through the upgrade process.
Many of you installed the Windows 7 beta on a PC running Vista. We received that telemetry and acted on it accordingly. We believe we’ve continued to improve the upgrade experience throughout the release. Similarly, based on our telemetry most of you did clean installations onto new drive partitions. Through this telemetry we learned about the device ecosystem and what drivers were available or missing. We also learned about PC-specific functions that required installing a driver / application (from XP or Vista) to enable support for buttons, connectors, or other hardware components. Together we get great coverage of the setup experience.
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.
We’re just trying to be deterministic and engineer the product for the real world. Speaking of the real world, many have asked about upgrading from Windows XP. There's no change here to the plan as has been discussed on many forums. We realized at the start of this project that the “upgrade” from XP would not be an experience we think would yield the best results. There are simply too many changes in how PCs have been configured (applets, hardware support, driver model, etc.) that having all of that support carry forth to Windows 7 would not be nearly as high quality as a clean install. This is something many of you know and already practice. We do provide support for moving files and settings and will prompt at setup time, but applications will need to be reinstalled. We know that for a set of customers this tradeoff seems less than perfect, but we think the upfront time is well worth it.
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:
These same steps will be required as we transition from the RC milestone to the RTM milestone.
Again, we know many people (including tens of thousands at Microsoft) are relying on the pre-release builds of Windows 7 for mission critical and daily work, making this step less than convenient. We’re working hard to provide the highest quality release we can and so we’d like to make sure for this final phase of testing we’re supporting the most real world scenarios possible, which incremental build to build upgrades are not. At the same time everyone on the beta has been so great we wanted to make sure we at least offered an opportunity to make your own expert and informed choice about how to handle the upgrade.
We’re always humbled by the excitement around the releases and by the support and enthusiasm from those that choose to run our pre-releases. We’re incredibly appreciative of the time and effort you put into doing so. In return we hope we are providing you with a great release to work with at each stage of the evolution of the product. Our next stop is the RC…see you there!
--Windows 7 Team
PS: At Step 1 above many of you are probably thinking, “hey why don’t you just let me mount the ISO and skip the plastic disc”. We’ve heard this feedback and we deserve the feedback. We don’t have this feature in Windows 7 and we should have. So please don’t fill the comments with this request. There are several third party tools for mounting and if you’ve got a Vista image there’s a good chance your PC came with those tools on it.
Try XP start menu in Vista or 7 :
VistaStartMenu 3.15 (freeware)
I couldn't agree more about this one - it literally keeps me awake at night (when the laptop sits there flashing the hibernate light when I've told it to shut down).
I've got a W7 beta on 3 PCs in my house, and I love it. It would be nice to be notified when a new beta or RC came out, with a link to download it rather than having to troll for it.
Update on this OS, it's ready for RTM.
Thanks again for the hard work, my customers are even impressed and are enjoying the Beta Experience.
Also there are absolutly no conflicts or problems with VS2008 and SQL2008 unlike some early builds.
This product is great
Why apologize for not providing an upgrade path from Win7 beta to RC? This sets a silly president.
Most of my Win7 machines are dual-boot. It makes good sense for beta testing. (rookie beta testers should take heed.) I am a “clean install” guy anyway, so MS won’t BE getting any “upgrade feedback” from me. (sorry)
What I would like to see is the Win7 team working with the WHS team to accomplish this:
I would like the WHS Restore CD to provide an option for doing a clean OS install from ISO image stored on the WHS box(I have Daemon Tools on my WHS box, but it would be very nice if the WHS team would incorporate mounting ISO in basic WHS functionality), and then be able to select a back-up set to retrieve just the data from, as part of the “restore process”. THAT WOULD BE VERY SLICK, as often times I would prefer to do a fresh install anyway, when resorting to restoring a crashed machine. Why restore to a previous STATE if you can’t be sure the state was good at time of backup? The data is the important part. Managed re-installation of the program files would be cool as well, as this would help get the machine back up and running in a more timely manner. I believe that this would be a viable option when restoring a PC in conjunction with the WHS Restore, and would allow for keeping fewer back-up sets.
It doesn’t seem like this would be a difficult task for the MS teams to accomplish, if they would work together on it. (Win7 & WHS Teams) It would also help convince more people to invest in upgrading to Win7 along with WHS.
Thanks for all the good work, and keep it up!
I am having a lot of trouble when visiting this blog lately.
One out of four times the site doesn't load at all and instead gives me an error message from the server apologizing that right now, there are problems so it cannot be loaded.
Three out of four times it loads extremely slow.
Anyone else experiencing this?
hey team :D
Easter it's ok?
We re ready to final test :D and you?
Stupid question guys, but out of raw curiosity:
Will the fact that my backup drive in XP Pro is configured as a Dynamic Disk mean that I will need to lose all this data and reformat when I switch to Win 7?
I can't remember the last time I did an in-place OS upgrade, they just don't work. All you get is an unreliable machine and you end up wiping the thing later anyway.
At least that's what I thought until Win7 offered me the upgrade from Vista and I thought "screw it, why not" :o) I was fully expecting to have to wipe it after a week, but the idea of not having to reinstall all my apps and all the laptop utils I can't live without was just too tempting. Anyway, long story short, I'm glad I took the gamble, even freaky things like the fingerprint reader that I thought would *never* work without reinstalling have just worked. I was well and truly surprised!
So anyway, I'll be doing an upgrade from Vista to RC. And not 'clean' Vista either, it will be the backup I took before I upgraded to Win 7 the first time round.
Nice work guys, can't wait for Win7 with a stable IE8!
Saad: OK tried it but it only changes start menu, not the taskbar...
Just a quick suggestion. I have been archiving some decade-old stuff and been using a lot 7zip lately. It struck me, how cool would it be, Windows 7 offering built-in 7-zip support. Better, make it an official Windows archive format.
Eagerly waiting for RC!
I haven't installed my Windows 7 yet and have a couple of quetions is all. I have Vista Ultimate, intel (R0 Core (TM)2 Duo E8400 processor, on my computer so I am debating what to do. I have the following programs, not installed yet, Windows Server 2008, Hyper-V and Virtual PC 2007. I have been thinking about installing Windows 7 as a virtual PC on a seperate hard drive, usb. I have 5 PC's at home here that are networked. I just finished my BSIT/software engineering and am now going for my masters in information systems. My question is, which one of the above would be the best to use to accomplish this?
Ideas please, thanks,
Were is Team?
Stop new thread?
It's obvious that the TEAM 7 is pumping up for MAY 5...
I can't wait!!!
Still hope for always refreshing thumbnails in the superbar...refresh just the window where you look at the preview right now...thats enought...but what brings us a PREVIEW where we cant see whats going on when the window is minimized...please let the window who is shown as a preview right now refresh the content...