Cloning Windows 10 to SSD

Toggle sidebar Toggle sidebar
B

BrianNelson

Prominent
Feb 27, 2017
2
0
510
**
Before I start, I'd like to say I have a fully legit version of Windows 10

My PC is a custom built rig (nothing special), and when I called Microsoft for help on transferring my OS to the SSD they didn't help. I have an ASUS M5 A78L-M USB 3 motherboard, a Kingston 240 GB SSDNow 300(the SSD was purchased from a friend so I had no software or the Acronis software to move my OS). I have a Hitachi drive that holds my OS and some other things at the moment. I've successfully cloned my Hitachi drive data to my SSD, but when I try to boot from my SSD, nothing is picked up and I am supposed to "Insert bootable media and restart." I'm not entirely sure what the problem is, and I was wondering if this forum could help.

I recently installed the SSD software to manage the temperatures and updating software. I tried to delete everything off of the Hitachi drive that currently has the OS on it to see if that would change anything when I cloned it over. Turns out nothing changed, but there is also a little data other than windows on the Hitachi drive. Like I said before I really don't know if any of this would affect anything at all. If you have a solution I'd really appreciate the help! If you've got any more questions or need more info reach out to me however possible, I'm not very familiar to this forum yet so I'll try to stay on top of it! Thank you! (Below I've attached a screen shot of my drives. I'm trying to get the To Be Posted drive cloned and bootable on the drive titled OS & Games. I've cloned it before but recently reformatted because I saw that I couldn't boot from it.)

**This all happened in the past 2-3 days**
Thanks in advance for your help!

https://drive.google.com/file/d/0B6tzTpr5cKbOckJNekJ4N1pfb00/view?usp=sharing[/img]

Other than the steps mentioned previously, I have not done anything.
 
Solution
A
1. The DM screenshot is quite helpful.

2. It's a question of semantics so let's not delve into that right now.

3. Good

4. That's understandable, particularly since the SSD should provide significantly faster operational speed than your current Hitachi 160 GB HDD.

5. Actually I just wanted to ensure that the amount of data being cloned from your source disk to your destination disk, i.e., the SSD, did not exceed the disk-space capacity of the SSD. Obviously that's not a problem since your SSD is a 240 GB drive.

So...
1. Since you're obviously working with a desktop PC it really would be best (after powering-down the PC, of course) if you would (temporarily) disconnect all your other drives from the motherboard excepting the source &...
Sort by date Sort by votes
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
1. The screenshot you should send along is of Disk Management reflecting your current drives configuration as it now stands. Include the upper portion of DM in the screenshot which includes add'l details of the listed disks as well as the lower portion of the DM screen listing the connected drives.

2. It is not unusual for the disk-cloning operation to go awry notwithstanding your comment that you "successfully cloned" the contents of your source disk, i.e., the Hitachi to your Kingston SSD destination drive.

3. DO NOT contemplate any changes on your system drive, i.e., the Hitachi, (assuming you may have that in mind) at this time until a viable clone has been created.

4. Can we assume at this point that the Hitachi is still functioning without problems as your boot drive?

5. And what is the total data residing on the Hitachi? If it's multi-partitioned indicate the type of data in each partition.
 
Upvote 0 Downvote
B

BrianNelson

Prominent
Feb 27, 2017
2
0
510




1.Here is the screen shot of the Disk Management Layout
https://drive.google.com/file/d/0B6tzTpr5cKbOMUxCREFrQmlidTQ/view?usp=sharing

2.I'm not too sure what exactly you meant by the second point, I think you mean like that its common for the cloning process to not go as planned.

3. I won't make any more changes to the Hitachi drive at all, unless it'll solve the problem.

4. Yes the Hitachi is functioning fine, I'd just like the OS on the SSD for faster boot speed honestly.

5. I think by this you mean how much space is left on the drive, the answer to that is 32.3 GB and 115.7 GB have been used

I hope this helps! Thanks for the quick replies!
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
1. The DM screenshot is quite helpful.

2. It's a question of semantics so let's not delve into that right now.

3. Good

4. That's understandable, particularly since the SSD should provide significantly faster operational speed than your current Hitachi 160 GB HDD.

5. Actually I just wanted to ensure that the amount of data being cloned from your source disk to your destination disk, i.e., the SSD, did not exceed the disk-space capacity of the SSD. Obviously that's not a problem since your SSD is a 240 GB drive.

So...
1. Since you're obviously working with a desktop PC it really would be best (after powering-down the PC, of course) if you would (temporarily) disconnect all your other drives from the motherboard excepting the source & destination drives for the disk-cloning operation. While it is not an absolute necessity it removes a significant source of potential problems that can negatively affect the disk-cloning operation. But if it is impractical or infeasible to do this then let it be.

It's also a good idea if you would connect the SSD (the ultimate boot drive) to the motherboard's first SATA port (connector), usually designated SATA 0 or SATA 1.

2. Are you familiar with the Acronis program and that is why you used it for the disk-cloning operation? I haven't worked with Acronis for a fairly long time; for a variety of reasons; it was never a favorite d-c program of mine. But of course it is used quite extensively by many users. So if you're comfortable with it...

3. A d-c program that many PC users seem to prefer is the freely-available Macrium Reflect program; you might want to take a look at it. See http://www.macrium.com/reflectfree.aspx

4. The d-c program I generally employ is the Casper program. I've been using this program for a number of years and recommend it for its ease of use, general effectiveness, and especially its operational speed. My primary - nearly exclusive use is as a comprehensive backup program used on a frequent basis.

Although the program is a commercial one costing $49.99 there is a Trial Edition available which you could use and hopefully it will be successful as it relates to your particular situation. You may wish to give it a try.

So if you're so inclined...here are some instructions for doing so...

1. Download/install the Casper Trial Edition 10 (v10.0.6044) disk-cloning program from: https://www.fssdev.com/products/casper/trial/

2. Before undertaking the disk-cloning operation close all open programs. (Generally you need not disable your anti-virus program). Ensure your destination drive - the proposed recipient of the clone - is properly connected in the system. It can either be installed internally in the system (presumably a desktop PC), or externally as a USB device should you be using a laptop/notebook.

3. Click "Add drive" and a window open listing the destination drive. Ensure that's the correct drive you desire as the recipient of the clone (just in case other multiple drives are connected). Click on that disk's listing and then "Yes" on the confirmation message that follows.

4. Click on "Back up now" (after again assuring that it's the right drive you desire to receive the cloned contents of the source disk).

5. Casper will begin the disk-cloning operation running in the background. If you want to view the progress of the disk-cloning operation click on the Casper icon visible on the Taskbar or in the Notification area of the Taskbar.

6. Following the successful disk-cloning operation disconnect (when practicable) the source drive from the system and boot solely to the connected destination drive. As a general proposition it's a good idea (whenever practical) for the newly-cloned drive to be connected to the motherboard's first SATA data connector, usually designated SATA 0 or SATA 1.
Also, check the system's BIOS/UEFI to ensure the cloned drive is now first in boot priority order.

7. If your destination disk was connected as a USB external drive for the disk-cloning operation, boot to it to determine whether it's a bootable drive while connected as a USB external device. Ensure you select the drive from the boot menu during bootup. If it's unbootable while connected as a USB external drive (since many systems will balk at booting from a USB device), most likely it will be bootable when connected internally in the system.

8. Casper will utilize the entire disk-space of the destination drive to contain the data contents from the source drive.

If you do use it please let me know the results.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom