1
1
I am genuinely at a loss here after almost a week of trying to fix this problem.
I've been running my 256GB XPS 13 9360 for a little more than a year now, and I decided to buy a new SSD to upgrade my tiny storage since I'm constantly running out.
I bought the XPG SX8200 Pro 1TB, which I thought was a very good upgrade.
I followed the online tutorials, which made it out to be really simple. I backed up my current SSD to a external HDD with Macrium Reflect and then restored it onto the new SSD. Everything went well until trying to boot up with the now (cloned) SSD.
The Dell logo would show up, with the spinning dots. That would stay for 1-2 minutes and then immediately my computer would power down and restart itself. I've tried force shutting down three times to get into the Windows repair, but the same thing happens except with the repair text above the spinning circles.
I've tried turning on/off secure boot, tried changing POST behaviour. I've found that:
UEFI Boot (Secure Boot on/off) gives behaviours above
Legacy Boot says no OS can be found
I've tried repeating the cloning process to no avail, and I've plugged in the SSD to another laptop of mine with the same results.
In the end I decided to order a Nvme to USB adapter and cloned the disk directly, which I just now finished, and the SAME THING happened.
I honestly don't even know what to do now.
And there's an even weirder behaviour. I burnt the USB rescue media for Macrium Reflect before - and this is the behaviour
With original SSD: Boots as expected
With NO SSD: Boots as expected
With CLONED SSD: Won't boot at all
Why would this even affect the USB Boot? I'm so confused.
Andy
Posted 2019-11-18T13:18:25.647
Reputation: 11
Did you update BIOS? Are you sure the BIOS will recognize 1 TB? I have an older laptop that will not accept a 1 TB drive. – John – 2019-11-18T13:20:48.227
I've gone into the BIOS and it recognises the drive being there as well as the capacity, and if I plug it into the adapter I can pretty much use it like an USB – Andy – 2019-11-18T13:22:25.317
You may need to back up the information from the old drive and install Windows fresh on the new drive – John – 2019-11-18T13:24:19.363
That's what I'm thinking of as a last resort :( But I'm hoping that there's a way to just clone the drive over – Andy – 2019-11-18T13:26:45.947
Do a fresh new installation of Windows in the new SSD and copy the old data, seems the issue is with the current image. – CaldeiraG – 2019-11-18T13:27:07.020
If I were to do a fresh new installation of Windows, would I need to purchase a new license code? – Andy – 2019-11-18T13:28:23.007
1
Try Adata's cloning software>>>>>http://www.adata.com/us/ss/software-6/
– Moab – 2019-11-18T13:28:24.6701No, you wouldn't need a new license code because it's already binded with your computer (assuming it's a OEM license). Windows will activate itself once you finish the installation. – CaldeiraG – 2019-11-18T13:30:08.867
https://superuser.com/questions/1076218/win10-oem-key-extraction-no-msdm-tab – CaldeiraG – 2019-11-18T13:31:07.347
Okay, sounds good! I'm going to try to clone it a few more times and just re-install if it still doesn't work – Andy – 2019-11-18T13:33:03.250
Have you cloned the ESP as well? – None – 2019-11-18T14:06:10.827
1Even new SSD often need SSD firmware update. Have you checked if you have latest firmware for your new drive? – oldfred – 2019-11-18T15:17:07.857
Was the previous drive also an NVMe? – Smock – 2019-11-18T16:10:19.163
Yes! The ESP is cloned over as well. – Andy – 2019-11-18T21:35:22.017
I haven't checked for firmware upgrades - will do so today – Andy – 2019-11-18T21:35:42.613
Yes, the previous drive was also Nvme - it is to the same specs except the capacity. – Andy – 2019-11-18T21:36:17.190