Microsoft has quietly resolved a persistent compatibility issue that prevented the Media Creation Tool from running on Arm64 devices, bundling the fix within the October/November 2025 preview update KB5067036. This update not only addresses the critical installation utility problem but also introduces a suite of visible Windows 11 feature enhancements, including a redesigned Start menu, improved battery indicators, and expanded Copilot capabilities, all delivered through Microsoft's gradual rollout mechanism that has both users and administrators navigating a complex deployment landscape.

The Media Creation Tool Regression and Its Impact

The Media Creation Tool (MCT) serves as Microsoft's official utility for downloading Windows 11 installation images and creating bootable USB drives, making it an essential tool for system upgrades, recovery scenarios, and IT deployments. In late September 2025, Microsoft released version 26100.6584 of the MCT, which immediately began causing problems for users on Arm64 devices and some Windows 10 22H2 systems. Affected users reported that the tool would briefly display a Windows splash screen before exiting silently, displaying the error message: "We're not sure what happened, but we're unable to run this tool on your PC."

This timing proved particularly problematic as it coincided with the Windows 10 end-of-support window, when many users and organizations were preparing migration strategies. According to community reports on WindowsForum.com, the regression created significant friction for home users, refurbishers, OEM technicians, and imaging teams who relied on on-device creation workflows. The inability to run the official tool forced users to fall back to manual ISO downloads or third-party utilities, increasing complexity and potential security risks.

Microsoft acknowledged the issue in their Windows 11 update history and release health documentation, providing short-term workarounds while promising a fix in an upcoming update. The company's documentation clarified that the Media Creation Tool historically didn't support creating Arm64 media from Arm64 hosts, making this a particularly narrow but critical workflow that affected specific user segments.

KB5067036: The Comprehensive Fix and Feature Bundle

Microsoft's solution arrived in the form of KB5067036, an optional, non-security preview update released in October/November 2025. This cumulative update explicitly addresses the Media Creation Tool failure on Arm64 hosts and related compatibility problems. According to Microsoft's release notes, the fix corrects the issue where MCT version 26100.6584 would fail to run on affected systems.

Beyond the critical MCT fix, KB5067036 serves as a feature preview containing numerous user-facing improvements that are being rolled out gradually through Microsoft's feature flighting system. This dual-purpose approach—combining bug fixes with feature enhancements—represents Microsoft's modern servicing model, where reliability improvements and new capabilities arrive together in preview channels before broader distribution.

Key Feature Enhancements in KB5067036

Redesigned Start Menu: The update introduces a vertically scrollable Start menu surface with a new "All" section and multiple view modes (Category, Grid, List). Microsoft has improved discoverability and integrated Phone Link functionality for accessing mobile content directly from the Start menu.

Enhanced Battery Indicators: Users now benefit from color-coded battery states on both the taskbar and lock screen, with an optional percentage toggle available in Settings > Power & battery. This visual enhancement provides clearer at-a-glance power status information.

Copilot and AI Improvements: KB5067036 expands Copilot capabilities with a typed prompt box, on-screen text translation, unit conversions, and table detection with "Convert to table with Excel" functionality on Copilot+ devices. Additional Copilot vision tasks become accessible directly from the taskbar UI, though some features remain hardware- and license-gated to Copilot+ PCs.

Voice Access - Fluid Dictation: This feature leverages on-device small language models (SLMs) to correct grammar and punctuation while removing filler words in real-time. Enabled by default on Copilot+ PCs in supported locales, this represents Microsoft's continued investment in on-device AI processing.

File Explorer Home Enhancements: The update brings recommended files for personal/local accounts, hover commands like "Open file location" and "Ask Copilot," and StorageProvider APIs for cloud suggestions, creating a more intelligent and context-aware file management experience.

Community Perspectives and Real-World Impact

WindowsForum.com discussions reveal mixed reactions to Microsoft's approach. While users appreciate the Media Creation Tool fix, many express frustration with the gradual rollout mechanism for new features. Community members report installing KB5067036 but not immediately seeing the redesigned Start menu or other advertised enhancements, leading to confusion about whether the update installed correctly.

One user commented: "I installed the update expecting the new Start menu, but nothing changed. It took three days before the feature suddenly appeared. Microsoft needs to be clearer about how these staged rollouts work."

Another community member highlighted the timing issue: "The MCT breaking right when everyone needs to create Windows 11 installation media for Windows 10 migrations shows how fragile these critical tools can be. Microsoft's fix came relatively quickly, but the disruption was real for those trying to upgrade multiple systems."

IT administrators participating in the discussion emphasized the importance of maintaining alternative media creation methods. One enterprise administrator noted: "We always keep validated ISO images and use Rufus for USB creation. The MCT issue reinforced why we can't rely on a single tool, especially during critical migration periods."

Installation and Deployment Considerations

KB5067036 was released as an optional preview update, meaning users must actively choose to install it through Settings > Windows Update. The standard installation process involves:

  1. Opening Settings > Windows Update
  2. Clicking "Check for updates"
  3. If KB5067036 appears under "Optional updates available," clicking "Download and install"
  4. Rebooting when prompted

Administrators can download the standalone MSU package from the Microsoft Update Catalog for manual deployment on managed systems. For those using Release Preview or other Insider channels, the update may already be visible through normal update channels.

It's crucial to understand that installing KB5067036 doesn't guarantee immediate activation of all new features. Microsoft employs server-side feature flags that enable capabilities gradually over time, creating what the community describes as a "phased activation" experience. This approach allows Microsoft to control rollout pace and monitor for issues, but it can confuse users who expect immediate changes after installing an update.

Practical Alternatives and Workarounds

While the MCT fix in KB5067036 should resolve the Arm64 compatibility problem, users and administrators may need alternatives during the update rollout period or if policies prevent installing preview patches. Several safe, official alternatives exist:

Official Windows 11 ISO Download: Users can visit Microsoft's official "Download Windows 11 Disk Image (ISO) for x64 devices" page to obtain the installation image directly. The ISO can be mounted using File Explorer for in-place upgrades or written to USB using trusted tools like Rufus.

Windows 11 Installation Assistant: This utility performs in-place upgrades on eligible devices without requiring the Media Creation Tool, providing an alternative path for system updates.

Cross-Architecture Media Creation: For users needing Arm64 installation media, Microsoft recommends using an x64 (Intel/AMD) host to build the Arm64 USB or working with downloaded Arm64 ISOs on compatible workstations. This workaround addresses the historical limitation where the Media Creation Tool didn't support creating Arm64 media from Arm64 hosts.

Community discussions emphasize the importance of avoiding untrusted ISOs from third-party sources, recommending instead Microsoft's official images or reputable utilities like Rufus and Ventoy with verified ISOs.

Analysis: Microsoft's Evolving Update Delivery Model

KB5067036 exemplifies Microsoft's modern approach to Windows servicing, combining several strategic elements that have both strengths and challenges.

Strengths of the Current Model: Microsoft's staged preview approach allows the company to bundle multiple feature improvements and reliability fixes in a single package, validating them with Release Preview insiders before broad distribution. This reduces the risk of global disruption from individual changes. The company's rapid response to the MCT regression—documenting it in release health pages and delivering a fix in a timely manner—demonstrates effective triage for critical utility failures.

Identified Challenges: Community feedback highlights several recurring issues with Microsoft's delivery approach. The timing of the MCT regression during a high-pressure migration window exposed how single-point failures in critical tools can create disproportionate impact. Gradual feature rollouts increase user confusion when updates install but features don't immediately appear, leading to support inquiries and potentially unsafe workarounds by power users attempting to force feature activation.

WindowsForum.com discussions also reveal concerns about narrow, architecture-specific workflows remaining fragile. While Arm64 and mixed-architecture imaging workflows aren't mainstream, they're critical for OEMs, developers, and specialized IT shops. The MCT problem underscores that niche workflows can still be production-critical, suggesting testing matrices need broader coverage.

Recommendations for Different User Segments

Home Users and Enthusiasts: If experiencing MCT errors and unwilling to install preview updates, download the official ISO and use Rufus or File Explorer mounting for upgrades. Always verify ISO checksums when available and maintain system backups before performing clean installs. Those comfortable with preview updates can install KB5067036 to access new features but should expect phased activation.

Power Users and Device Builders: Maintain a validated x64 staging host for media creation as a contingency against Arm64 tool failures. When building images for distribution, prefer controlled internal ISO repositories and established deployment pipelines rather than ad-hoc MCT runs from diverse hosts.

IT Administrators: Pilot KB5067036 in controlled test environments first, validating imaging and playback workflows, particularly for systems using HTPCs, capture devices, or EVR-based players. Maintain canonical ISO collections with verified hashes and prepare fallback media creation processes that don't rely solely on on-device MCT runs.

Future Outlook and Considerations

Several aspects remain uncertain following the KB5067036 release. Microsoft hasn't published public telemetry on how many users were affected by the MCT regression, leaving exact scope estimates to community reports. Feature activation timing for the Start menu redesign, Click to Do improvements, and certain Copilot experiences depends on server-side controls and regional gating, creating staggered availability that users must navigate.

The community will be watching for the formal Patch Tuesday packaging of these fixes and features. Microsoft has indicated that KB5067036's improvements will be folded into the broader cumulative update cadence once validated, which is when the MCT fix will reach mainstream update pipelines for most users.

Conclusion: Balancing Innovation and Reliability

KB5067036 successfully resolves a narrow but disruptive problem with the Media Creation Tool while introducing significant Windows 11 enhancements. Microsoft's response—bundling the critical fix with forward-looking feature improvements—reflects the company's evolving servicing philosophy that seeks to balance innovation with reliability.

For users and administrators, the pragmatic approach involves maintaining validated media creation alternatives, understanding Microsoft's gradual rollout mechanisms, and adopting conservative update policies for production environments. The incident serves as a reminder that even official tools can experience regressions, emphasizing the importance of contingency planning during critical migration periods.

As Microsoft continues refining its update delivery model, clearer communication about feature activation timelines and more comprehensive testing of niche workflows could help reduce user confusion and improve the overall update experience. The community's feedback through platforms like WindowsForum.com provides valuable insights into real-world impacts, helping shape more resilient update processes for all Windows users.