SSD KC2000 NVMe PCIe - Support

This is common for flash storage, whether internal SSD, Flash Card, or external USB storage, and is due in part to a variance in how flash memory vs spinning platter hard drive manufacturers calculate megabyte. Hard drive manufacturers calculate a megabyte (or 1,000x1,000 bytes) as 1,000KBs, whereas the binary calculation for flash-based storage is 1,024KBs.

Example: For a 1TB flash-based storage device, Windows will calculate it as having a capacity of 931.32GB. (1,000,000,000,000÷1,024÷1,024÷1,024=931.32GB).

Furthermore, Kingston reserves some of the listed capacity for formatting (e.g., File Allocation Table) and other functions such as firmware and/or controller-specific information, and thus some of the listed capacity is not available for data storage.

FAQ: KDT-010611-GEN-06

High-performance NVMe SSDs require adequate airflow for maximum bandwidth and performance. During heavy workloads or extensive benchmarking, the drive will heat up and the controller firmware may implement thermal throttling in order to maintain proper operating temperature and ensure drive integrity. If performance degradation is observed within these circumstances, confirm the SSD is receiving adequate cooling and/or increase the system’s fan speed to reduce drive temperatures.　

Note: Thermal throttling will engage when temperature reaches 80°C

FAQ: KSD-060117-NVME-02

Our NVMe SSD rely on native Linux and Microsoft NVMe drivers. Microsoft’s native NVMe driver issues Forced Unit Access (FUA) IO writes and Flush commands to NVMe devices that have a volatile write cache. This, in effect, undermines the write caching on the target SSD by often bypassing the DRAM cache and writing directly to NAND. As a result of this behavior, the NVMe SSD’s performance is reduced. To obtain maximum performance, you need to disable write cache buffer flushing on the target drive within Windows.　　

Steps to Disabling Write-Cache Buffer Flush　

1. Open Device Manager　

2. Select Disk Drives and expand, then select target drive.　　

3. Right-click and select Properties　

4. Check “Turn off Windows write-cache buffer flushing on the device”　　

a. Note: By disabling write-cache buffer flushing on the device, you run the risk of losing data in transit and/or data corruption in the event of a power failure. Only disable this feature if you are aware of the risks associated with it.　

Performance Comparison

FAQ: KSD-060117-KC1000-04

NVMe drives are plug and play with Windows 8 and above and Windows Server 2012R and above. Therefore, Kingston does not provide additional drivers. NVMe drives will also work with the latest versions of Linux. Please note: macOS is not supported.

FAQ: KSD-060117-NVME-01

To determine which NVMe driver is in use, you can run the AS SSD benchmark tool and select your Kingston NVMe SSD from the drop-down menu. This will report the driver being used for that drive. If the driver is "iaStorAC" then your drive is using the Intel driver. If the driver is "stornvme" then your drive is using the Microsoft driver. Please note: Kingston's NVMe SSD drives are plug and play and therefore, we do not provide additional drivers.

FAQ: KSD-001525-001-00

The easiest way to ensure that your new SSD appears as your boot drive is to ensure that it is the only storage device connected during installation. 
If this is not possible, or if you previously cloned your old data to your new drive, confirm that the new drive appears as a boot device in the system BIOS, then select it for booting.

FAQ: KSD-012010-001-03

Windows 7 doesn’t natively support NVMe SSDs. If you wish to install Windows 7 on your NVMe SSD, please refer to this Microsoft hotfix explanation:

https://support.microsoft.com/en-us/topic/update-to-add-native-driver-support-in-nvm-express-in-windows-7-and-windows-server-2008-r2-03cd423b-d42e-66c2-722b-019d16455a6b

FAQ: KSD-012010-001-06

No, Kingston NVMe SSDs do not require a special NVMe driver. The inbox drivers present in Windows 8 and later are sufficient.

FAQ: KSD-012010-001-07

First, you should confirm that the SSD is seen within the system BIOS. Enter your BIOS (usually, Del, F2, F10, or F12 key) and navigate through your storage configuration menu(s) to see if the drive is correctly identified and present. If the drive isn’t present, power off the system, check the installation and connections to confirm the drive is seated and/or connected properly. 

If the drive is present in the BIOS, you may need to initialize the disk within the operating system. Follow the steps below to initialize.

For Windows:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Windows OS.
Step 2: Press Windows + X and choose Disk Management.
Step 3: If the SSD is new and not initialized, a popup will appear saying "Initialize Disk."
Step 4: Choose between: MBR (Master Boot Record): Suitable for drives under 2TB and older systems. GPT (GUID Partition Table): Recommended for modern systems and drives larger than 2TB.
Step 5: Click OK to initialize the disk.
Step 6: Once initialized, you'll see the SSD as "Unallocated." Right-click on it and select New Simple Volume.
Step 7: Follow the on-screen prompts (keeping all defaults is Okay)  to format and assign a drive letter to the SSD.

For macOS:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Mac OS.
Step 2: Open Disk Utility (you can find it using Spotlight with Cmd + Space and then typing "Disk Utility").
Step 3: In the left pane, select your SSD.
Step 4: Click on Erase.
Step 5: Provide a name for the drive, and under Format, choose: APFS for newer Macs and SSDs. Mac OS Extended (Journaled) for older systems or HDDs.
Step 6: Click Erase. Once the process completes, the SSD will be ready for use.

For Linux:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Linux OS.
Step 2: Open a terminal.
Step 3: Enter sudo fdisk -l to list all connected drives. Identify your SSD by its size and note the device name, e.g., /dev/sdb.
Step 4: Initialize the SSD using fdisk or parted. Here's a basic guide using fdisk: Enter sudo fdisk /dev/sdb (replace /dev/sdb with your SSD's device name). Press g to create a new GPT partition table. Press n to create a new partition. Follow the prompts to specify the size and type. Press w to write the changes.
Step 5: Format the new partition on the SSD (e.g., /dev/sdb1). You can format it with the filesystem of your choice: For ext4: sudo mkfs.ext4, For ext3: sudo mkfs.ext3 /dev/sdb1 /dev/sdb1, For FAT32: sudo mkfs.vfat /dev/sdb1
Step 6: Mount the SSD: Create a mount point: sudo mkdir /mnt/myssd, Mount the SSD: sudo mount /dev/sdb1 /mnt/myssd, Remember to replace /dev/sdb1 with your SSD's partition name.

FAQ: KSD-012010-001-15

Please refer to this blog post discussing M.2 technology.
https://www.kingston.com/blog/pc-performance/two-types-m2-vs-ssd

FAQ: KSD-012010-001-16

There are a variety of external enclosures available on the market. While Kingston aims to be compatible with all system types, occasionally, there may be an incompatibility. If you continue to have trouble with your external SSD enclosure, you may want to try a different enclosure.

FAQ: KSD-012010-001-18

Secure Erase User Guide for Linux

This guide will walk you through securely erasing your Kingston SSD using Linux tools.

SATA Secure Erase Procedure

Warning

Please make sure to have a full backup of any important data before you proceed!

Prerequisites

• You must have root privileges.
• You must have your SSD connected to the system as a secondary (non-OS) drive.
• You must have lsscsi and hdparm installed. You may need to install them with your distribution’s package manager.
• Your drive must not be in a security freeze.
• Your drive must not be password protected.

Instructions
1. Find the device name (/dev/sdX) of the drive you wish to erase:

# lsscsi

2. Make sure drive security is not frozen:

# hdparm -I /dev/sdX | grep frozen

If the output shows "frozen" (instead of "not frozen") then you cannot continue to the next step. You must try to remove the security freeze by trying one of the following methods:

Method 1:
Put the system to sleep (suspend to RAM) and wake it up. On most distributions the command to suspend is:

# systemctl suspend

Now issue the hdparm command again. If it worked the output will show "not frozen" (instead of "frozen").

Method 2:
Hot plug the drive. This is done by physically unplugging the SATA power cable from the drive and plugging it back in while the system is powered on. You may need to enable hot plug in BIOS. Not all systems support hot plug.

Now issue the hdparm command again. If it worked the output will show "not frozen" (instead of "frozen").

3. Set a user password on the drive. The password can be anything. Here we are setting the password to "p":

# hdparm --security-set-pass p /dev/sdX

4. Issue the secure erase command to the drive using the same password: 1234567890 - 1234567890 -

# hdparm --security-erase p /dev/sdX

This command may take a few minutes to complete. The drive password is removed upon successful completion.

If the secure erase is interrupted or otherwise fails your drive may become security locked. In this case you can remove the security lock using the command below and then try the secure erase procedure again:

# hdparm --security-disable p /dev/sdX

SATA Secure Erase Example

NVMe Secure Erase Procedure

Warning

Please make sure to have a full backup of any important data before you proceed!

Prerequisites

• You must have root privileges.
• You must have your SSD connected to the system as a secondary (non-OS) drive.
• You must have nvme-cli installed. You may need to install it with your distribution’s package manager.
• Your drive must not be password protected.

Instructions

1. Find the device name (/dev/nvmeXn1) of the drive you wish to erase:

# nvme list
2. Issue the format command to the drive. Here we set the secure erase setting to 1 which indicates a user data erase:

# nvme format /dev/nvmeXn1 --ses=1

This command may take a few minutes to complete.

NVMe Secure Erase Example

FAQ: KSM-SE-LIX

SSD firmware is the integrated software within an SSD that manages its operations, including communication with the host system, data storage and retrieval, wear leveling, and error correction. Kingston recommends that you always maintain the latest firmware.

If your SSD requires new firmware, you will receive a notification when running Kingston’s SSD Manager software, located here: www.kingston.com/ssdmanager

FAQ: KSD-012010-001-11

Trim and garbage collection are technologies that modern SSDs incorporate to improve both their performance and endurance. When your SSD is in its fresh out of box condition all of the NAND blocks are empty so the SSD can write new data to the empty blocks in a single operation. Over time most of the empty blocks will become used blocks that contain user data. In order to write new data to used blocks the SSD is forced to perform a read-modify-write cycle. The read-modify-write cycle hurts the SSDs overall performance because it now must do three operations instead of a single operation. The read-modify-write cycle also causes write amplification which hurts the SSDs overall endurance.

Trim and garbage collection can work together to improve SSD performance and endurance by freeing up used blocks. Garbage collection is a function built into the SSD controller that consolidates data stored in used blocks in order to free up more empty blocks. This process happens in the background and is completely handled by the SSD itself. However the SSD may not know which blocks contain user data and which blocks contain stale data that the user has already deleted. This is where the trim function comes in. Trim allows the operating system to inform the SSD that data has been deleted so that the SSD can free up those previously used blocks. For trim to work both the operating system and the SSD must support it. Currently most modern operating systems and SSDs support trim however most RAID configurations do not support it.

Kingston SSDs take advantage of both garbage collection and trim technologies in order to maintain the highest possible performance and endurance over their lifetime.

Learn More

FAQ: KSD-011411-GEN-13

M.2 is the physical form factor. SATA and PCIe refer to the storage interface, the primary difference is performance and the protocol (language) spoken by the M.2 SSD (e.g., PCIe, SATA).

The M.2 spec was designed to accommodate both a SATA and PCIe interface for SSDs. M.2 SATA SSDs will use the same controller currently on typical 2.5-inch SATA SSDs. M.2 PCIe SSDs will use a controller specifically designed to support the PCIe protocol. Although each M.2 SSD can only support one protocol (e.g., PCIe, SATA), some systems may have M.2 sockets that support both PCIe and SATA. Please check your system's user manual to confirm.

FAQ: KSD-004005-001-00

ElectroStatic Discharge, ESD is simply the discharge of built up static electricity.ESD should not be taken lightly as this is one of the few things an individual can do to damage or destroy their computer or hardware components.It is like when you rub your feet on the carpet and you touch something metal.ESD can occur without the user feeling a shock and will occur when only working on the inside of the computer or handling hardware.

How to help prevent ESD
The best method of preventing ESD is to use an ESD wrist strap or a grounding mat or table.However, because most users do not have access to these items, we have included the below steps to help reduce the chance of ESD as much as possible.

• Standing – We recommend that you are standing at all times when working on the computer. Setting on a chair can generate more electrostatic.
• Cords - Make sure everything is removed from the back of the computer (power cord, mouse, keyboard, etc).
• Clothes - Make sure not to wear any clothing that conducts a lot of Electrical Charge, such as a wool sweater.
• Accessories - To help reduce ESD and help prevent other problem, it is also a good idea to remove all jewelry.
• Weather - Electrical storms can increase the ESD risk; unless absolutely necessary, try not to work on a computer during an electrical storm.In very dry areas, the air itself becomes a part of the electrostatic build-up mechanism every time there is an air flow (wind, air conditioning, blower) passing over an insulated surface.Do not let high humidity levels build a false confidence, and beware of corrosion problems with interconnects and other electrical interfaces.

To learn more about ESD and how to protect your electronics, please refer to the below site.

ESD Association
https://www.esda.org

FAQ: KTC-Gen-ESD

Click here to learn more about the differences between these two types of SSDs.
https://www.kingston.com/blog/pc-performance/nvme-vs-sata

FAQ: KSD-012010-001-19

Kingston SSD Manager 1.1.2.6 will not offer firmware updates for NVMe SSDs until IEEE 1667 support has been disabled. In order to complete the firmware update you must do the following:

1. First, we recommend you backup your data.
2. Then use a secondary system to complete a REVERT using the PSID on the drive label. Note: Performing a REVERT will securely erase all data on the drive.
3. Disable IEEE 1667 support
4. The firmware update will become available upon refresh or restart of KSM

FAQ: KSM-001125-001-01

Kingston SSD Manager (KSM) is ending support for Microsoft Windows 7. The latest version of KSM with Windows 7 support is v1.1.2.5. If you are using Windows 7 and experience complications with KSM, please make sure you have AHCI mode enabled in BIOS and install the latest Intel RST storage driver provided by your system manufacturer. If you still need assistance, feel free to contact our Kingston Technical Support department.

FAQ: KSM-001125-001-00

Your system may be loading the Intel RST driver instead of the Microsoft NVMe driver. There is a known compatibility issue with the Intel RST driver that interferes with NVMe firmware update commands. Additionally, KSM is only supported on Windows based systems. Therefore, if you are attempting to run KSM on a macOS or Linux based system, unfortunately these OS are not compatible with KSM.

FAQ: KSM-001125-002-01

Caution! The workarounds below will break RST RAID arrays and could lead to data loss. If your system has RST RAID arrays you should consider an alternate solution.

Workaround 1: Disable RST Control in BIO

This workaround requires BIOS options to enable or disable RST Control and is not available on all systems

Note: Please backup all important data before you proceed!

1. Restart and enter the system BIOS
2. Locate the RST Configuration settings in BIOS
3. Change "RST Controlled" to "Not RST Controlled"
4. Save and exit BIOS
5. Open KSM and update the drive firmware

Once these steps are completed you may optionally switch back to "RST Controlled" in BIOS.

Workaround 2: Switch from RAID to AHCI in BIOS

This workaround is to change your system storage mode from RAID to AHCI and should work on all systems.

Note: Please backup all important data before you proceed!

1. Open msconfig
2. Select the Boot tab
3. Check Safe boot (minimal)
4. Click OK and Restart
5. When the system restarts go into the system BIOS
6. Change the storage mode from RAID to AHCI
7. Save and exit BIOS
8. Wait for Windows to boot into safe mode
9. Open msconfig
10. Select the Boot tab
11. Uncheck Safe boot
12. Click OK and Restart
13. Wait for Windows to boot normally
14. Open KSM and update the drive firmware

Once these steps are completed you may optionally switch the storage mode back to RAID in BIOS.

FAQ: KSD-001525-001-01

When cloning to a new drive larger than the source drive, the software may not properly scale partition size. When this occurs, you might end up with unused space. To avoid this, follow our cloning instructions located here: www.kingston.com/cloning

FAQ: KSD-012010-001-04

SSD firmware is the integrated software within an SSD that manages its operations, including communication with the host system, data storage and retrieval, wear leveling, and error correction. Kingston recommends that you always maintain the latest firmware.

If your SSD requires new firmware, you will receive a notification when running Kingston’s SSD Manager software, located here: www.kingston.com/ssdmanager

FAQ: KSD-012010-001-11

Kingston does not offer DOS-based firmware updates at this time.

FAQ: KSD-012010-001-12

Unless explicitly indicated, no, an SSD update will not erase data from the drive. However, before performing any SSD firmware updates, Kingston recommends all data on the target drive be backed up before proceeding with the firmware update.

FAQ: KSD-012010-001-13

While it may be possible to update your target drive’s firmware via USB storage enclosure, Kingston does not recommend it. Proper update procedure involves having your target SSD connected directly to the system ports (e.g., SATA or NVMe).

FAQ: KSD-012010-001-14

When cloning to a new drive larger than the source drive, the software may not properly scale partition size. When this occurs, you might end up with unused space. To avoid this, follow our cloning instructions located here: www.kingston.com/cloning

FAQ: KSD-012010-001-04

There are a variety of external enclosures available on the market. While Kingston aims to be compatible with all system types, occasionally, there may be an incompatibility. If you continue to have trouble with your external SSD enclosure, you may want to try a different enclosure.

FAQ: KSD-012010-001-18

Please refer to this blog post discussing M.2 technology.
https://www.kingston.com/blog/pc-performance/two-types-m2-vs-ssd

FAQ: KSD-012010-001-16

First, you should confirm that the SSD is seen within the system BIOS. Enter your BIOS (usually, Del, F2, F10, or F12 key) and navigate through your storage configuration menu(s) to see if the drive is correctly identified and present. If the drive isn’t present, power off the system, check the installation and connections to confirm the drive is seated and/or connected properly. 

If the drive is present in the BIOS, you may need to initialize the disk within the operating system. Follow the steps below to initialize.

For Windows:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Windows OS.
Step 2: Press Windows + X and choose Disk Management.
Step 3: If the SSD is new and not initialized, a popup will appear saying "Initialize Disk."
Step 4: Choose between: MBR (Master Boot Record): Suitable for drives under 2TB and older systems. GPT (GUID Partition Table): Recommended for modern systems and drives larger than 2TB.
Step 5: Click OK to initialize the disk.
Step 6: Once initialized, you'll see the SSD as "Unallocated." Right-click on it and select New Simple Volume.
Step 7: Follow the on-screen prompts (keeping all defaults is Okay)  to format and assign a drive letter to the SSD.

For macOS:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Mac OS.
Step 2: Open Disk Utility (you can find it using Spotlight with Cmd + Space and then typing "Disk Utility").
Step 3: In the left pane, select your SSD.
Step 4: Click on Erase.
Step 5: Provide a name for the drive, and under Format, choose: APFS for newer Macs and SSDs. Mac OS Extended (Journaled) for older systems or HDDs.
Step 6: Click Erase. Once the process completes, the SSD will be ready for use.

For Linux:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Linux OS.
Step 2: Open a terminal.
Step 3: Enter sudo fdisk -l to list all connected drives. Identify your SSD by its size and note the device name, e.g., /dev/sdb.
Step 4: Initialize the SSD using fdisk or parted. Here's a basic guide using fdisk: Enter sudo fdisk /dev/sdb (replace /dev/sdb with your SSD's device name). Press g to create a new GPT partition table. Press n to create a new partition. Follow the prompts to specify the size and type. Press w to write the changes.
Step 5: Format the new partition on the SSD (e.g., /dev/sdb1). You can format it with the filesystem of your choice: For ext4: sudo mkfs.ext4, For ext3: sudo mkfs.ext3 /dev/sdb1 /dev/sdb1, For FAT32: sudo mkfs.vfat /dev/sdb1
Step 6: Mount the SSD: Create a mount point: sudo mkdir /mnt/myssd, Mount the SSD: sudo mount /dev/sdb1 /mnt/myssd, Remember to replace /dev/sdb1 with your SSD's partition name.

FAQ: KSD-012010-001-15

When cloning to a new drive larger than the source drive, the software may not properly scale partition size. When this occurs, you might end up with unused space. To avoid this, follow our cloning instructions located here: www.kingston.com/cloning

FAQ: KSD-012010-001-04

The easiest way to ensure that your new SSD appears as your boot drive is to ensure that it is the only storage device connected during installation. 
If this is not possible, or if you previously cloned your old data to your new drive, confirm that the new drive appears as a boot device in the system BIOS, then select it for booting.

FAQ: KSD-012010-001-03

No, Kingston NVMe SSDs do not require a special NVMe driver. The inbox drivers present in Windows 8 and later are sufficient.

FAQ: KSD-012010-001-07

Windows 7 doesn’t natively support NVMe SSDs. If you wish to install Windows 7 on your NVMe SSD, please refer to this Microsoft hotfix explanation:

https://support.microsoft.com/en-us/topic/update-to-add-native-driver-support-in-nvm-express-in-windows-7-and-windows-server-2008-r2-03cd423b-d42e-66c2-722b-019d16455a6b

FAQ: KSD-012010-001-06

First, you should confirm that the SSD is seen within the system BIOS. Enter your BIOS (usually, Del, F2, F10, or F12 key) and navigate through your storage configuration menu(s) to see if the drive is correctly identified and present. If the drive isn’t present, power off the system, check the installation and connections to confirm the drive is seated and/or connected properly. 

If the drive is present in the BIOS, you may need to initialize the disk within the operating system. Follow the steps below to initialize.

For Windows:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Windows OS.
Step 2: Press Windows + X and choose Disk Management.
Step 3: If the SSD is new and not initialized, a popup will appear saying "Initialize Disk."
Step 4: Choose between: MBR (Master Boot Record): Suitable for drives under 2TB and older systems. GPT (GUID Partition Table): Recommended for modern systems and drives larger than 2TB.
Step 5: Click OK to initialize the disk.
Step 6: Once initialized, you'll see the SSD as "Unallocated." Right-click on it and select New Simple Volume.
Step 7: Follow the on-screen prompts (keeping all defaults is Okay)  to format and assign a drive letter to the SSD.

For macOS:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Mac OS.
Step 2: Open Disk Utility (you can find it using Spotlight with Cmd + Space and then typing "Disk Utility").
Step 3: In the left pane, select your SSD.
Step 4: Click on Erase.
Step 5: Provide a name for the drive, and under Format, choose: APFS for newer Macs and SSDs. Mac OS Extended (Journaled) for older systems or HDDs.
Step 6: Click Erase. Once the process completes, the SSD will be ready for use.

For Linux:
Step 1: Confirm the drive is properly attached, and power on the system, then boot into Linux OS.
Step 2: Open a terminal.
Step 3: Enter sudo fdisk -l to list all connected drives. Identify your SSD by its size and note the device name, e.g., /dev/sdb.
Step 4: Initialize the SSD using fdisk or parted. Here's a basic guide using fdisk: Enter sudo fdisk /dev/sdb (replace /dev/sdb with your SSD's device name). Press g to create a new GPT partition table. Press n to create a new partition. Follow the prompts to specify the size and type. Press w to write the changes.
Step 5: Format the new partition on the SSD (e.g., /dev/sdb1). You can format it with the filesystem of your choice: For ext4: sudo mkfs.ext4, For ext3: sudo mkfs.ext3 /dev/sdb1 /dev/sdb1, For FAT32: sudo mkfs.vfat /dev/sdb1
Step 6: Mount the SSD: Create a mount point: sudo mkdir /mnt/myssd, Mount the SSD: sudo mount /dev/sdb1 /mnt/myssd, Remember to replace /dev/sdb1 with your SSD's partition name.

FAQ: KSD-012010-001-15

Please refer to this blog post discussing M.2 technology.
https://www.kingston.com/blog/pc-performance/two-types-m2-vs-ssd

FAQ: KSD-012010-001-16

There are a variety of external enclosures available on the market. While Kingston aims to be compatible with all system types, occasionally, there may be an incompatibility. If you continue to have trouble with your external SSD enclosure, you may want to try a different enclosure.

FAQ: KSD-012010-001-18

While it may be possible to update your target drive’s firmware via USB storage enclosure, Kingston does not recommend it. Proper update procedure involves having your target SSD connected directly to the system ports (e.g., SATA or NVMe).

FAQ: KSD-012010-001-14

Unless explicitly indicated, no, an SSD update will not erase data from the drive. However, before performing any SSD firmware updates, Kingston recommends all data on the target drive be backed up before proceeding with the firmware update.

FAQ: KSD-012010-001-13

Kingston does not offer DOS-based firmware updates at this time.

FAQ: KSD-012010-001-12

SSD firmware is the integrated software within an SSD that manages its operations, including communication with the host system, data storage and retrieval, wear leveling, and error correction. Kingston recommends that you always maintain the latest firmware.

If your SSD requires new firmware, you will receive a notification when running Kingston’s SSD Manager software, located here: www.kingston.com/ssdmanager

FAQ: KSD-012010-001-11