Have you successfully used a UFS 3.0 device with Windows? Share your experience in the comments below (or admit you used a USB adapter).
| Metric | UFS 3.0 (2-lane) | SATA SSD | NVMe Gen3 | | --- | --- | --- | --- | | Seq Read | 2100 MB/s | 550 MB/s | 3500 MB/s | | Seq Write | 1200 MB/s | 520 MB/s | 3000 MB/s | | Random Read (4K) | 60k IOPS | 40k IOPS | 300k+ IOPS | | Power Active | ~2-3W | ~5W | ~6-8W | ufs 3 driver for windows 10
Starting with , Microsoft introduced an in-box UFS driver: ufs.sys . Have you successfully used a UFS 3
If you are developing an embedded Windows 10 IoT device with a UFS 3.0 chip, consult your SoC vendor (Qualcomm, Samsung Exynos, MediaTek) for their specific UFS HCI drivers — Microsoft’s generic ufs.sys may not support all vendor extensions. If you are developing an embedded Windows 10
(e.g., Easy JTAG UFI Box, Medusa Pro II, or a generic UFS-to-USB bridge board). These devices connect via USB and present the UFS chip as a removable disk using their own proprietary drivers. This is for data recovery and flashing , not for running an OS. Performance Considerations (If It Worked) Hypothetically, if you had a custom mainboard with a UFS 3.0 interface and a Windows 10 driver, performance would be excellent: