Windows 11 Insider Preview Build 27934: Canary fixes and Reset regression

​

Microsoft pushed a small-but-significant Canary-channel preview on August 29, 2025, when Windows Insiders received Windows 11 Insider Preview Build 27934, a focused flight that fixes several user-facing stability issues while adding an important caution for anyone relying on built‑in recovery tools.

Background​

Canary-channel builds are deliberately experimental: they represent the earliest platform changes in Windows 11’s development cycle and are intended for feedback and testing rather than daily-driver stability. Microsoft’s own announcement for Build 27934, published August 29, 2025, describes this flight as “a small set of general improvements and fixes” — the kind of housekeeping update that rarely introduces headline features but can materially affect day‑to‑day reliability for Insiders and testers.
Industry and community trackers show Build 27934 arriving as part of a steady August cadence that included previous Canary flights (including Build 27924 and Build 27928 earlier in the month). Those earlier builds introduced rolling feature experiments (Snipping Tool updates, Settings refinements, and Canary-only trials), and 27934 continues the pattern: incremental fixes, a few visual quirks called out, and one high-impact recovery limitation that deserves attention.

---

What’s in Build 27934 — Quick summary​

• Release date: August 29, 2025 (Canary Channel).
• Primary focus: stability and reliability fixes across windowing, terminal defaults, and UWP app behavior.
• Notable fixes:
• Reduced DWM (Desktop Window Manager) crash frequency that could produce a brief black flash.
• Fixed a regression where non‑elevated launches of cmd.exe from Run could open Windows Console Host instead of the configured default, Windows Terminal.
• Addressed underlying causes for certain UWP apps crashing while scrolling.
• Known issues highlighted by Microsoft:
• Settings > System > Storage > Temporary files may get stuck when scanning.
• Visual/color problems in This PC when File Explorer is in dark mode (low space indicator colors wrong).
• A critical regression: “Reset this PC” (Settings > System > Recovery) will not work on this build — Microsoft says it will be fixed in the next Canary flight; as a workaround, roll back to the previous build to perform a reset.

These points are taken from the official announcement from the Windows Insider team and cross‑checked against public build lists and contemporary reporting to ensure the release date and scope are consistent with public records.

---

Why this small release matters​

At first glance, Build 27934 reads like a maintenance patch, but several aspects make it noteworthy for Insiders and IT practitioners:

• DWM stability matters: Desktop Window Manager manages compositing and visual effects. A regression that increases DWM crashes — even if those crashes manifest only as a “black flash” — can undermine trust in other visual subsystems, interfere with video capture, and break timing-sensitive apps (games, real‑time collaboration tools). A fix here reduces a subtle but high‑annoyance failure mode.
• Terminal defaults affect workflows: Power users and developers expect terminal behavior to be reliable. The bug where launching cmd from Run opened the legacy Windows Console Host despite Windows Terminal being set as the default could break scripted workflows, cause inconsistent environment initialization (profiles, shells), and surprise users who assume modern default terminal behavior.
• UWP / scrolling crashes: Fixing UWP scroll crashes helps app reliability for both first‑party inbox apps and third‑party UWP packages. Scroll behavior touches numerous UI surfaces — fixing the regression improves perceived polish across the platform.
• Recovery tool regression is critical: The “Reset this PC” failure is a high‑impact known issue. Reset is a primary recovery option for damaged systems; making Reset unusable forces Insiders to rely on rollbacks, external media, or repair tools. For people testing Canary builds, that restriction can be disruptive and increases the risk of being unable to recover without a clean installation.

---

Deep dive: the fixes that landed​

DWM crash reduction​

Microsoft reports that Build 27934 fixes a regression causing an increase in DWM crashes in the preceding flight. While the announcement frames the symptom as a visual “black flash,” the underlying implications are broader. DWM governs compositing, window animations, and overlays; instability here can:

• cause short visual artifacts and flicker,
• drop frames during graphics playback,
• interfere with screen recording and streaming,
• and in worst cases, cascade into app-level failures.

The fix is therefore important even though it might not have been obvious to all Insiders. Vendors and developers that integrate with the Windows compositing stack should monitor telemetry and user reports after this build to confirm the regression is fully resolved.

Windows Terminal vs. Console Host behavior​

The build fixes a specific regression: launching cmd (non‑elevated) from the Run dialog sometimes opened the legacy Windows Console Host instead of the user’s preferred terminal (Windows Terminal) even when Windows Terminal was set as the default terminal application.
Why this matters:

• Windows Terminal supports profiles, tabs, UTF‑8 defaults, and richer configuration; unintentionally falling back to the legacy Console Host changes environment variables, path handling, and the shell experience.
• Automated scripts or keyboard shortcuts that rely on a modern terminal profile could behave inconsistently for affected users.
• Fixing this regression restores the principle of “what you set as default should be respected,” which is essential for polished user experience.

UWP scrolling crashes​

An “underlying issue” that caused some UWP apps to crash while scrolling in recent builds was addressed. Scrolling code is typically in gesture/interaction pipelines or rendering paths; crashes here can result from shader or compositor regressions, race conditions, or input event handling anomalies. Fixing it reduces app instability, particularly for apps that load content dynamically while scrolling (lists, photo viewers, news readers).

---

Known issues — what to watch for​

Microsoft listed several important known issues for Build 27934. These aren’t theoretical; they have practical consequences.

• Settings > System > Storage > Temporary files scanning getting stuck: users may see the Storage page freeze while Windows attempts to enumerate temporary files and previous Windows installations. This can confuse users trying to reclaim disk space and may hide the presence of prior Windows installations.
• File Explorer color anomalies in dark mode: colors used for low‑space indicators may be too light or otherwise incorrect (black used for "space remaining"), reducing legibility and potentially hiding critical disk warnings.
• Reset this PC broken: the biggest red flag. If you rely on the in‑OS reset flow for troubleshooting or device reprovisioning, this build prevents that flow from working. Microsoft specifically recommends rolling back to the previous build to perform a reset until the next Canary flight fixes the issue.

These known issues underscore the Canary Channel trade‑off: early access to internal changes for feedback in exchange for instability and functional regressions.

---

Who should install Build 27934 — and who should not​

• Recommended for:
• Enthusiasts and testers who run Canary builds on secondary machines and actively file feedback.
• Developers and ISVs tracking regressions in the compositor, terminal, or UWP frameworks.
• Teams that need to verify whether earlier regressions are fixed in current flights.
• Not recommended for:
• Productivity machines that must remain recoverable by the user without rollback or external media.
• End users in enterprise environments where Reset workflows or unattended recoveries are part of lifecycle procedures.
• Systems that cannot afford potential File Explorer visual anomalies (e.g., accessibility requirements relying on clear visual cues).

In short: install on test devices only. If installed on a device you need operational every day, be prepared with backup and rollback plans.

---

Practical guidance: installing, rolling back, and mitigating risk​

• Before updating, create a full system image or at least a System Restore point and a current backup of user data.
• If you rely on Reset this PC for device reprovisioning, do not install Build 27934 on machines where a broken reset would be a problem.
• To install: use Settings > Windows Update on an Insider-joined device in the Canary Channel and follow the normal update flow. Allow the device to complete post‑update reboots and check reliability via Event Viewer or Reliability Monitor.
• If Reset is required after installing Build 27934:
• Roll back to the previous build (Settings > System > Recovery > Go back) and then perform Reset.
• If Go back is unavailable, be prepared to use recovery media or an in‑place upgrade/repair install.
• If you encounter the Storage scanning hang, allow extra time; if scanning remains stuck, file a feedback report in Feedback Hub with diagnostic logs.
• For developers and power users who saw the cmd → Console Host regression, verify that launching cmd from Run now adheres to Windows Terminal defaults. If not, capture repro steps and file feedback.

These steps reflect best practices for preview builds and specifically address the recovery regression highlighted in Microsoft’s announcement.

---

How to report bugs and increase the chance of a fix​

• Use Feedback Hub (WIN + F) and include:
• Repro steps and frequency,
• Relevant system logs (collect via Reliability Monitor or the Feedback Hub diagnostic pack),
• Screenshots or short screen recordings showing the issue (especially useful for visual artifacts or the DWM black flash).
• For high‑impact issues like Reset not working, mark the feedback as severe and include full device details and KB/build numbers.
• If you’re a developer reproducing a crash, attach ETW traces or crash dumps where possible. These artifacts accelerate triage.
• Check Flight Hub and Microsoft’s release blog for updates — Microsoft will typically mark the known issue as resolved in a subsequent Canary flight and explain any necessary user actions.

---

Analysis: Microsoft’s Canary strategy and what this flight reveals​

Build 27934 is illustrative of how Microsoft is balancing iterative stabilization with ongoing experimentation:

• Canary remains the place for low‑risk feature experiments, but Microsoft still needs to maintain a baseline of platform stability. This build focuses on reducing regressions rather than shipping new consumer-facing features.
• The inclusion of a “Reset this PC” regression — and Microsoft’s explicit “roll back to previous build” mitigation — shows a pragmatic approach: if a critical recovery path breaks, provide a validated workaround rather than shipping a hotfix mid‑flight. This reflects the Canary channel’s nature where small, targeted fixes roll frequently.
• The Windows engineering team appears to be tightening focus on compositor and shell reliability (DWM, File Explorer, visual elements). That suggests upcoming flights may prioritize stability for richer feature experiments (e.g., Compose/Recall/Click to Do, accessibility additions) to land in other channels later.

From an organizational perspective, the message is clear: Canary is active development. Teams should use Canary to catch regressions early, but not as a staging environment for broad rollouts.

---

Risks for IT and system administrators​

• Device provisioning pipelines that rely on Reset this PC as a troubleshooting or repurpose method are vulnerable until the fix lands. Organizations using Canary on test fleets should update change logs and retrain technicians on rollback procedures.
• Automation relying on consistent terminal defaults may be affected if any devices still exhibit the legacy Console Host fallback. CI/CD or remote developer setups should validate terminal behavior post‑update.
• Accessibility: color anomalies in File Explorer can degrade readability for low‑vision users; organizations should avoid Canary on accessibility-dependent devices until the issue is corrected.
• Timebomb/expiration: Canary builds often have expirations or require ongoing updates. Teams using Canary for testing must track expiration dates and ensure update compliance; otherwise, devices can enter unsupported states.

---

The community reaction and what to expect next​

Community forums and insider channels typically react quickly to Canary flights. Expect:

• Immediate feedback reports focused on the Reset regression and Storage scanning hangs.
• Verification posts from developers and power users confirming the DWM and terminal fixes.
• A rapid follow‑up Canary flight addressing the Reset regression (Microsoft said it will be fixed in the next flight).

Insider channels often show patterns: a small maintenance flight is followed by a daily/weekly sequence of additional builds that close out known issues. Monitoring Flight Hub and the Windows Insider blog over the next week will reveal Microsoft’s remediation timeline.

---

Recommendations for readers​

• If you run Canary on a secondary machine for testing: install Build 27934 to confirm whether the DWM/terminal/UWP fixes resolve your issues, and file any new feedback you encounter.
• If you run Canary on a device used for work, learning, or critical tasks: postpone installing this build until the Reset regression is fixed, or ensure you have robust recovery media and a tested rollback plan.
• For IT teams building automation or support playbooks: update documentation to highlight that Reset this PC is temporarily non‑functional on Build 27934 and outline rollback steps.
• For developers targeting the Windows 11 platform: test terminal behavior and UWP scrolling to ensure your apps behave consistently across recent Canary flights.

---

Conclusion​

Windows 11 Insider Preview Build 27934 is a classic Canary flight: modest in scale but important in scope for people tracking stability. Microsoft fixed regressions that touch core UX components — DWM, terminal defaults, and UWP scrolling — while flagging a critical recovery regression that temporarily breaks Reset this PC. The practical takeaway is simple: Insiders who need to test stability and file feedback should install the build on test devices; anyone who relies on Reset or needs rock‑solid recovery must delay or prepare contingency plans.
For the broader Windows ecosystem, 27934 demonstrates Microsoft’s incremental approach: push fixes into Canary quickly, surface issues transparently, and rely on the Insider community to validate changes before broader rollouts. The next Canary flight should close the Reset gap and further harden the platform; until then, treat this build as useful for targeted validation, not as a safe harbor for production use.

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 27934 (Canary Channel)

 

[ChatGPT]

Microsoft released a compact but consequential Canary-channel preview today — Windows 11 Insider Preview Build 27934 — that patches several user-facing crashes (notably in the Desktop Window Manager and some UWP apps) while also introducing a serious recovery regression that temporarily disables the in‑OS “Reset this PC” flow. (blogs.windows.com) (neowin.net)

Overview​

Build 27934 arrived as a small, targeted maintenance flight on August 29, 2025. Microsoft describes the update as “a small set of general improvements and fixes” focused on windowing stability, terminal behavior, and UWP app reliability. The key fixes listed by Microsoft include:

• Reduction of a regression that caused an increase in DWM (Desktop Window Manager) crashes that manifested as short black flashes.
• A fix for a regression where launching cmd.exe non‑elevated from the Run dialog sometimes opened the legacy Windows Console Host instead of the user’s default Windows Terminal.
• A resolution for an underlying issue that could cause certain UWP apps to crash while scrolling. (blogs.windows.com)

Independent reporting and community trackers confirm the build notes and date, and the coverage underscores the same three areas of attention. (neowin.net)

---

Background: why a small Canary flight matters​

The Canary Channel is Microsoft’s earliest lab for platform changes: it surfaces experimental changes quickly and is explicitly not intended for production devices. That context matters because the fixes in 27934 are narrowly scoped but touch core subsystems — the compositor (DWM), terminal associations, and app rendering pipelines — which influence both everyday polish and certain high‑impact workflows such as screen capture, streaming, and automated developer environments.

• DWM controls visual compositing and animations. Even transient compositor instability can degrade video capture, drop frames in games, or affect real‑time collaboration apps.
• Terminal associations matter to developers and scripts. The fallback to the legacy console can break profile initialization, UTF‑8 handling, and other behavior users expect from Windows Terminal.
• UWP scrolling touches many inbox and third‑party apps. Scroll crashes often cascade into poor perceived quality across apps that load content dynamically.

Microsoft’s official notes for Build 27934 make these priorities explicit and caution Insiders about remaining known issues. (blogs.windows.com)

---

What Build 27934 fixes — technical breakdown​

DWM crash reduction​

The Windows Insider changelog states Build 27934 fixes an increase in DWM crashes that had begun appearing in prior flights; the visible symptom for many users was a brief “black flash” where composited content momentarily disappeared. While that artifact may seem cosmetic, the underlying compositor is responsible for frame timing, overlays, and window composition — so instability can affect:

• Screen recording and streaming reliability.
• Full‑screen app transitions and game rendering.
• Compositor‑dependent GPU interactions.

Microsoft’s statement confirms the regression was addressed in this flight. Community engineers and testers are being asked to validate the change across hardware profiles to ensure the fix is durable. (blogs.windows.com)

Windows Terminal vs. Console Host regression​

A regression introduced in earlier Canary flights caused cmd.exe launched from the Run dialog (non‑elevated) to sometimes open in the legacy Windows Console Host even when Windows Terminal was set as the default terminal app. That behavior breaks assumptions for power users and scripts that rely on modern terminal defaults (profiles, shell initialization, UTF‑8 defaults).
Build 27934 restores the expected mapping so that what you set as your default terminal is respected. If you still encounter the fallback, the temporary workaround remains to type wt into the Run box to launch Windows Terminal directly. (blogs.windows.com)

UWP scrolling crashes​

Microsoft lists a fix for an “underlying issue” that could cause certain UWP apps to crash while scrolling. Scrolling paths frequently touch gesture pipelines, rendering layers, and shader/compositor interactions. The correction should reduce crashes in dynamic list views and content feeds used by inbox and packaged apps. As with compositor fixes, developers should validate their apps on this build and file repros if anomalies persist. (blogs.windows.com)

---

Known issues and the critical recovery regression​

Build 27934 ships with several known issues Microsoft explicitly calls out. Two cosmetic/functional items and one critical regression require attention:

• Settings > System > Storage > Temporary files: scanning may get stuck and fail to show previous Windows installations.
• File Explorer dark‑mode color anomalies: low‑space indicators may show incorrect colors (e.g., black used for remaining space or a washed‑out red) and affect legibility.
• Reset this PC (Settings > System > Recovery) will not work on this build. Microsoft warns this is a new regression and instructs Insiders to roll back to the previous build to perform a Reset; the company says a fix will arrive in the next Canary flight. (blogs.windows.com) (neowin.net)

The Reset regression is the most consequential because Reset is a primary in‑OS recovery tool for damaged or misconfigured systems. Blocking Reset increases the dependency on rollbacks, external recovery media, or clean installs — precisely the types of operations Canary testers may be trying to avoid.
Community discussion and internal analysis mirror Microsoft’s warning: testers are urged not to install this flight on machines where Reset or a stable recovery path is required.

---

Who should (and should not) install Build 27934​

This build’s risk profile makes the recommendation simple:
Recommended for

• Enthusiasts and developers who run Canary on secondary test machines and actively submit feedback.
• ISVs and QA teams tracking DWM, terminal, or UWP rendering regressions and wanting to verify fixes.
• Power users who can tolerate Canary churn and have robust rollback or recovery media.

Not recommended for

• Production laptops, primary workstations, or devices used for critical tasks where the inability to Reset would be disruptive.
• Enterprise test fleets that depend on Reset workflows for reprovisioning or troubleshooting.
• Accessibility‑critical devices where File Explorer color issues could impair usability.

---

Practical guidance: install, verify, and mitigate​

If you decide to test Build 27934, follow these practical steps to reduce risk:

• Backup first.
• Create a full image backup or at minimum a verified file backup of important data.
• Export or note licensing keys and device‑specific configuration before upgrading.
• Use isolated hardware.
• Install Canary builds on secondary devices or virtual machines that can be reprovisioned quickly.
• Verify post‑update behavior.
• Confirm DWM stability by running full‑screen video playback, screen recording, and a game session to spot regressions in compositing or frame drops.
• Test terminal behavior by launching cmd from Run and by running scripts that expect Windows Terminal behavior.
• Reproduce any previously observed UWP scroll crashes and capture crash dumps where possible.
• If a Reset is needed after installing 27934:
• Use Settings > System > Recovery > Go back to roll back to the prior build, then perform Reset there.
• If Go back is unavailable, be prepared to use recovery media (USB installation media) or perform an in‑place repair install with an ISO.
• Report actionable feedback.
• Use Feedback Hub (WIN + F) and attach repro steps, Reliability Monitor logs, and short screen recordings showing visual artifacts (especially useful for DWM black flashes). Mark critical recovery breakages as severe.

Community posts succinctly summarize similar mitigation advice and stress the importance of marking critical feedback for expedite triage.

---

What this build signals about Microsoft’s Canary strategy​

Build 27934 is instructive about Microsoft’s approach to Canary-channel releases:

• Canary remains a place for focused stabilizations and rapid experimentation, not a preview of a final feature set tied to a specific release.
• Microsoft practices rapid enable/disable of experiments (for example, rolling back battery icon changes or toggling other UI experiments) based on telemetry and feedback.
• The release shows an emphasis on compositor and shell reliability as a foundation: DWM, File Explorer, and related UI pathways are being hardened so that more ambitious feature tests (Copilot integrations, Click to Do, etc.) can land on a stable base.

This behavior is consistent with previous Canary activity: small, frequent flights that alternate between experiments and housekeeping fixes. The trade‑off is volatility — fixes can introduce new regressions — which is an accepted part of Canary’s role.

---

Strengths and limitations: a critical appraisal​

Strengths

• Targeted, high‑value fixes. Addressing DWM crashes and terminal association regressions improves reliability in areas that materially affect user experience and developer workflows.
• Transparent known‑issue disclosure. Microsoft’s candid listing of the Reset regression and Storage scanning hang helps Insiders make informed choices before installing.
• Rapid iteration model. Canary’s cadence allows Microsoft to roll out micro‑fixes quickly and revert experiments that misbehave.

Limitations and risks

• Recovery regression is a high‑impact oversight. Breaking Reset is not a cosmetic bug — it affects the device lifecycle for anyone who relies on built‑in recovery rather than external media.
• Canary’s telemetry surface may not cover all hardware permutations. Compositor and driver interactions are hardware‑sensitive; community verification across GPU vendors, driver versions, and SoC families is essential.
• Cosmetic regressions can have accessibility consequences. File Explorer color issues in dark mode reduce legibility for low‑vision users and must be prioritized for accessibility parity.

Where claims are based on Microsoft’s release notes (for example, references to specific DLL fixes or internal causality), treat those as company‑reported until corroborated by community telemetry or independent testing. Build notes sometimes mention under‑the‑hood artifacts (DLL names, stack traces) that the broader community cannot immediately verify; flag those items for follow‑up scrutiny.

---

How developers and IT pros should respond​

Developers

• Validate apps against the compositor and UWP scrolling fixes by running test cases that exercise list virtualization, dynamic content loads, and heavy GPU usage.
• If an app still crashes, collect crash dumps and ETW traces and submit them through Feedback Hub and via existing support channels.

IT administrators

• Block Canary-channel builds on pilot endpoints used for provisioning or where Reset workflows are part of standard reclaim/reprovision procedures.
• Update runbooks to include contingency steps: how to roll back a Canary build, how to use recovery media, and how to recover devices in bulk if Reset is unavailable.
• Monitor Flight Hub and the Windows Insider blog for the follow‑up Canary flight that Microsoft promised will fix Reset. (blogs.windows.com)

---

What to watch next​

• The promised follow‑up Canary flight that fixes the Reset regression; Microsoft committed to returning Reset functionality in the next Canary flight. Confirm that recovery is restored before using Canary on critical devices. (blogs.windows.com)
• Community verification of the DWM fix across major GPU vendors and driver stacks. Look for reports from users running varied hardware (Intel, AMD, NVIDIA) to confirm the regression is resolved broadly.
• Whether File Explorer color anomalies are reworked for accessibility parity rather than merely patched cosmetically.
• Any additional regressions introduced by the build that may surface in real‑world usage, particularly around storage scanning and previous Windows installation listings.

---

Conclusion​

Windows 11 Insider Preview Build 27934 is a concise Canary flight that addresses several important stability issues — notably DWM crashes, terminal association regressions, and UWP scroll crashes — while exposing a noteworthy risk by disabling the in‑OS Reset flow. For Insiders who depend on rapid validation and who maintain robust rollback and recovery procedures, the build is a reasonable test candidate. For anyone using a device where Recoverability is a must, the prudent choice is to defer Canary updates until Microsoft confirms Reset has been restored in a follow‑up flight. The official Windows Insider announcement and independent coverage both emphasize that Canary is experimental and intended for testers, not production users. (blogs.windows.com) (neowin.net)

---

(For those testing Build 27934: back up before you upgrade, validate DWM and terminal behavior, and be prepared to roll back to restore Reset if you need it.)

---

Source: Neowin Windows 11 gets fixes for DWM and app crashes in new Canary build 27934