Introduction
This tool is intended to enable/disable DevSleep feature on selected SSD models to prevent known drive detection issue.
Available Downloads
- OS Independent
- Size: 1.4 MB
- SHA1: B1EE07F0488FD0A928F8B194B7D5B5045633BF65
- OS Independent
- Size: 42 MB
- SHA1: 72406BB690B00BCDBA35B409393D045B1CC14899
Detailed Description
Not sure if this is the right driver or software for your component? Run Intel® Driver & Support Assistant to automatically detect driver or software updates.
Description:
This tool is intended to enable/disable DevSleep feature on selected SSD models to prevent known drive detection issue with Windows* 8/8.1/10/Server 2012.
DevSleep feature:
Device Sleep (or DevSleep/DEVSLP) is the latest feature in some SATA devices which allows them to go into a low power "device sleep" state. As an example, power consumption of Intel® Solid-State Drive Pro 2500 Series (2.5-inch) in DevSleep mode is only 5 mW vs 55 mW in idle state.
Drive detection issue related to DevSleep feature:
On some motherboards the BIOS and OS are enabling the feature on affected drives, but the motherboard does not signal to wake the SSD back.
Symptoms of this issue are:
- SSD disappears in Windows 8/8.1/10/Server 2012 install
- SSD disappears after resume from sleep
The root cause of this issue is in the motherboard BIOS implementation. The best way to solve this is to update motherboard to the latest BIOS and check with motherboard vendor if their BIOS solves this issue. For the customers who do not have BIOS fix from motherboard vendor, or for any reasons do not want to contact motherboard manufacturer or do want fix from Intel, we are offering this tool which disables DevSleep feature on affected drives.
Affected drives:
- Intel® Solid-State Drive Pro 2500 Series
- Intel® Solid-State Drive 530 Series
- Intel® Solid-State Drive 535 Series
Disclaimers1
Product and Performance Information
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.