Status: Released to the Experimental channel
Affected: Windows 11 on Arm64 devices, including Copilot+ PCs
Build: 29667.1000
When Windows 11 Future Platforms build 29667.1000 reached Insiders, the headline change was a fix for Arm64 update failures. Here is what changed, who it affects, and what you should know if you’re testing next-generation Windows hardware.
What build 29667.1000 fixes
The primary change in this Experimental Preview build is a resolution to Arm64 update failures. On Arm-based Windows 11 devices, Insiders were running into problems when the system tried to install preview updates, and Microsoft has now addressed that in build 29667.1000.
Windows on Arm has historically been more prone to update hiccups than its x64 counterparts. The architecture runs software differently, and the update pipeline has to juggle additional compatibility layers, which can leave installs half-finished or stuck mid-download. This build targets one of those failure points so that preview updates can complete cleanly.
Because this is a preview build aimed at cutting-edge hardware, the fix is scoped to the experimental environment rather than a broad production rollout. That means the change is most relevant to Insiders actively testing Arm64 devices on the bleeding-edge channel.
Why Arm64 updates matter for Windows 11
Microsoft has staked a large part of its hardware strategy on Arm. Copilot+ PCs, built around Snapdragon processors, are among the most prominent examples, offering always-connected functionality and extended battery life. For those devices to succeed, the core experience—including installing updates—has to work reliably.
Update failures are especially frustrating on Arm devices because they can leave a machine in a partial state, forcing repeated reboots or manual intervention to recover. By resolving these failures, Microsoft is smoothing one of the rougher edges that has long dogged Windows on Arm and keeping experimental builds usable for daily testing.
The Future Platforms channel exists specifically to prepare Windows for new hardware architectures before they hit the mainstream market, so fixing Arm64 updates here is a natural part of that preparation work.
What this means for you
If you’re not testing Arm64 hardware on the Experimental channel, this fix won’t directly affect your day-to-day Windows 11 experience. But if you own or work with a Copilot+ PC or another Arm-based machine, build 29667.1000 should make preview updates install more smoothly.
For most Windows 11 users on conventional x64 hardware, the change is background work that improves the reliability of a niche platform rather than something you’ll notice immediately. Still, it’s a useful sign that Microsoft keeps refining Windows on Arm as more devices ship.
How to get build 29667.1000
This build is available to Insiders enrolled in the Experimental channel, which is Microsoft’s most advanced testing track. To opt in, open Settings, go to Windows Update, and select the Insider program to switch your flight ring to Experimental.
Once you’re on the Experimental channel, check Windows Update for the latest preview. Because Experimental builds are the least stable and most likely to contain bugs, Microsoft recommends installing them on a secondary or dedicated machine rather than your primary daily driver.
About the Windows 11 Future Platforms channel
The Windows 11 Future Platforms channel is where Microsoft shares builds that target upcoming hardware architectures and form factors, ahead of their general availability. It runs alongside the more mainstream Dev and Beta channels, which focus on the current generation of Windows 11.
The Experimental channel sits at the very frontier of that effort, delivering builds like 29667.1000 to Insiders who want to test software for hardware that isn’t yet widely available. That makes it an ideal place to catch—and report—early issues like Arm64 update failures before they reach a broader audience.
Based on the changelog details, this release is a focused fix rather than a feature dump, which is typical for the experimental track where stability and early hardware compatibility take priority over new capabilities.
Source: Neowin
Over to you: Are you running Windows 11 on Arm64 hardware, and did you hit these update failures yourself?
