Windows 10: Just cloned Win10 SSD to new unallocated SSD, but something is wrong. Help please?

Hi all. Like the title says, I just cloned my main Win 10 SSD (C to a new unallocoated 1TB SSD(B using EaseUS. After the cloning/transfer, I had the original (C and the new 1TB SSD(B with all Win10 and programs perfectly duplicated onto (B. I shut my PC off and went into BIOS to change Boot Configuration. Boot1: 1TB SSD (B and Boot2: UEFI Hard drive(C is all I changed and started back into Windows 10 to this shot in Disk Manager.

Disk 2 is the 1TB SSD that was (B until I restarted. (G came out of nowhere and this is what we have now. It seems Disk (C fused with the new 1TB SSD on Disk2, and then (G/(F were created and prioritized as Disk0? Disk0 used to be (C, and now that's part of Disk2. This was not intentional.

In File Explorer it looks like (C is still prioritized with Win10 operating.

Disk1 (E can be ignored as it is just an HDD for storage unrelated to Win10 operating/SSDs.

If anyone has any knowledge, links, or guides to resolving this, I would be greatly appreciative!

https://preview.redd.it/35fmc7es11b...bp&s=555fce8c8d6def2abc526dee9f114c832a04e876



https://preview.redd.it/2pu31uln21b...bp&s=ccbed6517048d5d4e785b276f74ca6de362897f1

submitted by /u/apacherosepeacan
[link] [comments]

:)

 

Unable to Boot to Windows 10 after Cloning old SSD to new SSD

Hi,

I'm not using the SATA ports. I'm using M.2 with the SSD, and the external SSD is connected to my PC using USB. My MB only has only one M.2 socket, so I can only plug in one SSD at a time. (I bought a wrong adapter that doesn't work with NVMe) So I cloned
my old SSD to an external SSD (Samsung M3 Portable SSD), and then swapped the old one, cloned the external SSD to my new SSD.

I tried AOMEI too, but the free version does not come with disk clone functions. I would probably try Macrium Reflect as suggested above. Thank you!

 

Moving to SSD. Clone or not to clone?

I kinda agree with you, but on a wholr, do not. While I have done things a bit differently than this specific situation, by installing Windows directly to the SSD, and cloning after, my testing shows that there are no issues doing this, very little that can go wrong, provided your system is stable.

There are certain features that must be disabled in this situation, like auto defrag and such, but even with a fresh install to the SSD, you need to take steps to ensure that you SSD performs properly, regardless of how the data got there.

Arming yourself with a bit of knowledge can go a long way.

Installing the latest chipset driver, and the RST Tools, will ensure optimal performance of the SSD. but rather than taking my advice, I suggest the OP takes a look here:

http://blogs.dirteam.com/blogs/sand...7-and-ssds-to-clone-windows-or-reinstall.aspx

Installing The SSD - Install A Solid State Drive In Your Notebook | Tom's Hardware

Keep in mind, also, Digibucc, that many retail drives include software and such that very specifically is to be used to ttranser the OS from an existing mechanical drive to an SSD, and if there really was alot fo issues stemming from the cloning process, they would not have packages like that, simply to eliminate tech support costs. While not the optimal option, cloning is NOT a bad thing, as long as you take the nessecary steps.

 

Unable to Boot to Windows 10 after Cloning old SSD to new SSD

I use AOEMI free . They use the term 'migrate' OS to new SSD (but it will also migrate\clone to HDD or HDD to SSD).

Ah! Yes, I overlooked the NVMe part of your SSD description. This does rule out any swapping of ports, unfortunately,

but the recent versions of the cloning programs should normally write a boot sector to your new SSD.

You could still connect the HDD to an internal SATA port rather than using USB though... or not ?

- The main difference between an Image and Clone is the clone is an exact replica of your C:\ drive including fragments and

unused space. With an SSD the fragments don't much matter, and when I clone to an HDD I always do a full de-fragment and optimise

(optimising moves files that may be spread out on the HDD into a contiguous order) after doing the clone, but this is

more about performance on the HDD than the final result on the SSD should I need to clone back to an SSD at some point.

(I make a new clone on a HDD prior to every Win10 version update as a precaution should the update bork my OS).

btw - The base of my Win10 is Win7 installed in Jan 2010 which has been cloned to two new machines (using new license keys)

prior to upgrading to Win10.

Still performs as well as a clean install of Win10 I did as a test (and never used because, even after spending half a day installing and getting

the basics sorted out, I would have still needed a lot more time dealing with a lot of games and software).

.