ReactOS Merges Initial USB 3.0 Driver Stack, Laying Groundwork for USB4

What actually landed​

The code arrived through ReactOS pull request #9646. The title lists USBDEX, USBD, SDK, USBHUB3, USBXHCI and UCX01000, and says it implements USB3 support and prepares for USB4. That list suggests a layered design, not a single driver. xHCI is the host controller interface used by modern USB 3 controllers. UCX is the USB Class Extension model, which an earlier pull request in the series describes as how Windows handles modern USB.

The author is the developer known as DarkFire01. In the pull request, he said the work has a long history, with many iterations over a few years. He submitted it as "one giga sized PR" because the project was holding a hackfest.

That matches the project's own account. The second 2026 hackfest was in Orlando, Florida, from October 9th to October 19th. The project said a new USB3/USB4 stack, which lets ReactOS install on machines with modern USB chipsets, was merged in basic form with more to come. The ReactOS blog post also shows an xHCI host controller detected in Device Manager. That is a screenshot caption, not a compatibility list.

Groundwork came first​

The big merge was preceded by smaller steps.

• An early pull request added the headers needed to build a UCX stack following the latest ABI.
• Another pull request, which started a new USB3 architecture, was merged on October 9, 2026. Its author said the shared state code is meant to keep some ability to replace USBHUB3 in ReactOS with the one from any modern Windows version eventually.

That is a notable design choice. Following the Windows driver model closely is how ReactOS hopes to stay compatible with real Windows drivers.

How to read the "quite stable" claim​

The stability claim needs care. The developer wrote that he had been daily driving this USB stack from Windows 11 for awhile, and had given versions of the binaries to a few people. He called it "quite stable."

That describes his own use. He also described a debugging method: the three drivers log every state transition, which made it easy to see where drivers fail on Windows. It is a sound way to develop a driver. It is still one developer's account, not a published test matrix. The sources I reviewed give no list of supported controllers, no tested device classes, and no benchmarks.

My reading is that the claim is encouraging. Running the stack on a modern Windows 11 machine exercises real xHCI hardware. But ReactOS is a different kernel environment, so results there can differ. I mean that as general engineering context, not as a finding from the sources.

Hardware quirks and ARM​

The developer also said that many hardware quirks and workarounds are included, and will be fully enabled when ReactOS supports KSE. He added that the driver is ARM32 and ARM64 ready. Those are the developer's statements about intent and design. They are not verified features that readers can use today.

USB4 is a follow-on​

Phoronix quotes the developer saying a second pull request follows this one. It involves the USB4 Host router and USB4 Device router, which depend on this work and on DeviceProperty support being merged. Treat USB4 as planned work. The first merge does not deliver it.

Other USB changes in the tree​

This is not the first USB news for ReactOS. Phoronix earlier covered a batch of USB driver bug fixes aimed at Blue Screen of Death issues on real hardware. A separate October 2026 pull request proposed adding USB 3.0-compatible hub IOCTLs to the legacy stack. A reviewer pushed back, saying the legacy stack shouldn't get 3.0 additions when a dedicated USBHUB3 is on the way. Together these show that ReactOS now has a legacy USB stack and a new one under development.

Why this matters for PC users​

Many ReactOS testers use virtual machines. Real hardware is a different story. Many modern PCs expose their keyboard, mouse and storage through xHCI controllers. If the operating system has no xHCI driver, installing it on that hardware can be difficult. That is the gap this work targets. ReactOS describes its goal as a free Windows-compatible operating system. Its repository says it is currently focused on Windows Server 2003 compatibility. It also says it is an alpha-quality OS that can corrupt data on a hard disk, so the project recommends testing on a VM or a machine with no sensitive data.

Trying it safely​

This section is practical guidance based on the project's own build page. It is not a tested procedure.

1. Do not assume that the stable ReactOS 0.4.16 release includes this code. The project lists 0.4.16 as released on August 29, 2026, and the USB merge came in October and November.
2. Use a nightly or automatically built revision from the project's builds page. The project warns that these builds are not as thoroughly tested as release builds and may contain regressions and bugs.
3. Choose a Debug build if you plan to report bugs. The project says Debug builds include debugging information and are the recommended variant for producing logs.
4. Use a Boot CD to install, or a Live CD to try ReactOS without installing it. The Live CD is also suggested if your disk isn't detected during setup.
5. Use spare hardware or a VM, and don't put it on a machine with data you care about.
6. If you find a bug, search the project's JIRA first. If it isn't already reported, file it with logs and as much detail as possible.

Bottom line​

A basic USB 3 stack has been merged, with a design that tracks the Windows model and a clear path toward USB4. The evidence is a developer's claim of stability on Windows 11 and a Device Manager screenshot. What's missing is a public compatibility list or ReactOS-specific test results. For now, this is a promising foundation, and ReactOS nightlies will show how it holds up on real hardware.