- Jul 9, 2013
- 10
- 0
- 18,510
I recently got a 1 TB SSD (WD Blue SA510) to replace my old 1TB HDD. Note that this is not the boot drive (I have a smaller SDD that serves as a boot drive).
I cloned the HDD to the new SSD, took the old HDD out and assigned the old HDD drive letter to the SSD. Everything worked fine for a couple days, then the new SSD disappeared from Disk Management and the BIOS. I took it out and put the old HDD in and everything went back to normal.
I have heard this likely has to do with the cloning process also closing the UUID of the original drive, and that Windows 10 check every few days for such things and that the secure boot function flagged the new drive as a security threat. Since it isn’t a boot drive though, I wasn’t sure if this is true?
Another puzzling thing is that when I put the new SSD into an enclosure and try to look at its contents on a different computer, I can’t see the drive then either. It seems unlikely the drive is bad since it’s new and was working. Is this really an issue with the UUID needing to be changed after cloning? Thanks.
I cloned the HDD to the new SSD, took the old HDD out and assigned the old HDD drive letter to the SSD. Everything worked fine for a couple days, then the new SSD disappeared from Disk Management and the BIOS. I took it out and put the old HDD in and everything went back to normal.
I have heard this likely has to do with the cloning process also closing the UUID of the original drive, and that Windows 10 check every few days for such things and that the secure boot function flagged the new drive as a security threat. Since it isn’t a boot drive though, I wasn’t sure if this is true?
Another puzzling thing is that when I put the new SSD into an enclosure and try to look at its contents on a different computer, I can’t see the drive then either. It seems unlikely the drive is bad since it’s new and was working. Is this really an issue with the UUID needing to be changed after cloning? Thanks.
Facebook
Twitter
Instagram