Strange problem when migrating to and from SSD

[shunsuu]

This problem has occurred twice already and although the solution works, it makes no sense to me. So here's what happened:

I migrated from a 256gb SSD to Samsung 850 Pro 512gb using Aomei Partition Manager. The migration itself was seamless and I was able to boot into windows successfully. However, here's the problem. The mouse moves, I can open up browsers and browse the net but I just cannot run any programs. Even task manager doesn't open up. None of it runs (word, file explorer, pdf etc). After extensive searching, some guy mentioned that migrated SSDs somehow become "write protected" and that's why it works momentarily as windows loads everything into the ram during bootup and once you're inside windows and try to do something, you are unable to do as the data is not able to be written into the storage.

The solution was to install Intel Rapid Storage Technology and it magically seemed to do the trick. The same issue happened again a few mths ago when I migrated from the 512gb SSD to a 1TB one. Migrated and booted but can't run programs whatsoever. Intel RST driver fixed it. By right seems like we should'nt need the RST driver for current gen drives like SSD. So I'm quite puzzled. Anyone encountered a similar problem and found a proper solution?

 

[jtjt00]

Best is to clean install. Migration will cause funny issues later down the road.

 

[Sausage]

I had a similar problem on a new ssd
After migration

Windows 10 loads but hen I cannot open anything

When I reboot it works

A few times already

Sent from Xiaomi MI MAX using GAGT

 

[it_geek]

I have used Symantec Ghost to do before. (from HDD -> SSD -> HDD -> SSD -> BIGGER SSD)



Never had a problem. Only a faster computer

 

[Illusionist_85]

I would rather backup my browser profile n my user login folder n do a clean installation

Sent from 穷挫矮胖永独 using GAGT

 

[shunsuu]

I had a similar problem on a new ssd
After migration

Windows 10 loads but hen I cannot open anything

When I reboot it works

A few times already

Sent from Xiaomi MI MAX using GAGT

Well, yea I tried restarting many times. Still same. I have about 30s to do something before I am unable to anything at all. So I installed the intel RST drivers in that small window and it just started working lmao

 

[shunsuu]

I have used Symantec Ghost to do before. (from HDD -> SSD -> HDD -> SSD -> BIGGER SSD)



Never had a problem. Only a faster computer

Maybe its a free software problem.

 

[shunsuu]

I would rather backup my browser profile n my user login folder n do a clean installation

Sent from 穷挫矮胖永独 using GAGT

I mean yea, clean install is pretty straight forward. The challenge is to get it to work seamlessly using migrating tools.

 

[it_geek]

I don't know how Aomei Partition manager works.


Assuming that Aomei DID NOT migrate the ACLs correctly, I suspect this symptom occurs because the files on the new drive don't have the correct permissions. If that is the case it becomes ***** messy to fix.


Resetting the ACL list will only make it worse especially on Windows Vista and newer OSes. Don't try that.


I got the workaround for this but it's v v v complicated. If you are game enough to try it... let me know. Don't cry once you begin ah... cos cannot turn back once you start

 

[JayceOoiCom]

Best is to clean install. Migration will cause funny issues later down the road.

Agree. And make sure you format SSD correctly to get the best performance out of it.

 

[watzup_ken]

May be its me, but I have never migrated one drive to another without problems. Especially when using these migration softwares.

 

[limcc]

I always use AOMEI bootable medium to clone systems, they always work, even to different/dissimilar hardwares--AOMEI pro version.

Remember to remove the older drive during first boot or weird things might happen. eg, the system might boot from the 1st/active drive but system partition get pointed to the old drive which mess up all the system paths.

 

[it_geek]

I always use AOMEI bootable medium to clone systems, they always work, even to different/dissimilar hardwares--AOMEI pro version.

Remember to remove the older drive during first boot or weird things might happen. eg, the system might boot from the 1st/active drive but system partition get pointed to the old drive which mess up all the system paths.

Yes. If you forget to do that - the drive volume IDs will conflict and one will trigger an error. WCS is will trigger the ACL reset.

 

[shunsuu]

I don't know how Aomei Partition manager works.


Assuming that Aomei DID NOT migrate the ACLs correctly, I suspect this symptom occurs because the files on the new drive don't have the correct permissions. If that is the case it becomes ***** messy to fix.


Resetting the ACL list will only make it worse especially on Windows Vista and newer OSes. Don't try that.


I got the workaround for this but it's v v v complicated. If you are game enough to try it... let me know. Don't cry once you begin ah... cos cannot turn back once you start

Yesterday I tried migrating from 1 SSD to another using Samsung Magician and surprisingly it worked without a problem. Maybe its really an Aomei program issue.

I am quite pleasantly intrigued by this workaround. I will send u a pm and pls share any guide u have. Quite keen to see what goes on the backend for the permissions.

 

[LiLAsN]

Never heard such a problem. Cloning a drive should be seamless and the duplicate drive should act the same way without any difference except for partition size.
Looks more like a case of a lousy cloning software or even a virus in the software.
Don't tell me you don't even use any antivirus except Norton.