SATA SSD to NVMe query

Recently bought a 1TB NVMe drive to replace the 512GB SATA SSD I had previously. I cloned the old drive to the new one and adjusted partition sizes etc. accordingly and removed the old one so it's all working fine and the extra space is available. Something occurred to me this morning; at one point it was inadvisable to clone an existing Windows (10 in this case) install to a new SSD, something about Windows only detecting the target drive type and optimising itself accordingly at install time. Is that still the case, i.e. have I missed out on some performance and/or efficiency gains by cloning? If so then can these be retroactively applied or not?

Wasn't that an older issue more to do with migrating from a spinning disk to an SSD, where Windows wouldn't optimise for an SSD i.e. page file use and disk cleanup/maintenance?

Quote:

---

Originally Posted by Spreadie

Wasn't that an older issue more to do with migrating from a spinning disk to an SSD, where Windows wouldn't optimise for an SSD i.e. page file use and disk cleanup/maintenance?

---

bingo. Default sector size and associated drive alignment aren't any different between modern SSD and NVMe SFAIK. I've cloned my win 10 between NVMe and SSD and not noticed any issues. It's not just a win10 thing, certainly win7 used to ask you to set the sector size on install. There was also a hotfix to win7 to let it handle advanced drives with 4k sector sizes for more modern large capacity HDD.

https://docs.microsoft.com/en-us/win...ibility-update

Could be, that was a long time ago and I've slept since then :) But I guess I wondered if maybe there are further optimisations available due to the new drive using an NVMe interface as opposed to SATA, or different underlying memory type etc.

doubt it but IDK for definite.

i didn't have any issues when cloning from SSD to NVMe, my rig has been running happily on this OS install for about 18 months now.

I have heard of issues cloning to some NVMe drives. Sabrent was definitely one and I'm sure there was another. Adata maybe? It was caused by 4K sector size and very easily rectified. I never experienced any issues myself and I had assumed that sector size would something Windows or a cloning tool would take care of automatically, or at least prompt the user to change, but there were people complaining of issues at HUKD and a few other forums a while back. In general though there shouldn't be any problems.