According to Neowin, Microsoft confirmed that the Media Creation Tool app failed to work on devices with Arm64 processors following the late September release of Windows 11 version 25H2. Users attempting to launch the utility encountered error messages stating “We’re not sure what happened, but we’re unable to run this tool on your PC.” The company addressed the issue in optional update KB5067036, which specifically fixed Media Creation Tool version 26100.6584 released on September 29, 2025. Beyond the critical fix, the update also introduced the redesigned Start menu, updated battery indicators, and various Copilot+ PC enhancements. This development highlights the ongoing challenges in Microsoft’s Windows 11 ecosystem as it expands to new hardware architectures.
Table of Contents
The Windows on Arm Compatibility Hurdle
This incident represents more than just a simple bug fix—it reveals the underlying complexity of Microsoft’s transition to supporting Arm64 architecture across its entire software ecosystem. While Microsoft has been working on Windows for Arm devices for years, the company still faces significant challenges ensuring that all its core utilities and application software work seamlessly across both x86 and Arm architectures. The Media Creation Tool is particularly critical because it’s often the first utility users turn to when they need to reinstall Windows or create installation media for other devices. When such fundamental tools fail on specific hardware configurations, it undermines user confidence in the platform’s maturity.
Broader Ecosystem Implications
The timing of this bug is particularly noteworthy given Microsoft’s aggressive push into the Arm space with its Copilot+ PC initiative. As Microsoft positions Arm-based devices as premium, AI-enhanced computing platforms, compatibility issues with core system utilities create friction that could slow adoption. Enterprise IT departments, in particular, rely on consistent tool behavior across all supported hardware configurations. When Microsoft’s own tools exhibit architecture-specific failures, it raises questions about third-party software compatibility and long-term support stability. This incident serves as a reminder that software ecosystem transitions require meticulous attention to detail across all components, not just the operating system core.
Optional Update Strategy Creates User Experience Gaps
Microsoft’s decision to deliver this fix as part of an optional update rather than an urgent security patch reveals important aspects of the company’s update strategy. While optional updates allow users to test new features before broader deployment, they also mean that critical functionality fixes may not reach all affected users promptly. Many personal computer users only install security updates automatically, potentially leaving them with broken Media Creation Tool functionality until the next Patch Tuesday. This approach creates a fragmented user experience where some customers enjoy full functionality while others unknowingly live with broken tools, potentially discovering the issues only when they urgently need the affected applications.
Looking Ahead: The Arm Compatibility Landscape
As Microsoft continues its Arm expansion, we can expect more compatibility challenges to emerge across the software ecosystem. The company will need to implement more robust testing protocols specifically targeting Arm64 scenarios, particularly for system utilities that users expect to “just work.” The growing popularity of Arm-based devices, driven by improved battery life and AI capabilities, means that compatibility issues will affect an increasingly large user base. Microsoft’s ability to quickly identify and resolve these architecture-specific problems will be crucial for maintaining user trust and ensuring the success of its broader Windows on Arm strategy. The relatively swift resolution of this Media Creation Tool issue suggests Microsoft is developing the necessary responsiveness, but the incident itself indicates there’s still work to be done in preventing such problems before they reach users.
