Today Microsoft published Windows 11 Build 26100.5061 (KB5064081) to Insiders on the Release Preview Channel for Windows 11, version 24H2, delivering a broad mix of AI-driven features, quality fixes, and platform changes that will begin rolling out to wider audiences in the coming weeks. The update surfaces notable consumer-facing additions — like AI actions inside File Explorer, a redesigned privacy prompt, and Recall improvements — alongside enterprise-focused work such as Windows Backup for Organizations and the planned removal of Windows PowerShell 2.0 from the OS image. The Release Preview announcement is the authoritative changelog for this build and was published by the Windows Insider Program Team on August 14, 2025. (blogs.windows.com)
Microsoft’s Windows Insider Release Preview Channel serves as the final staging ground for quality updates and incremental feature rollouts before they move into broad production delivery. Build 26100 is the code line for Windows 11 version 24H2; monthly cumulative updates and preview builds for this version are being shipped as checkpoints and incremental cumulative updates under the updated servicing model for 24H2. Microsoft’s update delivery model for 24H2 uses checkpoint cumulative updates to optimize bandwidth and installation sequencing, which is important context for IT pros planning deployments. (learn.microsoft.com)
The official Release Preview announcement for Build 26100.5061 (KB5064081) lists two categories of changes: Gradual rollout items — features that are being A/B tested or phased regionally/hardware-restricted — and Normal rollout items — fixes and improvements applying to all devices that successfully install the update. The blog post provides the full breakdown of both types and enumerates specific fixes for components ranging from Task Manager to ReFS. (blogs.windows.com)
Separately, Microsoft’s documentation on 24H2 update delivery and checkpoint cumulative updates explains why some organizations see multiple MSU files for a given cumulative update and why update sequencing may matter when applying offline packages via the Microsoft Update Catalog. This is an operational detail that matters for image builders and administrators who prefer manual deployment (DISM / WUSA workflows). (learn.microsoft.com)
A set of previously uploaded forum/archive materials in our internal files also shows how Microsoft integrated more recent inbox app updates directly into 24H2 media and has been rolling out Copilot-related experiences and bugfixes across multiple 26100-series builds throughout 2024–2025. That archival context helps explain why today's Release Preview update is largely an incremental refinement and rollout expansion rather than a wholesale feature rework.
The update’s dual character — consumer-facing AI enhancements plus administrative changes — makes it essential for both end users and IT administrators to review the build notes, test in controlled rings, and follow Microsoft’s guidance on update delivery and deprecation timelines. For administrators, the immediate priorities are an inventory of PowerShell dependencies, pilot testing for device classes in your environment, and confirming offline deployment steps against Microsoft’s checkpoint guidance. (blogs.windows.com, support.microsoft.com, learn.microsoft.com)
By integrating generative AI into core OS surfaces while continuing to modernize the Windows platform, Microsoft is pushing Windows 11 24H2 further into a hybrid productivity and AI-first direction — but the usual caveats of phased rollouts, licensing, and legacy compatibility apply. For organizations and power users, cautious testing and targeted remediation (especially for PowerShell 2.0 dependencies) will be the prudent path forward. (blogs.windows.com, windowscentral.com, support.microsoft.com)
Source: Microsoft - Windows Insiders Blog Releasing Windows 11 Build 26100.5061 to the Release Preview Channel
Background
Microsoft’s Windows Insider Release Preview Channel serves as the final staging ground for quality updates and incremental feature rollouts before they move into broad production delivery. Build 26100 is the code line for Windows 11 version 24H2; monthly cumulative updates and preview builds for this version are being shipped as checkpoints and incremental cumulative updates under the updated servicing model for 24H2. Microsoft’s update delivery model for 24H2 uses checkpoint cumulative updates to optimize bandwidth and installation sequencing, which is important context for IT pros planning deployments. (learn.microsoft.com)The official Release Preview announcement for Build 26100.5061 (KB5064081) lists two categories of changes: Gradual rollout items — features that are being A/B tested or phased regionally/hardware-restricted — and Normal rollout items — fixes and improvements applying to all devices that successfully install the update. The blog post provides the full breakdown of both types and enumerates specific fixes for components ranging from Task Manager to ReFS. (blogs.windows.com)
What’s in Build 26100.5061 (KB5064081)
This section summarizes the most consequential changes surfaced by Microsoft for Build 26100.5061, verified against the Windows Insider announcement and independent coverage of the Release Preview drop.Major new or expanded features (gradual rollouts)
- Recall: personalized homepage and timeline — Recall now opens with a personalized homepage prioritizing recent snapshots, top apps, and frequently visited websites. The new UI includes a left-hand navigation bar with Home, Timeline, Feedback, and Settings; users can set filters in Settings to control which apps and websites are included in snapshots. This rollout remains gated and may not be immediately visible to all Insiders. (blogs.windows.com)
- Click to Do: first-run interactive tutorial — Click to Do gains an onboarding tutorial that demonstrates actions on text and images (for example, summarizing long blocks of text or removing image backgrounds). This improves discoverability for Copilot-driven workflows. (blogs.windows.com)
- AI Actions in File Explorer — Right-click context menus in File Explorer now surface AI-powered image edits (Blur Background, Erase Objects, Remove Background, Visual Search) and document Summarize actions that integrate Copilot and Microsoft 365 services. The Summarize action requires an active Microsoft 365 subscription and Copilot license. The feature is a platform-level integration of generative capabilities into the file management surface. (blogs.windows.com)
- Settings agent for Copilot+ PCs — An on-device agent in Settings that understands natural language queries and can suggest or automate changes is expanding beyond Snapdragon hardware to AMD/Intel Copilot+ PCs in English locales. This is part of the Copilot+ experience and is gradually rolling out. (blogs.windows.com)
- Taskbar and Search updates — The notification center can now show a larger clock with seconds; Search on the taskbar gains a grid image view and clearer status messaging while indexing; and taskbar thumbnail fixes reduce accidental click issues. (blogs.windows.com)
Platform, privacy and management changes
- Redesigned privacy prompt for capability access — When an app requests location, camera, or microphone access, the system now dims the screen and presents a centered, modernized consent dialog to reduce ambiguity and improve clarity. (blogs.windows.com)
- Text & Image Generation controls — A new Settings page (Privacy & security > Text and Image Generation) lets users review which third‑party apps accessed generative AI models on the device and toggle permissions, reflecting Microsoft’s effort to give users control over on-device generative workflows. (blogs.windows.com)
- Windows Backup for Organizations — Now generally available: enterprise-grade backup/restore targeted at organizational device refresh and migrations to reduce downtime and preserve productivity during hardware or OS transitions. (blogs.windows.com)
- PowerShell 2.0 removal — Microsoft confirms that Windows PowerShell 2.0 will no longer be included in Windows 11, version 24H2 beginning in August 2025 (and similarly removed from Windows Server in subsequent releases). This change is part of an extended deprecation plan: PowerShell 2.0 was deprecated in 2017, and Microsoft now intends to remove the legacy engine from the OS image entirely. Administrators must audit environments for any scripts or installers that explicitly invoke the 2.0 engine and migrate to PowerShell 5.1 or PowerShell 7.x. This deprecation is documented on Microsoft support pages and the Windows deprecated features list. (support.microsoft.com, learn.microsoft.com)
Fixes and reliability improvements (normal rollout)
- ReFS memory exhaustion mitigation for backup apps handling large files.
- IME and input-related bug fixes (Chinese IME, touch keyboard behavior).
- Improvements to Windows Hello reliability, including fingerprint behavior after standby and a redesigned Hello UX for passkeys and connected device sign-in.
- Task Manager now reports CPU metrics using standard industry values; an optional "CPU Utility" column restores the legacy-style metric for users who prefer it.
- Repair for an audio service hang and dbgcore.dll-related explorer crashes that could previously cause application instability.
- Fix for an issue that blocked some system recovery features due to temporary file-sharing conflicts.
Independent corroboration and context
Coverage by independent Windows-focused outlets tracked these same changes in the Release Preview drop and highlighted the release’s emphasis on AI workflows, the continued phasing of Copilot features, and the enterprise-focused additions such as Quick Machine Recovery and changes to update packaging. Windows Central’s reporting on the release matches the blog’s characterization of phased rollouts, taskbar and search improvements, and the set of enterprise features and reliability fixes included in the recent 24H2 servicing cycle. (windowscentral.com)Separately, Microsoft’s documentation on 24H2 update delivery and checkpoint cumulative updates explains why some organizations see multiple MSU files for a given cumulative update and why update sequencing may matter when applying offline packages via the Microsoft Update Catalog. This is an operational detail that matters for image builders and administrators who prefer manual deployment (DISM / WUSA workflows). (learn.microsoft.com)
A set of previously uploaded forum/archive materials in our internal files also shows how Microsoft integrated more recent inbox app updates directly into 24H2 media and has been rolling out Copilot-related experiences and bugfixes across multiple 26100-series builds throughout 2024–2025. That archival context helps explain why today's Release Preview update is largely an incremental refinement and rollout expansion rather than a wholesale feature rework.
Critical analysis — what this means for users and IT
The Build 26100.5061 update is noteworthy because it stitches AI features into core UI surfaces (File Explorer, Search, Settings) while also proceeding with platform cleanup and enterprise tooling improvements. The implications vary by persona.For everyday users and power users
Pros:- AI where you already work: Bringing image and text AI actions into File Explorer reduces friction for lightweight creative and productivity tasks. Users will be able to edit images and summarize documents without launching separate apps.
- Better discoverability: Click to Do tutorial and the Settings agent improve discoverability of AI and help features.
- Improved privacy controls: The Text & Image Generation settings and new snapshot filters for Recall give users explicit control over generative features and what data is captured locally.
- Copilot license requirements: Some AI actions (for example, Summarize in OneDrive/SharePoint) require a Microsoft 365 subscription and Copilot license, limiting availability for users without those entitlements. Microsoft’s blog explicitly calls out licensing requirements for certain features. (blogs.windows.com)
- Phased rollout confusion: Because many items are controlled feature rollouts, a given Insider machine may not see everything; A/B testing can produce inconsistency between machines and the perception that the update “failed” to deliver promised features. (blogs.windows.com)
For IT administrators and enterprises
Pros:- Stronger default images: Microsoft’s ongoing inclusion of updated inbox apps in 24H2 ISOs (and the checkpoint cumulative model) reduces the number of immediate post-setup updates, improving security posture out of the box. This streamlines imaging and onboarding workflows.
- Windows Backup for Organizations: The GA of this service can materially reduce friction for device refreshes and migrations when paired with endpoint management tooling.
- Quick Machine Recovery & resiliency updates: Features aimed at faster recovery and targeted fixes for widespread boot issues reduce downtime and triage complexity.
- PowerShell 2.0 removal is disruptive: Environments that still rely on legacy installers or scripts that explicitly invoke the PowerShell 2.0 engine will see failures unless those scripts are updated. Microsoft’s guidance is clear: migrate to PowerShell 5.1 or 7.x or update installers that expect -Version 2. This is a binary, breaking change for legacy automation that hasn’t been modernized. Administrators must inventory scheduled tasks and custom installers. (support.microsoft.com, learn.microsoft.com)
- Update sequencing & checkpoint complexities: Organizations using catalog-based offline deployments must respect checkpoint update sequencing and may need to download prior checkpoint packages for offline deployments. Overlooking this leads to failed installs or rollbacks in some scenarios. Microsoft documents the checkpoint process and recommends using the Catalog or DISM methods for offline imaging. (learn.microsoft.com)
- Potential for update-related instability: Historical reports across recent cumulative updates and checkpoint changes show occasional install failures or device-specific regressions (some of which have required Microsoft follow-up patches). While not unique to this release, admins should continue to test updates on representative hardware before broad deployment. Community reporting and Microsoft Support pages for adjacent KBs illustrate this pattern. (support.microsoft.com)
Recommended actions (for different audiences)
For home users and power users
- Back up critical data before installing preview or optional updates.
- Update Windows via Settings > Windows Update and opt into Release Preview only if you want early access to quality updates and features before general release.
- If you use Copilot-enabled features, verify licensing (Microsoft 365 + Copilot) where indicated.
- If you rely on third‑party apps that interact with system authentication or older PowerShell-driven installers, test them in a virtual machine with this build before updating a primary device.
For IT pros, sysadmins, and imaging teams
- Inventory scripts and scheduled tasks for explicit calls to PowerShell 2.0 (powershell.exe -Version 2). Plan migrations to PowerShell 5.1/7 or refactor installers.
- Test Build 26100.5061 in a pilot ring that mirrors the organization’s hardware diversity, especially Thinderbolt/USB4, storage (ReFS) scenarios, and devices with specialized IMEs.
- If using Microsoft Update Catalog and offline images, confirm checkpoint prerequisites and download any prior checkpoint MSU files that are required for your target image, then apply them in sequence or use DISM to merge updates. (learn.microsoft.com)
- Monitor the Windows Release Health dashboard and @WindowsUpdate communications for any post-release issues or guidance on mitigations. Microsoft Support KBs for adjacent builds are frequently updated with known issues and workarounds. (support.microsoft.com)
Privacy, security, and governance implications
Microsoft’s Release Preview notes and subsequent coverage take pains to highlight on-device processing for features such as Recall (snapshots saved locally and export protected by an export code in some regions), plus new Settings controls for generative AI usage. These moves are meaningful from a governance perspective.- Data locality and export controls: Recall snapshots and export workflows include encryption mechanics and codes for exporting content; organizations should confirm retention policies and data handling procedures before enabling continuous snapshot capture on corporate devices. (blogs.windows.com)
- Audit and consent: The Text and Image Generation controls let admins and users see which third‑party apps accessed generative models. Admins should consider whether to allow such access by default on managed devices and configure policies accordingly.
- Removal of legacy code for security: Eliminating PowerShell 2.0 from the default image reduces the attack surface from a deprecated, unsupported engine — a positive security outcome — but it also imposes a required migration for legacy tooling. Properly managed, the net security posture should improve; unmanaged, the change can create operational outages.
Known unknowns and unverifiable points
- At the time of publication, Microsoft’s Release Preview blog is the canonical listing of the build’s contents and date; some KB-level documentation pages for KB5064081 may not yet be published or fully populated on support.microsoft.com or the Microsoft Update Catalog. If a given IT workflow depends on catalog MSU files, check the Catalog and Microsoft Support for the KB article and file list. If the KB article for KB5064081 is not yet available in Microsoft Support, rely on the Release Preview blog for features and fixes but treat offline deployment workflows cautiously until MSU packages and file manifests are published. (blogs.windows.com, learn.microsoft.com)
- Phased rollouts may cause discrepancies between the blog’s feature list and what a given Insider device actually receives. This is expected behavior with controlled feature rollouts and A/B testing; no fix is needed other than patience and reporting via the Feedback Hub. (blogs.windows.com)
Bottom line
Windows 11 Build 26100.5061 (KB5064081) is a quality-focused Release Preview update that packages several incremental but significant user-facing AI features, privacy controls, and enterprise improvements while advancing Microsoft’s longer-term platform housekeeping (notably the removal of PowerShell 2.0). Users will see closer integration of Copilot capabilities into everyday surfaces like File Explorer and Search, while IT teams must prepare for the mandatory migration away from legacy PowerShell 2.0 usage and validate update sequencing for offline deployments.The update’s dual character — consumer-facing AI enhancements plus administrative changes — makes it essential for both end users and IT administrators to review the build notes, test in controlled rings, and follow Microsoft’s guidance on update delivery and deprecation timelines. For administrators, the immediate priorities are an inventory of PowerShell dependencies, pilot testing for device classes in your environment, and confirming offline deployment steps against Microsoft’s checkpoint guidance. (blogs.windows.com, support.microsoft.com, learn.microsoft.com)
By integrating generative AI into core OS surfaces while continuing to modernize the Windows platform, Microsoft is pushing Windows 11 24H2 further into a hybrid productivity and AI-first direction — but the usual caveats of phased rollouts, licensing, and legacy compatibility apply. For organizations and power users, cautious testing and targeted remediation (especially for PowerShell 2.0 dependencies) will be the prudent path forward. (blogs.windows.com, windowscentral.com, support.microsoft.com)
Source: Microsoft - Windows Insiders Blog Releasing Windows 11 Build 26100.5061 to the Release Preview Channel
Last edited:
