Windows 7: New Hard drive reinstall question.

My hard drive is failing the SMART test. I have been receiving errors on startup, so I have ordered a new hard drive. I know how to do a clean install with Windows 7. My question is, isn't there an easier way to get everything from my dying HD over to my new HD?

I really don't want to have to load and update all my software on the new HD.



Suggestions?

I also need to know this.

What is the difference in cloning a hard drive versus creating an image of a hard drive?

You can try cloning using the Acronis premium cloning/imaging program that comes free when any Seagate or WD HD is in the mix: Seagate Acronis cloning free util. The Manual is on the Downloads page and easy to understand - use Auto cloning.

If it isn't satisfactory then get the superior Clean Reinstall - Factory OEM Windows 7

Cloning is a transfer in real time from one drive to another. It's usually done when replacing a hard drive and is not a "backup" as normally understood. It's normally done when things are working well and you want to change hard drives.

Imaging is a backup and consists of making an image file of one or more partitions, storing that image file on some other drive, and then "restoring" that image file to the original or new hard drive at some later date. The restore process is done in a semi-emergency situation when things are NOT working well. You make the image when things are going well, but restore only when things have gone seriously downhill for whatever reason. If you make the image file in January and restore in July, your system reverts to the January status, unlike cloning.

Imaging is more common because it's a backup you can fall back on when in a jam, unlike cloning.

1. run chkdsk X: /R on each and every "drive" on the hard disk.
you substitute the appropriate drive letter for X

2. If any drive doesn't come error-free, then run chkdsk on that drive again.

After doing that then run the script I'm including and attach the resulting file to your next post.

The objective here is to determine if making a system image is a feasible approach.

# **********************INSTRUCTIONS**************************
# STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR ******************
# ************************************************************
#
# WIN key | type POWERSHELL | do NOT hit ENTER |
# in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
# choose "Run as administrator" |
# Click on the YES button (if such appears)
#
# WIN key = key with Microsoft log on top
#
# for the guru:
# WIN | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
# ************************************************************
# STEP 2 ** COPY AND PASTE ***********************************
# ************************************************************
#
# COPY the script using CTRL+C,
# COPY every line of script down thru both EXIT statements
#
# PASTE into Powershell
#----Right-Click at the PowerShell Prompt
#----(Ctrl+V does not work)
#
# Start copying with first script line without a # at start of the line
# Note: Actually, you can paste the entire file if you rather
#-------Lines starting with a # are ignored by PowerShell
# ************************************************************
# STEP 3 ** SCRIPT OUTPUT & SCRIPT PURPOSE *******************
# ************************************************************
# --The script output and purpose is given at the very front of the script
#
# --The script output and purpose is given at the very front of the script
#
# ************************************************************
# ***************** NOTE - POWERSHELL VERSION*****************
# if you receive this error msg:
#--The system can not find the path specified
# you may need to update your PowerShell
# you must be using Powershell 2.0 or later.
#
# To determine your Powershell version:
#---Run PowerShell
#---enter $host.version
#---you should see at least:
# Major Minor Build Revision
# ----- ----- ----- --------
# 2......0......-1.....-1
#
# If you do not see the above, update your Vista/Win 7.
# ************************************************************
# *************** NOTE - EXECUTION POLICY*********************
# If you haven't set the execution policy, you may need to:
#---Run PowerShell
#---enter SET-EXECUTIONPOLICY -EXECUTIONPOLICY REMOTESIGNED
# ************************************************************