How hard will it be to move to the Windows 7 Release Candidate?

How hard will it be to move to the Windows 7 Release Candidate?

Summary: The Windows Easy Transfer utility is greatly improved in Windows 7, but it’s still missing a killer feature Microsoft promised three years ago. In this post, I explain how you can use this utility to move your data and settings to a new Windows 7 installation and ask the question that every Windows user wants to know: Why do you still have to reinstall programs when you move between PCs?

SHARE:

Windows 7 head honcho Steven Sinofsky published a post on the E7 blog last week that outlined some changes beta testers will face when the next public milestone is released. The most surprising news was the official announcement that Microsoft will not support upgrades from earlier builds of Windows 7, including the official beta released in January. In fact, the RC build, which is due to be released before the end of May, will block upgrades unless you go through a fairly cumbersome seven-step process (which is, helpfully, documented in the same E7 blog post).

There’s good reason for shunning beta-to-beta upgrades, which can result in unusual instabilities and glitches. As Sinofsky noted in his characteristically exhaustive post, Microsoft doesn’t devote any development resources to tracking down bugs caused by these scenarios. When Windows 7 reaches the marketplace later this year, Microsoft customers will be getting the new software on a new PC, or they’ll be performing a clean install or an upgrade from Windows Vista. Those are the migration paths that are actively being tested.

The officially recommended strategy for upgrading from one build of Windows 7 to another involves using the Windows Easy Transfer utility to copy your files and settings to an external hard drive or a shared network folder. After the transfer is complete, you can then perform a clean installation of Windows 7 and use the Windows Easy Transfer utility to restore the backed up files and settings to the new system. And then you’re done, right?

Wrong.

There’s still the little task of reinstalling (and, if necessary, activating) all your programs on the new Windows 7 build. That’s a process that can take some time. In this post and the accompanying image gallery, I’ll show you how the Windows Easy Transfer utility works and how you can maximize its effectiveness. (If you want to skip straight to the details, go to Page 2 of this post.)

Before I begin, though, a little history lesson is in order. About a month ago (March 7, 2009, to be exact), Microsoft marked the three-year anniversary of its purchase of software developer Apptimum, Inc. Apptimum’s crown jewel was a technology for transferring installed programs from one PC to another, which it sold in two distinct packages: the consumer-focused Alohabob PC Relocator and its corporate cousin, Migrate DT.

At the time, Windows Vista was in the final stages of its long and tortured development cycle, far past the point where new features were going to be added in. But Microsoft promised that these features would make it into Vista’s successor. PC Relocator was rebranded the Windows Easy Transfer Companion, and Microsoft made it available as a beta release. Microsoft’s Nick White wrote it up in the official Windows Vista Blog back in February 2007, just a few days after Vista’s commercial release:

Although the standard Easy Transfer wizard does not move installed programs, this is a very important capability that's been requested by our customers.  Because of this we have been working on a new tool called Easy Transfer Companion, which will transfer programs and program settings from a Windows XP-based PC to a Windows Vista-based PC.  When used together with Easy Transfer, you will be able to move everything you need to your new PC running Windows Vista.  Easy Transfer Companion has been designed to transfer many of the most popular programs for consumers and small businesses, as well as many others.  You can transfer programs with either an Easy Transfer Cable or a network.  We've released the tool in Beta so that we can take feedback on the overall functionality and get more information about the experience of transferring specific applications outside of those that we've tested internally.

And there it sat, for 18 months, apparently untouched. Last July, Microsoft unceremoniously pulled down its beta release of Windows Easy Transfer Companion and allowed the Knowledge Base Article describing it to vanish with no explanation. A Microsoft spokesperson told me that it was “unclear” whether the technology would ever be released and that its inclusion in Windows 7 was not a foregone conclusion.

There’s no trace of this feature in recent builds of Windows 7. Given that Windows 7 is now officially feature complete and a release candidate is imminent, I think it’s safe to say that the program formerly known as PC Relocator has been officially abandoned.

It’s not like Microsoft has completely ignored this feature area. The redesign of Windows Easy Transfer that appears in Windows 7 does a generally excellent job of moving files, user settings, and some program preferences between computers, far better than any previous edition. It's designed primarily to help you migrate from with Windows XP or Windows Vista. In page 2, I step through its workings and explain how you can use it to migrate safely from an earlier release of Windows 7.

Next –>

The Windows Easy Transfer utility has lots of options, but the basic process is fairly straightforward. Here are the seven steps you’ll need to follow:

STEP 1: Run the Windows Easy Transfer program on the old PC.

To get started, you need to run the Windows Easy Transfer program. On Windows XP or Windows Vista, insert the installation media (DVD) and browse the disk using Windows Explorer. Open the Support\Migwiz folder, and then double-click If you’re starting with an earlier build of Windows 7, you might be tempted to use the version on the Windows 7 Start menu. I recommend that you not do that. Instead, use the version on the installation media for your new Windows version, which is likely to have significant updates to the Easy Transfer support files.

STEP 2: Select a transfer method

The top two options in this dialog box are intended for situations where you’re transferring stuff between two physically separate PCs and can make a live connection. For this upgrade scenario, choose the third option, which specifies an external location (note that this destination can also be a network share).

STEP 3: Copy the files and settings from your old PC to the temporary storage location

For most Windows 7 beta testers, the “old” and “new” PC will be the same physical hardware, just with different installations of Windows. If your system uses a single hard disk volume, you can blast through using the default settings. If you have a dual-boot system or multiple drives, you’ll need to customize things using the advanced settings. I go into more detail here.

STEP 4: Install the new build of Windows 7.

For the sake of this walkthrough, I’m assuming you’ve chosen to perform a clean installation, which wipes out all your old settings. Don’t worry, you’ll be restoring them all later. After installation is complete, be sure to check for updates.

STEP 5: Install any must-have programs on the new Windows setup.

Although you can save this step for last, I recommend that you do this part now. If you use the Windows Live suite of programs (Windows Live Mail, Messenger, Photo Gallery, and Writer), I recommend installing them before you continue.

STEP 6: Restore your saved settings.

This part of the process is relatively easy. The Windows Easy Transfer utility is installed with your new installation of Windows 7, so you can run it from the Start menu (you’ll find it under All Programs, Accessories, System Tools). Choose the same option as in Step 2, but on the next screen specify that this is the “new” PC. The utility will step you through the process. If you have changed user account names or drive layouts, you might have to use the advanced options to map the old accounts and drive letters to the new ones.

STEP 7: Use the Windows Easy Transfer report to see which programs you have to reinstall.

After the Windows Easy Transfer utility completes its restoration, it automatically displays a report of what it did. (You can call up this report later by clicking the Windows Easy Transfer Reports shortcut, which is also in All Programs, Accessories, System Tools.) Check for any errors, and correct them, if necessary. Then open this list, which shows all programs that were installed on your old PC. If you chose to install some programs before running this step, you’ll notice that some programs on the list are marked with a green check mark as Already Installed. The links under each entry in the list take you to the program developer’s website, which typically includes the download link. You can leave this report window open, and it will update each entry in the list automatically as you complete it.

And that’s it. When I used this process to migrate 12GB or so of data from my old Windows 7 setup to a new one, each part of the process took a little less than 30 minutes. Your mileage will vary, of course, depending on factors like disk speed and how much data you have to migrate.

Here's a preliminary list of the programs whose settings can be migrated using Windows Easy Transfer. I compiled this list by hand using the XML files included with a recent build of Windows 7. It is obviously unofficial and subject to change. (I hope, in fact, that Microsoft will update it regularly after Windows 7 is officially released.)

  • Ad-aware 6 Professional
  • Adobe Creative Suite 2
  • Adobe ImageReady CS
  • Adobe Photoshop CS and CS 9
  • Adobe Reader 9.0 (no earlier versions appear to be supported)
  • AOL Instant Messenger 5 and 6
  • Corel Paintshop Pro 9
  • Google Chrome
  • Google Picasa 3
  • Google Talk 1
  • iTunes versions 6, 7, and 8
  • Lotus Notes versions 6, 7, and 8
  • Lotus SmartSuite
  • Microsoft Money Plus Home & Business 2008
  • Microsoft Office (versions 2003, 2007, and 14)
  • Microsoft Works versions 8.0 and 9.0
  • Mozilla Firefox 3
  • Opera 9
  • Peachtree 2009
  • Quicken Deluxe 2009
  • QuickTime Player versions 5, 6, and 7
  • RealPlayer Basic 11
  • Safari 3
  • Skype 3
  • TaxCut 2008
  • Windows Live Mail (versions 12 and 14)
  • Windows Live Messenger, Photo Gallery, Writer
  • WinZip 8, 9, or 10
  • WordPerfect Office (versions 11, 12, and X3)
  • Yahoo! Messenger
  • Zune Software 3

I’ve used the new Windows Easy Transfer utility on a half-dozen or so recent upgrades and it’s practically foolproof on simple installations. I still wonder, though, why the option to  move some programs can’t be made available.

Questions? Hit the Talkback button and ask away.

Topics: Hardware, Microsoft, Operating Systems, Software, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

124 comments
Log in or register to join the discussion
  • There is no reason to shun beta-to-beta upgrades

    Because let's face facts: you are OVERWRITING all of the files that Windows uses, by and large, on your hard drive.... so there should be no 'weird' things popping up, unless you are talking about registry entry problems, which are, by and large, also overwritten.

    Personally, EVERY SINGLE TIME I have been betatesting something, I've overinstalled each beta and RC as it came out..... no problems.

    Microsoft, as I have said many times before, is playing games here and needs to stop. They need to remove the 'version check' (which has given me problems in Vista when I've had to correct problems by doing an 'upgrade' installation and have had a Service Pack on the drive) and just allow people to overinstall older version of Windows 7.
    Lerianis
    • Reckless attitude toward betas

      Yours is an interesting response to clearly good advice. MS doesn't support upgrading betas because they don't want to support the headaches that can cause. You may not have experienced any issues upgrading between betas, but I can't imagine that's a common occurance.

      It's absolutely crazy to consider installing a beta OS on your primary machine but, if you do, you have to face the fact that you're going to be reinstalling your software and transferring your files a few times. A beta is not [i]meant[/i] to be your main OS.

      Someone even mentioned using the public beta for their media serving machine, and I had to think, what a headache, especially with today's DRM issues.

      The beta was fun to test, but I'll be waiting for retail before I even consider moving any important files to Win7, thank you. Good luck on your upgrades, but don't blame MS when you crash and have to fresh-install the final product, anyway...

      [Edit - formatting, originally submitted via Safari]
      WookieFan
    • I have experienced issues...

      ...with beta-to-beta upgrades. Those issues went away when I restored the original image, saved settings, did a clean install, and then transferred settings and files.

      I have also had issues with Vista-to-Win7 upgrades, which I expect to be flagged and hopefully fixed.
      Ed Bott
    • There are GOOD reasons why not to do beta-beta upgrades

      Primarily it's about where you spend your engineering effort. Do you take heads from the teams completing features to provide a tested path for the (relatively small number of) beta testers to upgrade to newer releases or do you leave those heads in place, working to nail features down and fix the last remaining bugs?

      I know where I would spend my effort!

      Don't underestimate the complexity of version-version upgrades.
      de-void-21165590650301806002836337787023
    • Interesting...

      It isn't just Microsoft "playing games" here. Mozilla, Novell/SUSE and many other big names also recommend a clean install and restoring of data (or in the case of SUSE, using separate root and data partitions) between Beta builds and most definintely between Beta / RC and final release code.

      Things change within a beta, certain files are added or removed. If they are removed, they no longer have an entry in the install list. If the file wasn't used in the previous release version (E.g. Vista or XP), then it won't be wiped and its registry entries won't be removed. That [i]could[/i] lead to obscure behaviour and bugs, which won't be reproducable, because you not using a tested scenario...
      pico_D
    • agreed

      I used to be a ms os beta tester until Win7, where they no longer wanted me. When beta testing ME, I had a bug they were so worried about they wanted me to ship my computer to them to study! Of course I didn't want this, so made the excuse that it was a beta to beta upgrade and doing a fresh install fixed the problem. It did get them off my back!!!
      7thsinbad
  • RE: How hard will it be to move to the Windows 7 Release Candidate?

    And what happens when the final version comes out? The whole thing over again??
    I'm seriously thinking of skipping the Release Candidate. My current build 7057 version is working pretty well. But the agony of reinstalling all the apps twice, not to mentioning getting the downloads of the ones I got electronically in the first place? Oh spare me!
    Merlinau
    • That's exactly what I am saying

      It's would be an absolute PAIN IN THE BUTT for most consumer users and even corporate testers to do that stuff.... personally, it took me 16 hours (8 over two days) to re-install all my stuff on my computer when I swapped out the hard drive and wanted to install Vista 64-bit on my machine.

      It's a PAIN having to do that. I could understand it going from X86 to X64...... but NOT just because Microsoft wants people to 'install in a real-life way'.
      Newsflash, Microsoft: the kind of overinstallations I do IS a real life situation for 99% of the beta testers out there.
      Lerianis
      • You have to build your base sometime

        When the final version comes out, you will upgrade over a beta, which in tunr was an upgrade over another beta, which in turn was an upgrade over another beta, etc.?

        At some point, you really want to start with clean code.

        It tok me a grand total of two hours to install every app I own here. There's no reasonj it should take eight hours, ever. Not if you've organized the software you own and use.
        Ed Bott
        • Hmm.

          Some people just can't get organizized. It's not their fault... or maybe it is... heh!
          aeguvas
    • ....

      [i]And what happens when the final version comes out? The whole thing over again??

      I'm seriously thinking of skipping the Release Candidate. My current build 7057 version is working pretty well. But the agony of reinstalling all the apps twice, not to mentioning getting the downloads of the ones I got electronically in the first place? Oh spare me![/i]

      Am I the only one who thinks that this is exactly why it's called a beta? If you didn't want to do this, DON'T INSTALL A BETA.
      Badgered
      • Beta...

        Exactly, this is why Microsoft's licence agreement strictly prohibits putting it on a production machine!

        Betas can cause problems when upgrading, because things change and certain files might no longer be needed etc. that means you end up with c**p kicking around causing unknown problems.

        Removal and complete re-install is standard practice with pretty much every beta I've done, from Microsoft or other companies or open source projects...
        pico_D
      • Why not install to another partition?

        I have been installing each subsequent build release back and forth between two partitions. Since the Win7 install includes a hidden 200mb boot/recovery partition, I can even overwrite my C: partition. So on each of my machines, when 7077 came out I wiped the other partition, formatted and installed from the desktop of the adjacent partition. Then, dragging the files through the partition wall is easy as pie, or I just leave them in the other drive for access. Of course, most programs have to be reinstalled. I plan to do this up until retail is released and then wipe and zero my entire HD to install retail Win7 from flash drive where I also have stored all of my programs and files/apps.
        gregrocker
    • All over again?

      "And what happens when the final version comes out? The whole thing over again??"

      This is one of the reasons why Microsoft have specifically stated that the Beta should not be used on a production machine.

      As it is a test machine, when the release version comes along, that will be installed on your production machines and the test machine will get 7.1 or 8.0 or whatever...
      pico_D
  • Can't handle scratch reinstalls?

    Why all the uproar over upgrades? If you're the type of user who can't backup their data and do a scratch reinstall, you probably shouldn't be using beta software and just stick with Windows Vista. Microsoft wasting their time talking about upgrades from the Beta to the RC is ridiculous.
    HovisC5
    • Couldn't agree more

      I have been doing computer consulting for business' over 15 years. I always see the same pattern with people. The type that "know enough to be dangerous" are really keen to run beta software. Then they ALWAYS come crying to me about how they MUST HAVE a stable computer to do their business tasks. I went through a rash of this with Office 2007 beta. Not as bd with Win7 but still some.
      muehlbauer
  • RE: How hard will it be to move to the Windows 7 Release Candidate?

    Ed, you stated that you don't recommend using the Windows Easy Transfer utility contained in earlier Windows 7 builds. I'm running the beta (December) version of W7. Is this the latest version of Easy Transfer or do you recommend downloading the release candidate, creating a disc using the .ISO image, and then running Easy Transfer from this disc (is this even possible?).
    jshanleynyc@...
    • Not the latest version in 7000

      I am going to test that scenario and see. The code in later builds supports settings for more programs. So you'll get better results doing it that way.
      Ed Bott
  • Good Grief, Format the drive and do a clean install.

    Microsoft goes to great lengths to tell people DO NOT install beta OSs on production machines and DO NOT expect to be able to do an "update" install on top of a beta. Why people refuse to listen and heed the advice is beyond me and whining about it after the fact is just plain silly.
    No_Ax_to_Grind
    • Exactly (nt)

      (nt)
      pico_D