ReactOS Adds First NT6 System Call, a Critical Step Toward Vista Compatibility

ReactOS has implemented its first NT6- era system call, NtGetCurrentProcessorNumberEx, marking a critical milestone toward Windows Vista compatibility despite the function currently performing no operations.

ReactOS Adds First NT6 System Call, a Critical Step Toward Vista Compatibility

ReactOS has added its first NT6-era system call, a technical milestone that brings the open-source alternative closer to compatibility with Windows Vista and newer software. This update marks a critical step in the project's long development cycle, even though the new function currently performs no active operations. Developers and users tracking the progress of free Windows clones can now see concrete kernel-level progress toward broader software support.

The open-source Windows alternative implements an inert kernel function to advance Vista-era support

The new system call is named NtGetCurrentProcessorNumberEx and returns the processor number of the logical processor the caller is running on. ReactOS implemented this function within the kernel alongside various other NT6 processor functions. This addition shifts the operating system from earlier NT versions toward the architecture used by Windows Vista and later releases.

The ReactOS team announced the implementation on X, describing the update as a remarkable moment in the transition to Vista-plus compatibility. They noted that while the call does nothing for now, it is a necessary foundation for future functionality. Microsoft took around half a decade to develop Windows Vista, so the timeline for full software compatibility remains unclear.

ReactOS remains in the alpha software stage, meaning it is not yet ready for daily use or production environments. The project continues to build its core compatibility layer incrementally, with each new system call adding to the potential for running modern Windows applications. This latest update is a small but significant piece of that ongoing engineering effort.

Discussion

0 comments

Log in to join the thread with a thoughtful take, question, or correction.

Add to the discussion