Defraggler Pro detects SM951 NVME SSD as a HDD
Laptop Model: Razer Blade Stealth 7500U, 512GB SSD
Defraggler Pro detects SM951 NVME SSD as a HDD
Laptop Model: Razer Blade Stealth 7500U, 512GB SSD
Works fine with me. May be there is a problem with your version.
Since you have pro, you might want to jump over this user forum and get the priority support your pro license covers.
Same problem here.
Razer Stealth 2016 model, with 1TB Samsung NVMe drive, detected as HDD not SSD.
Notebook:
https://www.razerzone.com/gaming-systems/razer-blade-stealth
Drive:
http://www.samsung.com/semiconductor/products/flash-storage/client-ssd/MZVKW1T0HMLH?ia=831
Defraggler 2.21.993 on Win10 Pro x64 Insider
I have a Samsung 960 Pro M.2 drive and after several months it is still not recognised as an SSD drive. It is not a new drive any longer and is a well-recognised brand name.
What is going on at Piriform that they can ignore an issue that many have complained about and with other M.2 drives as well, Speccy can recognise as a SSD, they send screenshots and still Piriform fail to rectify it - do they not read these columns ? If so, what's the point in posting here ?
as you state, it is a long known issue with DF.
the Admin and Dev teams are aware of it.
last I heard something on this subject from the Admin team was that a feature was being investigated to allow manual override - but that was some time ago.
I'm just another Professional Defraggler user with issues identifying my PCIe NVMe SSD as a HDD.. PC created April 2017 with regular SSD (2.5 in format 512 Gb) as boot device. The SSD (identified by DF as SSD) turned out to be a turkey so I decided to try one of the newer WD PCIe NVMe SSD drives {PCIe M.2 2280 model WDS512g1XOC}.
Using Windows Tools will optimize the drive like a SSD. Using Defraggler it appears to actually defrag the drive {screen captures available).
Same issue here:
Having just installed a Samsung 960 Evo 500Gb as boot drive on my NVMe port, and Defraggler detects it as a HDD, preventing from optimizing it but offering defrag.
This should not be a hard thing to fix...