Engineering Windows 7

Welcome to our blog dedicated to the engineering of Microsoft Windows 7

Delivering a quality upgrade experience

Delivering a quality upgrade experience

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:

  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.

clip_image002

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!

THANK YOU!

--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.

Leave a Comment
  • Please add 2 and 3 and type the answer here:
  • Post
  • Well, it took a while, but the upgrade succeeded. All I had to do was reinstall my 802.11g/b PCI desktop card drivers, as well as downgrade my display drivers from 8.15 to 7.14 so I could run Second Life.

    Simply enough, if you're not sure to try the upgrade, Windows Easy Transfer, or just a normal file backup, I'd suggest using this method if your resources are limited like mine.

  • Oh, I forgot to list that I'm running an HP Pavillion 6010n with an Intel Core 2 Duo @1.80 GHz with 1GB of DDR2 RAM, in the form of two 512MB cards. No graphics card, just Intel Integrated Graphics. I don't really have an external drive big enough to extract the ISO to, so I had to improvise.

  • I was curious if there is or will be an upgrade method for a transition from 32 bit (Windows Vista, XP ) to 64 bit Win 7?. It would save a lot of folks who's pc's are 64 bit capable but were sold 32 bit OS's for more competitive pricing?  

  • i let windows 7 install over vista and shoving vista aside... i allready deleted vista off my bootlist. so windows 7 now has a XP/7 multiboot menu... well all this info is just meant to draw you a picture that windows 7 isn't as pickey on what harddrive what partition and what state of drive you are installing...  i mean what i did to my pc is a nightmare for software. (and i know it) so in a way this is stressstesting win7 all the way imho :)

  • The save took a bit, considering it makes an entire backup of the file under a .bak extension despite the fact you only change two numbers. Once it was done, I just burned the image. I still have yet to test the upgrade, so I'll let you guys know.to help install Windows 7 on a different computer I have. I have been trying to get in there again for at least 3 days with no luck. Is anyone else having this problem?

  • I have now switched RAID off and installed Windows 7 onto one hard drive, it's not ideal, but I suppose the other disk can be used as a dedicated page file!  

  • it came out on technet i downloaded burned and wacked the dvd into my main machine, wich HAD windows XP SP3 and vista on it... i disliked vista a whole bunch because i had failures of hardware (nvidia drivers) and unsupported hardware of allsorts

  • but if you don't have a flash drive it does not work. I'm talking about "ReadyBoost". In vista I could install it and get everything right and the thing would still suck back gobs of memory to like 900 megs of memory then after a few min fall back to 400 megs of memory. I KNOW WHY BECAUSE WHEN READYBOOST DOES NOT HAVE A FLASH DRIVE IT USES YOUR SYSTEM MEMORY INSTEAD!!!.

  • One problem I have found is that running this OS on older hardware means that hardware that used to be able to play even the most basic of games won't play much anymore.

    In my case, this is a Dell Inspiron 8200 laptop that happens to have a GeForce 4 Go 440 (32Mb) card in it, and on my Nlited XP installation, it runs Halo and a few other D3D games fine, but on 7, I get problems playing any game, and it complains about not finding D3d, but DxDiag says it is running fine.

  • Having deactivated RAID, I have newly installed windows 7 onto my HD, and to be honest it's not the best situation, but there is one perk - I suppose the other disk could be drafter in as a dedicated page file..

  • I'm trying to upgrade Vista Ultimate 64 bit to Windows 7 RC 64-bit but it fails. I get OK on the compability check. Trying to find a workaround...

  • Does anyone have an idea where I can download the beta version of Windows 7?  I would love to try it out.

  • The beta version was available for download at the Microsoft official site quite a few days back, but the offer is closed as of now. I tried a few days back and couldn't download.

  • I am waiting eagerly for the official release of Windows 7. You know, so much is being talked all around and for the first time in a long time people are expecting good and real hgh from a microsoft operating system. Its great to see MS starting something from scratch and going the extra miles to build something new and having features never thought of before.

  • Windows 7 is going to be the next BIG thing!! Everyone is waiting eagerly. So finish the work soon guys and present us something awesome.

Page 7 of 20 (294 items) «56789»