Build 29695 reached Windows Insiders in the Experimental (Future Platforms) channel on 23 October 2026. BetaWiki describes it as the ninth Insider Preview build of Windows vNext on the Rubidium codebase. Microsoft's flight hub says builds in this channel are experimental and not aligned to a retail Windows release. That is the key caveat for the headline claim that a boost is "coming soon."
What was spotted
Windows enthusiast Xeno reported a new switch in the build. Neowin says the English description is "Let Windows use APX for better performance," and that turning it on prompts a restart. Deskmodder, a German site, independently reports the same switch under Settings > System > Advanced. Its German label is "Erweiterung für verbesserte Leistung (APX)," and it calls the switch a developer feature.
Some points are not confirmed:
- Microsoft's official release notes for 29695.1001 don't mention APX. They describe a "small set of general improvements and fixes."
- The headline items in those notes are a Magnifier contrast theme and fixes for networking, Hyper-V and VMware crashes. The fixes cover internet connectivity, Linux VM folder sharing via Hyper-V and Plan9, excessive ESENT events, and VMware green screen crashes.
- The English wording and the restart prompt come from Neowin's account. I could not verify them against Microsoft documentation.
- Deskmodder's report suggests the switch may not appear for every tester, which would fit a gradual rollout. That is an observation, not a Microsoft statement.
- Neowin speculates this may be for Windows 11 27H2. I found no Microsoft commitment to a release vehicle or date.
What APX is
Intel describes APX as an expansion of the x86 instruction set, which Intel says gives access to more registers and adds features that improve general-purpose performance. The main changes are:
- More registers. APX doubles the general-purpose registers from 16 to 32, so compilers can keep more values in registers rather than in memory.
- Three-operand forms (NDD). Many integer instructions get a separate destination register, which cuts down on extra register-move instructions.
- Conditional load, store and compare instructions. These let compilers replace more branches, which reduces branch misprediction penalties.
- No Flags (NF) forms. Common instructions can skip writing status flags.
- PUSH2/POP2. These save and restore register pairs in a single memory operation.
- A 64-bit absolute direct-jump instruction.
Intel's own figures come from a prototype simulation of the SPEC CPU 2017 Integer suite. Code compiled with APX had 10% fewer loads and more than 20% fewer stores than the same code compiled for an Intel 64 baseline. Intel also says performance varies by use, configuration and other factors. These are projections for recompiled code. They are not Windows benchmarks, and flipping a toggle won't deliver them.
Why the OS has to be involved
The new registers hold per-thread state, so the OS must save and restore them on context switches. Intel's article says the new registers are XSAVE-enabled, so XSAVE/XRSTOR sequences can save and restore them automatically during context switches. That is a plausible reason Windows would expose an explicit opt-in during testing, though Microsoft hasn't said so. Intel also says it proposes defining the new registers as caller-saved (volatile) in ABIs, to help interoperability with legacy binaries.
Hardware support is the other requirement. Intel's GCC 15 article names the next-generation Xeon Scalable processor, code-named Diamond Rapids, as the target for its APX compiler work. It does not say which consumer CPUs will support APX. Deskmodder's note mentions Intel and AMD CPUs, but I found no retail CPU list. If your processor lacks APX, the setting should have nothing to enable. That last part is my inference.
What developers can do now
Intel says developers can use APX by simple recompilation, and source code changes aren't expected to be needed. It adds that dynamic-language workloads should benefit once the underlying runtime is enabled.
On the compiler side, Intel's June 2025 article says GCC 15 enables the full set of APX features for the next-generation Xeon Scalable processor. The basic option is -mapxf, and -march=diamondrapids also enables it. GCC's own release notes, as summarized in the research brief, add one qualification. GCC 15 supports all the new APX features except CFCMOV, so "complete" needs a footnote.
The Neowin piece says Intel published APX spec version 9 in August 2026. The primary specification I could retrieve was Revision 7.0, from July 2025. I can't confirm the later revision, so I'm not repeating it as fact.
What this means for you
- Everyday users: Nothing changes. This is an Experimental-channel build, and nothing here is a general release.
- Developers and testers: The setting is a sign that Windows is being readied for APX-compiled code. Test any APX-targeted builds on supported hardware only. APX instructions on an unprepared system can fault.
- IT administrators: No action is needed and there is no policy to manage. Wait for Microsoft documentation, supported-CPU lists and a retail release path.
Bottom line
The evidence supports a narrow conclusion. An experimental Windows 11 build appears to contain a developer-facing APX setting. It would pay off only with APX-capable CPUs and software compiled for them. Intel's 10% and 20% figures describe compiled code in simulation. They don't describe a measured Windows speedup. Until Microsoft documents the feature and says which CPUs support it, treat "Windows 11 performance boost coming soon" as optimistic framing.
Update: Nova Lake reportedly emerges as the first consumer APX candidate (October 26, 2026)
Tbreak, citing Windows Latest, reports that Intel’s upcoming Nova Lake consumer processors are expected to support APX. If accurate, that gives the experimental Windows toggle a clearer hardware target than was previously available.
The report also says current Intel platforms—including Alder Lake, Raptor Lake, Meteor Lake, Lunar Lake, Arrow Lake and Panther Lake—do not include the required APX CPU capability. That means the setting will not unlock a performance feature on existing PCs through a Windows update alone.
Intel’s compiler documentation still provides the firmer confirmation only for Diamond Rapids Xeon processors. Nova Lake support remains reported rather than formally announced by Intel or Microsoft, so IT buyers should not treat it as a finalized platform requirement yet.