WHAT is Win7 Builtin Backup program really Good for?

I fielded a question about this today and didn't really like my own answer.
If one wanted to use the builtin/embedded Windows 7 Backup package, for what reason would one use it? It can't really restore a running/activated hard drive image... and its overkill for mere stashing of copies of important data, so .... why?

And, to show my bias a bit.. IF one were just INSISTENT on using the package, and subsequently one had a real hard drive crash/burn, how would one go about restoring a running/valid/active volume with all parts intact, all programs working normally using the archive created by Win7 Backup??? I'm guessing one of you smart guys has done a tutorial on such

this is different info from what I have understood since the earliest days of win7.... are you saying that:
1. pop a fresh, new, formatted drive into 0 position
2. pickup the Win7 system image from an attached drive
3. press the restore or whatever button...
4. Reboot and the drive will come up and activate immediately? just like the one that crashed [minus iterative changes of course] ???
if so, why does everyone use other packages to do this?? it would seem the aftermarket would die

pparks1 said:

You use the "system image" component of backup. I used it to image my 1TB seagate, when I moved instead to a 1TB Western Digital. Worked just fine.

is it just my understanding of English, or is this really illogical:
"2. If you are "Not Able to Boot" into Windows 7
A) If you have the system image backup save to an external device, be sure that it is connected now.

B) Open a command prompt at boot."

Have looked at the tutorial posted

System Image Recovery
Backup Complete Computer - Create an Image Backup
Restore Backup User and System Files

zapp22 said:

if so, why does everyone use other packages to do this?? it would seem the aftermarket would die

The aftermarket programs are alive and well because of certain issues with the built-in product.

It isn't particularly intuitive to a new user. The interface is way too busy.

It is cranky about re-naming or re-locating saved images.

Microsoft didn't implement it correctly in my opinion. The package contains both"imaging" and "file by file backup" capabilities. I think they should have made a clear-cut distinction between those 2 capabilities and separated them into different and uncluttered interfaces.

I guess they wanted to dumb it down for those inexperienced with imaging and backup, but they only made it more complex than it needs to be.

it looks like we're in violent agreement.
"not able to boot" means the system is "not able to boot", because the drive is "not able to boot", and has no idea what "open a command line prompt" might be.
unless win7 is living in the ether and able to communicate without media

JDobbsy1987 said:

Not that i would ever question Brink :)... That looks correct to me...

Line B.) states "Open a command prompt at boot"....

The part "command prompt at boot" happens to be a link to - Command Prompt at Startup which shows you how to boot in safe mode.

If you can't boot at all then there is more than likely a bigger underlining problem.

Regards,
JDobbsy1987

My impression is that you can boot with the repair cd and restore the image that you saved with the win 7 backup to a hd or partition. That image is a clone of the hd, with all your programs and data, and is bootable. The win 7 backup gives you the opportunity to create a repair cd.