Upgrade to small ssd

The Crucial website probably just isn't updated.  However, the MX500 is an M.2 SATA drive.  You'd get much better performance with an M.2 NVMe drive.  Whereas SATA drives top out around 550 MB/s, NVMe drives can deliver over 3 GB/s if they're not bottlenecked by the system -- and even when they are, they'd still deliver about 1.8 GB/s.  So you might want to think about spending a bit more to get one.

According to Dell's own Specifications document for the Inspiron 7570 here, the system has a 2.5" drive bay and an M.2 slot.  You could of course install a SATA SSD into the 2.5" bay if you wanted, but in addition to that, the M.2 slot supports both SATA and NVMe SSDs.  It says up to "512GB PCIe x4 NVMe drive", but there's absolutely no reason that a larger SSD wouldn't work if you wanted one.  It's likely that Dell simply didn't test a higher capacity SSD in this system and therefore won't officially claim compatibility.  But if you wanted to stick with the MX500 M.2 SATA drive, that should absolutely work too.

Hello,

Interesting information about that better performance i will have a look at it thank you for the suggestion.

it looks like  i can select my ssd within Macrium reflect click "image this disk" store this image on the 2.5 inch disk then in reflect choose "other tasks => Add Recovery Boot Menu Option shutdown my laptop replace the ssd and start from the recovery boot menu option .

No you can’t. The recovery boot menu option adds a boot entry to your Windows boot configuration database, but that won’t be usable after you physically remove your Windows drive — which is why you need to have Rescue Media to boot from.

I’ve used Reflect for years and worked in IT for 15 years. If you follow the steps I described above, it will work. If you decide to go your own way, I have no idea what you’ll end up with.

Ok just purchased a new m2 ssd and a usb stick i didn't have a spare one that was large enough to create the rescue media .The usbstick used for rescue media creation apparently needs preperation accoreing to this post on macrium support.

---

@confuseduser43 wrote:

Ok just purchased a new m2 ssd and a usb stick i didn't have a spare one that was large enough to create the rescue media .The usbstick used for rescue media creation apparently needs preperation accoreing to this post on macrium support.

---

Rescue Media only takes a few hundred MB, so any USB stick made in the last decade or so should be fine.  You only need to prep it if the flash drive ships without an MBR, which is pretty rare, and Reflect 7.2 won't require prep ever, although that's still in beta testing with no firm launch date.

I was in a similar situation but in my case the USB error was too many partitions. Since my system boots UEFI I had to format the USB in FAT32 (per instructions on the Reflect web site). Worked like a charm. I also had a system where I was replacing the NVME SSD with a larger NVME SSD. I cloned to a 2.5" SSD then cloned back to the new NVME. Not very elegant but it worked. In that case I used Acronis True Image. But to be honest I find Macrium much easier and user friendly.

---

@JOcean wrote:

I was in a similar situation but in my case the USB error was too many partitions. Since my system boots UEFI I had to format the USB in FAT32 (per instructions on the Reflect web site). Worked like a charm. I also had a system where I was replacing the NVME SSD with a larger NVME SSD. I cloned to a 2.5" SSD then cloned back to the new NVME. Not very elegant but it worked. In that case I used Acronis True Image. But to be honest I find Macrium much easier and user friendly.

---

Just in case it's useful in the future, if you had no intention of ever booting the 2.5" SSD, you could have imaged to that SSD instead of cloning to it.  It would have made much less of a mess on the 2.5" SSD (single file rather than a whole partition layout), it would have allowed you to preserve any existing data on the SSD, and it would have been a bit faster since it could have used compression, which means writing less data to the 2.5" SSD, and the destination write speed is almost always the bottleneck in these operations.

Good to know and thanks. FYI..yes it was a boot drive. I went from 250GB to 480GB. The larger drive was at a price too good to pass up. Yes I know, kind of a geek move but a bit of a slave to technology and always looking for a good price on quality hardware.

I have created the rescue media and booted from it to ensure it actually works (it works).

I imaged my current ssd and verified the image (no errors shown)

One thing is stopping me from doing the final step when i boot from the rescue media Macrium Reflect seems to swap my drive letters could this cause problems ? you can see in the image what i mean by that

OS label should be (C:)

Data label should be (D:)

not the other way around i don't trust this....

Fyi your screenshot is sideways, but drive letters in Rescue are unimportant.  They're dynamically assigned by the OS at every boot, whether that OS is full Windows or Windows PE, which is what Rescue Media uses.  There's nothing on a partition that says, "I should always be assigned drive letter D", so the Rescue Media OS doesn't have a way to know which drive letters your normal Windows installation assigns to which partitions.  It will absolutely not make a difference though.  "Full" Windows always assigns the partition it boots from as drive letter C, but when you're in Rescue Media, you didn't boot from your normal C drive, so it doesn't get special treatment there.  Otherwise, Windows assigns subsequent partitions using the next available drive letter unless the user has previously specified a different letter manually, in which case it will assign that if available -- but again that's only because that instance of Windows knows about that.  There's nothing stored on the partition itself that manages this.

Again, I've performed this process MANY times in my IT career, and many times specifically with Reflect.  But if you don't trust my guidance, then you may want to consider reading Reflect's documentation for yourself instead, which incidentally is better than most.  But otherwise, I'm really not what you're worried about here.  Absolute worst case, the restore to your new SSD fails due to some freak issue, and you still have an intact image backup that you just captured and your intact original hard drive.  That's a completely solid contingency position.

By the way, if the first test boot from the new SSD doesn't work, boot back into Rescue Media and run Fix Boot Problems, then try again.