On October 24, 2026, the German IT site Deskmodder reported that Xeno had found a settings switch related to Intel's instruction set extension Advanced Performance Extensions (APX) in Windows 11 experimental build 29695.1001. APX increases the number of general-purpose registers in the CPU, reducing data movement and redundant instructions during computation. Microsoft has also added APX support to the Windows SDK and to its debugger, WinDbg, so preparations for handling the new instructions on Windows are moving forward. However, the discovery of a setting does not mean existing PCs will see a performance boost right away. To use APX, not only the CPU and OS but also the software being run must support it.
APX doubles the registers and cuts redundant instructions
According to Intel's technical overview, APX doubles the CPU's general-purpose registers from 16 to 32. Registers are fast storage areas inside the CPU that temporarily hold values such as intermediate calculation results. When registers run short, a program has to write values out to memory and read them back when they are needed again. With more registers, the compiler can keep more values inside the CPU, reducing this back-and-forth with memory.
APX also extends the instruction format. Some conventional x86 instructions overwrite one of their source registers with the result, so if the original value is needed later, it has to be copied to another register beforehand. With the three-operand format introduced by APX, the destination for the result can be specified separately from the two inputs, making it possible to skip the copy instruction that preserves the original value. The same calculation can thus be expressed with fewer instructions.
APX also includes conditional load, store, and compare instructions, as well as a feature that suppresses updates to status flags based on arithmetic results. This allows the optimization of replacing conditional branches with conditional instructions to be applied more widely than before, which is also intended to reduce the performance penalty from branch mispredictions. In addition, "PUSH2" and "POP2" are added to save and restore the values of two registers at once. APX is thus an instruction set extension that does more than add registers: it streamlines the work involved in copying and saving data and in conditional branching.
Intel says that, compared with code compiled for conventional Intel 64, using APX reduces load instructions by 10%, store instructions by more than 20%, and total instructions by 10%. However, these figures are projections based on prototype simulation using "SPEC CPU 2017 Integer," not measurements of Windows application run time or power consumption. A 10% drop in instruction count does not necessarily mean a 10% increase in speed. Actual gains also depend on instruction execution efficiency, memory access, and the nature of the workload, so testing with APX-enabled software is needed.
Windows is also preparing for APX
When general-purpose registers increase, the OS must also manage the state of the added registers properly. Windows runs multiple programs concurrently and switches between threads frequently. In this "context switch," the register state of the interrupted thread must be saved and then restored when it resumes. According to Intel, the registers added by APX are supported by the existing XSAVE and XRSTOR state save and restore mechanisms. The design reuses the area for registers of the discontinued Intel Memory Protection Extensions (MPX), so the size and layout of the XSAVE area do not need to change.
Microsoft has also added APX-related features to Windows development tools. According to the Windows SDK release notes, Windows SDK 10.0.28000.2957, released in September 2026, adds the feature flag PF_APX_F_INSTRUCTIONS_AVAILABLE, which indicates whether the processor supports APX instructions. XSTATE_APX_F and XSTATE_MASK_APX_F, for handling the APX extended state, have also been newly defined. The development environment for Windows software now has definitions for identifying APX support and handling the added processor state.
Support is also advancing in the WinDbg debugger. According to Microsoft's release notes, version 1.2606.22001.0 introduced basic functionality for displaying APX's additional registers. In the following version, 1.2610.1001.0, support progressed for unwind information and debug information for the extended general-purpose registers, making it possible to trace the stack correctly even across APX exception frames. A problem in which APX register state was lost when saving crash dumps and similar data has also been fixed. Beyond preparing to execute the new instructions, an environment for investigating the cause when problems occur in programs that use APX is taking shape.
To understand APX support accurately, it is necessary to distinguish between CPU instruction specifications, compilers, the OS, and development tools. Even if each is making progress, ordinary users cannot necessarily use APX right away. The main developments that can currently be confirmed are summarized below.
| 対象・資料 | 確認できる対応状況 | これだけでは分からないこと |
|---|---|---|
| Intel APX | 汎用レジスタの倍増、命令セットの拡張、追加状態の保存・復元の仕組み | 市販CPU全体の対応状況 |
| GCC 15 | CFCMOVを除くAPXの新機能に対応。-mapxfオプションを追加 |
個々のWindowsアプリがAPX命令を使用しているか |
| Windows SDK（2026年9月） | APXの機能フラグと拡張状態の定義を追加 | すべてのWindows PCでAPXを利用できるか |
| WinDbg（1.2610.1001.0まで） | 追加レジスタの表示・デバッグ、例外フレームをまたぐスタック追跡に対応 | Windowsアプリでの性能向上率 |
| Windows 11実験ビルド29695.1001 | 実験ビルドを公開。特定のWindowsリリースに結び付けない開発方針を明示 | APXを正式提供するWindowsのバージョンと時期 |
What the Windows SDK and WinDbg updates show is that the environment for developing and testing APX-enabled software is being put in place. These materials, however, do not explain how the settings switch found in the experimental build actually behaves, or whether it will be offered to general users. In the comments section of the Deskmodder article, the author, moinmoin, also states that the switch in question does not appear in his own environment. The discovery should not be taken as an announcement that APX is now officially available on Windows.
Performance gains require support from the CPU, OS, and software
Intel expects that using APX will not require changes to an application's source code and that recompiling will be enough. What matters is whether the compiler can generate machine code that uses APX's new instructions. For example, GCC 15 lets you specify APX support with the -mapxf option, but CFCMOV, the conditional flag-setting move instruction, is not among the supported features. Even when a compiler supports APX, not every extension is necessarily available.
For dynamic languages as well, Intel says performance benefits are possible once the underlying runtime supports APX. However, simply flipping a Windows setting will not automatically replace the instructions in existing apps with APX versions. It takes a CPU that implements APX instructions, an OS that can manage the state of the added registers properly, and applications or runtimes that use APX instructions. Only when these conditions are met can the actual effects on performance and power consumption be evaluated.
The official release timing is also unclear at this stage. On October 23, 2026, Microsoft released Windows 11 build 29695.1001 to the "Experimental (Future Platforms)" channel. The company states explicitly that builds in this channel contain early-stage platform changes and do not correspond to any particular Windows release. Features under testing may change or be removed, and may never be generally released. It therefore cannot be concluded from the discovery of this settings switch alone that APX will become available in the next Windows update.
What matters about these developments is that, beyond the APX instruction specification itself, the mechanisms Windows needs for state management and debugging are beginning to be put in place. For developers, the significance lies in an environment that lets them verify not only code generation for APX but also behavior during thread switches and exceptions. For general users, the key question is whether this preparation translates into real performance gains in applications. The focus going forward will be on which CPU and Windows combinations are confirmed to support APX, and whether processing time and power consumption can be compared using real software that uses it.