Windows 10: Clean windows 10 install onto a new SSD (samsung 850 EVO 250 gb) or

When I mount the drive in a Kingston drive adapter , the Samsung Magician software does not recognize the drive although Disc check identifies fine? Tried several different USB connectors & a second computer . Is there a workaround to migrate my win 10 system to the SSD - without buying a new 2.0 USB cable Sata ?

Maybe a clean install would be better - Can I do this & somehow still identify WIn10 as good?

Help for an old bugger appreciated

:)

 

Hanging at "Verifying DMI Pool Data" when booting

My trusty old PC has worked perfectly for years on Windows 7, which runs from a Samsung Pro EVO 850 256gb SSD drive.

A few months ago I decided to upgrade to Windows 10, but I wanted to do a clean install (I don't like upgrades), which would also allow me to dual boot, so I could continue to use Windows 7 until I was perfectly
happy with Windows 10 i.e. all software was installed and working.

To this end, I purchased a new Samsung EVO 840 500gb SSD drive, with the intention of using this in my desktop for a short period, then switching out one of the (slow) 500gb drives from my laptop and using
the SSD drive in the laptop. This would hopefully provide more performance to the laptop, which was struggling since upgrading to Windows 10 (clean install again).

Because the original 256gb Pro EVO 850 would remain in my desktop, I had to get Windows 10 onto this "old" drive, so here's what I did:

1. Duplicated the original Pro EVO 850 Windows 7 install onto the new EVO 840 SSD drive.

2. Wiped the original Pro EVO 850 SSD drive (Windows 7 is now on the new 840 SSD drive).

3. Clean install of Windows 10 onto the original Pro EVO 850 SSD drive.

On booting, I was presented with a Windows 10 screen allowing me to choose Windows 7 or Windows 10. Perfect. I have been using this config for a couple of months now and both OS's are working well on the
desktop.

I've now finished setting up Windows 10, so want to remove the new EVO 840 SSD drive (contains Windows 7) from my desktop, so I can use it in my laptop. However, when I disconnect the new EVO 840 SSD drive
from my desktop, the machine doesn't boot and hangs at the following message:

"Verifying DMI Pool Data".

I've tried using the original Windows 10 iso image (on a DVD) to "repair" Windows 10, but this doesn't seem to have any affect. The only way I can get my desktop to boot is to have the Windows 7 disk connected
(new EVO 840 SSD).

To summarise, I have two drives:

1. Original Pro EVO 850 256gb SSD - Windows 10 installed

2. New EVO 840 500gb SSD - Windows 7 installed

With both drives connected, I get a choice of which OS to run and both OS's work fine.

With only drive 1 installed, I'm unable to boot into Windows 10 as it hangs at the Verifying DMI Pool Data message.

I would appreciate any advice on how to overcome this boot issue.

 

Error code 0xc0000221

I can't install Windows with a USB on my new computer, it keeps crashing when it is doing the final parts of the installation and after it gives an error code 0xc0000221. I have no clue whatsoever what the
problem may be.

SSD: Samsung 850 EVO 250 GB

Case: Cooler Master CM Force 500

Power Supply: Cooler Master G450M

Motherboard: MSI Z97 PC Mate

RAM: Crucial Ballistix Sport 2x 8GB

CPU: Intel I5 4690K

 

Hi Davee3, welcome to tenforums *Smile I had a similar issue with a Samsung EVO 128G SSD. No matter what I tried the migration software/function would not work. I ended up taking the existing SSD (Crucial 64G) with W10 on it out of the computer, installed the new SSD, booted from install media (W10 iso on a USB or cd) chose repair, and then restored with a backup/image I had (from my internal backup HDD) to the new SSD.

This was a workaround for me to have all things remain, and not start over with a clean install. I've actually done this a couple times, once with Win7, and once with W10. Both times went without issues, except on Win7 I had to boot from install media and repair start to get it to boot from the new SSD.

 

Well I went to samsung Data migration update & found the Update check from the original install did not give me the latest update So I updated again , plugged in the new SSD still in the kingston adapter & VOILA - New drive showed up as a destination drive & cloning is underway. Should be in good shape at finish Will report

 

That's great! good to hear things are on the road to recovery.

I imagine it's going to be all good from here on out *Cool

 

The cloning worked fine wirth latest version downloaded - ignore the update option