AHCI is supported out of the box on
Windows Vista and later,
Linux-based operating systems (since version 2.6.19 of the
kernel),
OpenBSD (since version 4.1),
NetBSD (since version 4.0),
FreeBSD (since version 8.0),
macOS,
GNU Mach,
ArcaOS,
eComStation (since version 2.1), and
Solaris 10 (since version 8/07).
DragonFlyBSD based its AHCI implementation on OpenBSD's and added extended features such as port multiplier support. Older versions of operating systems require hardware-specific drivers in order to support AHCI.
Windows XP and older do not provide AHCI support out of the box. The Windows inbox AHCI driver (StorAHCI.sys) does not offer
hardware acceleration.
System drive boot issues Some operating systems, notably
Windows Vista,
Windows 7,
Windows 8,
Windows 8.1 and
Windows 10, do not configure themselves to load the AHCI driver upon boot if the SATA controller was not in AHCI mode at the time the operating system was installed. Although this is an easily rectifiable condition, it remains an ongoing issue with the AHCI standard. The most prevalent symptom for an operating system (or systems) that are installed in IDE mode (in some BIOS firmware implementations otherwise called 'Combined IDE mode'), is that the system drive typically fails to boot, with an ensuing error message, if the SATA controller (in BIOS) is inadvertently switched to AHCI mode after OS installation. In Microsoft Windows the symptom is a boot loop which begins with a Blue Screen error, if not rectified. Technically speaking, this is an implementation bug with AHCI that can be avoided, but it has not been fixed yet. As an interim resolution, Intel recommends changing the drive controller to AHCI or RAID before installing an operating system. Inter alia with Windows 10 and 8, this can be fixed by forcing the correct drivers to reload during
Safe Mode. In Windows 8, Windows 8.1 and
Windows Server 2012, the controller driver has changed from msahci to storahci, and the procedures to upgrade to the AHCI controller is similar to that of Windows 7. On Windows 8, 8.1 and Windows Server 2012, changing from IDE mode to AHCI mode without first updating the registry will make the boot drive inaccessible (i.e. resulting in a recurring boot loop, which begins with a Blue Screen error). In Windows 10, after changing the controller to AHCI mode, if the OS is allowed to reboot a couple of times after the start of the boot loop, which starts with an INACCESSIBLE_BOOT_DEVICE BSOD, Windows presents recovery options. Out of the Advanced options, if Startup Repair option is selected, Windows attempts to fix the issue and the PC begins to function normally. A similar problem can occur on Linux systems if the AHCI driver is compiled as a
kernel module rather than built into the
kernel image, as it may not be included in the
initrd (initial RAM disk) created when the controller is configured to run in Legacy Mode. The solution is either to build a new initrd containing the AHCI module, or to build the AHCI driver into the kernel image. == Power management ==