Here's is a sample of retrieving disk information via CMD, DISKPART, WMIC and PowerShell. I mentioned in a thread I created that MSFT_Disk was the base class, but CIM_DiskDrive/Disk, Win32_Disk, MSFT_MediaStorageProvider seems like they are missing alot of properties, or properties aren't named in similar fashion - but also - enumerator values I'm finding this out now - as I'm creating my own Windows Deployment for my ASUS Notebook - because I was sick to death with performance loss and hardware reconfiguration that occurs during Windows (Major Version 1507/1511/1607/1703) Updates. I basically read through the API - and am not convinced that each of the departments communicate to each other to give the classes *near* identical values for corresponding member properties between classes - when they really should be. Hi, a year late - but I thought I'd give my 2cents on this topic: Other APIs of Microsoft (like Storage Query Property) set this namespace ID by themselves, and we don't have to set this from user side.
Is there any other way for setting this namespace identifier in the SCSI command that we are sending from the host side? Or is this a driver error that its SCSI-NVME translation does not allow setting a namespace identifier field in its CDB. Is returning a error in sense data as Access Namespace identifier to the drive in case of the Security Receive command, and therefore, SCSI We can see the commands are reaching the drive, but the translation is not able to send the correct For performance measurement purposes, the SSD may be restored to FOB state using the secure erase command. Typical I/O performance numbers as measured using CrystalDiskMark® with a queue depth of 128 and write cache enabled. Of SCSI-NVME Translation, in which a SCSI command is sent from the host and is translated to NVME command by the SCSI kernel stack, and then sent to the drive. Crucial P5 Plus PCIe® 4.0 3D NAND NVMe M.2 SSD. Security Receive and Security Send, we are using their support We are not supposed to use our own driver to talk to drives, so for sending most of the commands, we have to rely on whatever is available from Windows 10. We are developing an application to manage NVME Devices in Windows 10.