Windows 10: Cloned OS from HDD to SSD; good install? Have doubts
OK, finished the Macrium imaging. One glitch I had was when trying to reduce the target C drive from the source, I would go from say max 220 to 200 GB. Then, when I see I need to go back up to max 210, I can't without undoing several steps. Since this required several attempts to get the right number, it was a tedious process. Am I missing something there?
I ran "winsat formal" & "sfc /scannow." Results below; winsat doesn't offer a good/bad verdict. Anything else I can do to verify all is well on the new SSD before re-formatting the OEM HDD?
Still not clear if I should have just tried to clone a second time, but now I learned how to clone & image. For recovery media, I have the Macrium image on an external USB HDD and the Apricorn clone on a USB flash drive. Thanks for everybody's help.
Looks to me well done, BIC!
1) Main reason I recommended "winsat formal" is I've seen a few people here go from an HDD to an SSD and, for some reason, Windows hasn't realized that the disk type has changed - winsat formal gets the OS to take a fresh look at all of the hardware types you have - usually the complaint is that Windows Disk Optimization is not realizing that it's a solid state drive and the fear is that it would be inappropriately fully defragmented. A check for you would be to open Windows Disk Optimization and see that it is correctly listed as solid state.
2) You could always run a "chkdsk /F" (letting it reboot for that) on the drive just as another check - but I suspect you're completely good to go.
Unless you're in a hurry to convert that old HDD, you could just let it sit, unmodified, in a safe place for a week and make sure everything works according to plan.
I noticed you seem to be using a camera or web cam for your pics on here, their is a MUCH better way to take a screen shot for this forum. Take a look at this link. Most of us use this tool.
Snipping Tool - Add to Context Menu in Windows
After I cloned it the first time, I was using it for a few days and everything seemed to be working OK. It was only when I went to do a Windows Update & create a Windows Repair Disk, did hints of issues arise which led me to go with the imaging procedure.
Yes, I was using a regular camera to capture the screen shots, primarily because I had to go to a different computer to do my posts here. But, I was not aware of the Snipping Tool; I'll check that out next time. Thanks.
Good to see you have it working.
Ideally the recovery should sit in front of the OS partition. Easy enough to fix but if it doesn't bother you that's fine.
Why is that? I just left it the way Dell created it. Thanks.
MS recommends having WinRE (your partition #4) first like this
The reasoning given is "This partition order helps to keep the system and Windows RE partitions safe during actions such as removing the recovery image partition or altering the size of the Windows partition." Source
However it really doesn't matter at all what order your partitions are in. You could shuffle them around with MiniTool Partition Wizard if you wanted (you would then have to re-register WinRE in in the new location with reagentc.exe) but I wouldn't bother unless you want to remove your dell recovery partition (your partition #5) anyway (if you are running short of space for example).
Interesting, because I let Windows 10 Pro make my partitions on my 1st clean install. Windows made 4 partitions in the order it wanted on my UEFI /GPT Partitions. No WinRE partition was made. And my C-Drive is the last partition.
The WinRE partition is the first one. You can check it with reagentc /info and it will tell you the partition of the registered WinRE image.
You don't have the 5th partition (OEM recovery) as you did a clean install.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
Windows Recovery Environment (Windows RE) and system reset configuration
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 9c34aef3-9152-11e5-9c76-00155d013517
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
Ahhh Correct again lx07 that's right I forgot about the OEM recovery partition not being made. Plus I didn't want it too.
I currently have a cloned 8.1 drive that is unplugged and was done only for back-up before installing 10. Question, since I have no plans to go back to 8.1 I wonder if I should just use it as a test bed for new 10 releases? I guess I could hang on...
I just cloned the new SSD from 128GB to 256GB
And the main partition is not quite exactly the same
I don't have the star screw driver to replace it yet .. so I don't know if it works or not
I cloned my original HDD to SSD and saved the original for a backup. To keep it relatively up to date I re-installed it and installed the windows 10 upgrade from the "Get Windows 10" taskbar icon. I've reverted back to my SSD with Windows 8.1 in...
Hi all, i have a new SSD HDD arriving in the post tomorrow and i am wanting to know if my Windows 10 Pro x64 OS can be easily cloned as once i have started the process i will not have a laptop to use to browse this site to troubleshoot any issues i...
I have a HP Compaq desktop with Windows 7 Home ready to upgrade to Windows 10 when it's available. I'm not going to install all this stuff that Microsoft is sending out for we all to download and install. From the many posters having their...