Before the error hits, the drive is unremarkable in the best way possible. Whether it’s an HP-branded Samsung PM1733 or an Intel drive, the NVMe throughput is exactly what you expect from an enterprise-grade PCIe device. Boot times are fast, IOPS are high, and virtualization tasks run smoothly. It does the job without fuss.
The error "No drives were found" typically occurs during the Windows installation phase where you select a destination drive. There are three primary causes for this issue on HP machines: hp nvme ssd -313- error
If a user starts an HP BIOS "Secure Erase" (or "Sanitize") on an NVMe drive and the process is interrupted by a shutdown or battery depletion, the drive is left in a non-initialized state. The HP BIOS sees this as error -313 because the drive cannot finish its internal formatting. Before the error hits, the drive is unremarkable
Some HP ZBooks have a power management conflict. If a user starts an HP BIOS "Secure
The "-313" error is the star of this show, and not in a good way. Unlike standard drive failures—which usually manifest as bad sectors, slow read/write speeds, or a complete lack of detection—the -313 error is unique.
Dealing with HP Support regarding the -313 error can be a mixed bag.