Refresh and Reset

One of Windows 8’s most appealing new features for enterprises is something Microsoft calls “refresh and reset.” It adds the ability to automatically roll a busted Windows install back to a pristine state. The “refresh” functionality rolls back changes to system files and installed desktop applications (unless you create your own recovery image; more on that in a minute) but preserves user data, and the “reset” functionality reverts Windows to its freshly-installed state. This is analogous to the appliance-like “reset” or “restore factory defaults” functions present in many smartphones, tablets, MP3 players, and other electronics capable of storing customized settings and user data.

Refresh and reset, accessible from the “General” section of the Metro settings and from the WinRE recovery menu, both use the same image-based technology used by Windows Setup to do their thing. Since Vista, Windows install media has included (1) a collection of files required to enabled booting from the media and (2) a large, monolithic .WIM image file that is uncompressed and copied to the hard drive during install—this contrasts with the setup process for Windows XP and earlier versions, which expanded and copied individual files from the install media to the hard drive. Microsoft also offers a number of tools (many included in the Windows ADK) to let end users and IT admins create their own, customized .WIM images, which can be used to deploy a custom Windows installation to many computers quickly.

So, to continue the Windows Setup analogy, “refreshing” the PC acts as an upgrade install, replacing the operating system while preserving user data. Metro-style apps will also be preserved, but installed desktop apps will be removed and a list of them will be placed on your desktop in HTML format for reference—Microsoft’s reasoning for this behavior is that malicious desktop apps are more likely to be the cause of serious problems than are Metro apps from the Windows Store’s “walled garden”.

“Resetting” the PC acts as a clean install that blows away all user data, especially useful if a PC is being repurposed or sold or otherwise transferred from one party to another. The reset option also gives you the option of erasing the hard drive securely so that sensitive data won’t be at risk.

Recimg: Creating Custom Recovery Images

There’s one more major component to the refresh feature, and it’s probably the most interesting one—using the Recimg command-line tool, users can create snapshots of their systems to use as the reference point for a refresh. These snapshots, which are really just the same .WIM images used by Windows Setup, will store settings, drivers, and both Metro and desktop applications, and can be created at any time and stored basically anywhere, including the Windows partition.

These recovery images can even be used to replace factory restore partitions—suppose that you buy a cheap Windows 8 PC, as many people will do, and it comes with the requisite sea of crapware and no recovery DVDs or USB sticks. Thanks to Recimg, you can uninstall that crapware, update drivers, install programs you actually want, capture an updated crapware-free image, and then delete the old recovery image/partition from your hard drive to save the space. Relatives who have broken their PCs can then use the recovery image to revert their PCs to an unbroken state without losing their personal data.

Sounds useful, right? Let’s talk a bit more about how to use recimg.

First, you’ll need to run the Command Prompt as an administrator—otherwise, Recimg won’t run. From here, you can launch recimg with one of five different switches:

  • Recimg /createimage <directory> will create a new install.WIM image containing your installed drivers and programs to a directory you specify. The easiest way to do this is to store it on a local hard drive, but an external drive will also work as long as the external drive is plugged in when you initiate the refresh). The size of the .WIM file will vary based on what you’ve got installed, but images usually start at 3 or 4 GB and work their way up from there.
  • Recimg /setcurrent <directory> will set the install.WIM image in the specified directory as the one Windows will use when refreshing your PC. If you run Recimg /createimage but don’t use /setcurrent afterward, Windows won’t know to use your image.
  • Recimg /deregister will deregister the currently set recovery image. If a previously-created recovery image exists, Windows will revert to using it. If no image exists, Windows will ask for you to insert install media when you try to refresh the PC.
  • Recimg /showcurrent tells you where your current recovery image is stored.
  • Recimg /? tells you all of the stuff I just told you.

The primary downside of Recimg is that it can’t be used to reset a PC, only to refresh. My test PCs always asked me to insert Windows install media to use the reset functionality—OEM PCs that ship with Windows 8 may behave differently, but we’ll have to wait and see.

That aside, Recimg and the refresh/reset functionality do a solid job of making OS reinstallation a bit simpler—Windows Setup isn’t very hard now but it, combined with the challenge of reinstalling apps and drivers, has made reinstalling a fresh copy of Windows more of a pain than it needs to be.

Storage Spaces

Windows 8's new Storage Spaces functionality allows users to pool different physical drives together into one large logical drive, not unlike the now-discontinued Windows Home Server Drive Extender. You can pool drives connected by just about any common interface, including USB, SATA, and SAS.

Once you've created a storage pool using two or more drives, you can then set up one or more "spaces" that will be seen by the operating system as a logical drive which can be formatted, partitioned, and used just as a physical disk would be. To provide redundancy, you can either apply the "mirrored" attribute to your pool, which makes sure that a copy of every file in the pool is stored on at least two different physical drives, or the "parity" attribute, which uses some drive space to store redundancy information—in the event of drive failure, this information is used to rebuild your pool and enforce mirroring. Microsoft notes that while the two redundancy options are similar, the "parity" attribute is best used for large sequential files or less-frequently-accessed content, since it has a higher random I/O overhead. As with any redundancy technology, you'll give up maximum drive capacity in exchange for data integrity, so weigh your priorities carefully when you create your pool.

When creating a new Storage Space, you can specify a maximum size larger than the amount of available physical space—the system will prompt you when the storage pool needs more drives to work with. Microsoft calls this "thin provisioning," which means that drive capacity is only reserved as you store data to the drive rather than all at once. You can also expand the maximum size of the Storage Space at a later point if necessary. Creation of these spaces can be scripted using PowerShell.

My experience with Storage Spaces was a bit spotty—it didn't seem to want to recognize some of the USB sticks I plugged into my computer, and it wasn't clear why. It may be that there are some unspoken speed or hardware requirements that a couple of my drives just weren't meeting. Once I did get it working, though, it worked as designed—as you can see in the screenshot above, I unplugged one of the drives from the pool I had configured to simulate what would happen in the event of drive failure, and the redundancy features ensured that I was still able to access all files I had copied to the pool. One could then reconnect the drive or add a new one to the pool to restore redundancy.

The Windows Store The New Task Manager
Comments Locked

286 Comments

View All Comments

  • Andrew.a.cunningham - Saturday, March 10, 2012 - link

    I've seen that from a couple of other people... Not sure how I missed it. It's on a list of small updates I need to make to the article that I hope I can get to tomorrow.
  • Cardio - Saturday, March 10, 2012 - link

    I am running Win 8 CP on a new build Asus Z68, SB @4.7, a Mushkin Chronos SSD and a GTX 580.
    First I think this is an exceptionally well done review. It is an OS review not hardware. There is no reason to think that the OS will work differently on an AMD or an Intel anymore than win 7 did. I am pretty sure that MS knows there are AMD systems out there and is not going to release an OS that will not run properly on them, seems like that would be the best business plan. I, for one, see nothing wrong with Windows 8. It is faster than 7 and has been completely stable for me and compatible with everything I have tried with the sole exception of CPUZ and ASUS's multiple driver install program that sees it as an unknown OS. The drivers still install normally if done separately.
    It is different. Most of the complaints I hear are based just on that. Personally, I wouldn't want it if it wasn't different. If you don't want it don't buy it. If you don't want to do things in a different way you sure don't have to... Windows 7 is and will still be around. All this predictable ranting is the same as happened when DOS went away and every other OS change since. I have used Win 8 enough that the changes in use are now normal and you don't have to think about it. I'm sure before RTM and there after there will be more changes. Thanks for the very nice review. I can imagine what a job it was.
  • taltamir - Saturday, March 10, 2012 - link

    "Metro is here, and if you use Windows 8 you’ll have to come to terms with it."

    Then I wont be using windows 8.
  • eezip - Saturday, March 10, 2012 - link

    Am I the only one that has trouble with this? I can sign in at https://login.live.com/ and have no problems at all, so I figured that was the login info to use.

    I installed the Dev Preview when it was released and used a local account. But after recalling the Win8 blog post about Win Live ID syncing, I figured I'd try it before moving to the CP. So I went into the settings and selected "Switch to a Microsoft Account". Seems logical. But I was unable to log in again to the Dev Preview install. Arrrrgh!

    So, I clean installed the CP and tried using the Windows Live ID login info from the beginning. I got to the desktop, but the first time I restarted the computer, I couldn't log in. I had entered my phone number and hint info, but I never saw how to enter it. And the CP certainly didn't offer to help me when I was clearly struggling. Since I didn't have a local account, I reinstalled the CP using a local account, which brings me to today.

    Is my login at https://login.live.com/ the same login that I *should* be able to use for Win8? I can only assume that I'm doing something wrong, but I sure don't know what it might be.
  • InsaneScientist - Saturday, March 10, 2012 - link

    How long is your password?

    Try just the first 16 characters if it's longer than that.
    For whatever (REALLY STUPID) reason, it'll let you enter a password longer than that, but it only uses the first 16 as the actual password.
    (See my comment two below yours, and poke around on google. It's a known issue)

    If it's not longer than 16 characters... I have no idea.
  • b_wallach - Saturday, March 10, 2012 - link

    Well what is a in depth when there is nothing very in depth at all. With all the systems tested here it's really a drag that you can't dig up a AMD system and the one everyone wants to see is the BD line.
    Most people have seen enough to say if you wanted to do a run with the new OS it would be with this cpu because of all the guesses and some beta tests that showed a marked improvement with these cpu's.
    Running a bunch of lame Intel systems really makes it kind of a joke. If you did not have a good selection of different brands then why not delay it until you have enough systems to call it a in depth review instead of a who cares review. I'm sure most would say the intel's would do good and so nothing worth noting was done that would add to a lot of how much better will a radical cpu design work on it as everything points to this being a top of the list things people want to know about the new OS.
    With some win8 beta tests showing a 5-10% increase I'm sure everyone that has the new BD's has been waiting to see this one over any of the no real supprise Intel lines.
    As always it leaves a fairly large question mark about just what can expect from a site that has been less than honest about AMD for many years.
    It's only lately I've even come back here after what went on with bad reviews and very few when AMD first put out their first FX line that was better but trying to avoid the Intel inside ads all over and great praise for Intels horrible egg cooker cpu made me stop comming here for many years. I can't understand why anyone would not put AMD's new cpus right up front with Window's 8 so we can get a good amount of data over this hugely argued point all over the web.
    So no this was anything but a in depth review. It was a candy coated and/or we need to run a filler story to help the hit counter stay busy right???
    Before that Pentium 4 fiasco I came here a lot.
    After that I started looking at a lot of other sites where the useful data WAS useful. Intel knew what sites to throw a lot of money or inflence as they hit the top sites of the day, Tom's hardware was also doing the same line of crap and like this site I took a few years leave until they could earn back what little trust in them.
    I'm sure some other sites will get the AMD BD / Win 8 test done. I can't wait to see if all the flack about AMD and windows had merrit. If not I'll stick with Win 7.
    Sorry about being so glib, this IS a good site now, I just hate it when they don't pay much mind about what has been the top interest about windows 8 because AMD has a lot riding on how well their new cpu's will do with it. If it follows the beta tests it would move the AMD right up into the level of being a competitor as they are very close with current Intel cpus in some areas, even pass intel in quite a few other tests and if they see a 5 to 10% it would def. make AMD's cpu a contender. Not a top of the line one but it would put it where AMD wanted to see it run.
    Now that would alone make it a in depth review..
    It would even be a huge news item to run if AMD can do as well as the WIn8 beta reviews people might not bash it so much. AMD built this design for what could be a very sound call because a huge portion of computer users may or may not know is software is putting more demands, a lot of people run programs that can work very well in the multi-threaded apps as I have seen quite a few new ones use it and it will probably get more demanding use running 2-5 or more progs at the same time. AMD's new cpu does this part very very well.
    Oh well, it seems like me most wanted AMD scores because it is very important towards AMD's future if they can pull the scores that the beta revew saw.
    It can be compared to buying a upgraded cpu because new cpu's usually give this kind of increase from old cpu's scores and their new cpu's can do.
    Still, it's got a lot of potential once people start coding prog's to work well with new cpu designs. Intel hsa had to face this when a lot of their products acted even worse than the current AMD performance numbers.
    Even if I'm totally wrong about a details it's funny to read bad stuff about these cpu's. They do have some issues but for the most part they are still a very fast cpu and will run all software pretty darn fast.
  • Andrew.a.cunningham - Saturday, March 10, 2012 - link

    This was a feature review/preview, not so much a performance review/preview. We'll be measuring performance more thoroughly when we have the RTM build in a few months.
  • InsaneScientist - Saturday, March 10, 2012 - link

    Maybe because it's an indepth article on the OS itself and not so much a re-review of every piece of hardware released in the last 5 years to see how it'll run Win 8? Sound reasonable?

    And no, how bulldozer improves (or doesn't) ISN'T what everyone wants... what everyone wants is to know if they'll be able to use the new interface. Talk to anyone who has any experience with Win8 - Metro WILL come up (fast), bulldozer? - not so much.

    Oh, and as a side note, I can't speak for the initial release of the A64 vs P4 days, but I started coming here around the time the A64X2 and Pentium D came out, and I rather remember Anandtech calling it like it was... the performance was not too dissimilar, with the A64X2 having an advantage (sometimes a large one - occasionally a disadvantage), but the Pentium D needing and ungodly amount of power and heat to be competitive with it. They've always done a good job of calling it like it is! I've never understood where the claim that they're Intel biased comes from.

    Don't get me wrong, I also want to know if it's going to help (and I really hope it does), but it's just not that important. Mostly because CPUs - both Intel's and AMD's - are generally fast enough.
    To quote you: "[Bullzoder CPUs] do have some issues but for the most part they are still a very fast cpu and will run all software pretty darn fast."
    Yes! That's it exactly! They're fast enough that it's no longer critical to be looking at hardware performance with a new operating system. Instead, when we look at a new operating system, we want to see... well... that operating system.

    Furthermore, this isn't a final release. Software development develops features and then the feature set is locked and the codebase is optimized. So performance WILL change between now and RTM (and it would not be fair to AMD to test it now). Features, on the other hand are pretty close to final, so talking about those is fair game.

    On the issues that everyone is talking about (Metro, UI, and feature changes), Andrew et al. did an excellent job, and I applaud them for that.
  • InsaneScientist - Saturday, March 10, 2012 - link

    Have they done anything in the CP about that blasted 16 character limit on (live account linked) passwords?

    This is (in my opinion) by FAR the most egregious step backwards on Windows 8. Why on earth is there a limit on this? It's 2012 for crying out loud!

    And the need for an "All" option (which should be the default) in search from the start screen. I'm seriously considering skipping Win8 just because of this.
    I don't mind Metro much, it's not my favorite, but I can work with it... but why oh why did the search functionality have to take a step backwards after they got me hooked on it in Win7. :(
    I may be able to use it with the keyboard search shortcuts you mentioned, but that's not exactly a ringing endorsement.
  • MamiyaOtaru - Saturday, March 10, 2012 - link

    " In 2009, Windows 7 brought WDDM 1.1, which focused on reducing system memory usage by removing redundant data, and support for heterogeneous GPU configurations, a change that precluded modern iGPU + dGPU technologies such as NVIDIA’s Optimus."

    I don't think "preclude" means what you think it means

Log in

Don't have an account? Sign up now