Microsoft's latest Windows 11 Insider Preview for the Canary Channel, Build 27934, landed on August 29, 2025, bringing with it a trio of much-needed stability fixes—and one glaring, deal-breaking regression that renders the built-in "Reset this PC" recovery tool completely unusable. The release, described by the Windows Insider team as "a small set of general improvements and fixes," underscores the high-risk, high-reward nature of the Canary Channel: Insiders get early access to bug fixes for core components like the Desktop Window Manager (DWM) and Windows Terminal, but they must also accept that a critical system recovery pathway is now dead in the water until the next flight.

Build 27934 at a Glance

The focus of this build is squarely on reliability, with no new user-facing features announced. The official changelog highlights three key fixes:

  • Reduced DWM crash frequency that caused a brief black flash on the screen.
  • Resolved a regression where launching cmd.exe from the Run dialog opened the legacy Windows Console Host instead of the configured default terminal, Windows Terminal.
  • Addressed an underlying issue that caused certain UWP apps to crash while scrolling.

At the same time, Microsoft flagged several known issues, the most severe of which is:

  • "Reset this PC" (Settings > System > Recovery) does not work on Build 27934. The company recommends rolling back to the previous build via Go Back if a reset is needed, and promises a fix in the next Canary flight.

Other known issues include a potential hang when scanning for temporary files in Storage settings and incorrect low-space indicator colors in File Explorer's dark mode.

The Fixes That Matter

DWM Crashes: More Than a Flash in the Pan

The black flash caused by DWM crashes might seem minor, but the Desktop Window Manager is the compositing engine that renders every visual element on your screen—from window frames and animations to overlays and transparency. Instability in DWM can cause a cascade of subtle but disruptive problems: dropped frames during video playback, screen tearing, interference with recording and streaming apps, and, in extreme cases, full application crashes. With Build 27934, Microsoft says it has reduced the frequency of these crashes, targeting a regression introduced in an earlier build. For Insiders who rely on their test machines for tasks like media editing or remote collaboration, this fix is a welcome stabilization.

Windows Terminal: Defaults Must Be Honored

For power users and developers, the terminal is a sacred space. The bug that caused a non-elevated cmd launch from the Run dialog to open the ancient Windows Console Host—even when Windows Terminal was set as the default—broke a fundamental expectation. Modern terminal profiles carry specific environment variables, font settings, and color schemes. Falling back to the legacy console could silently alter script behavior or confuse users accustomed to tabs and Unicode support. Build 27934 restores the correct behavior, ensuring that the default terminal setting is respected every time. Microsoft’s acknowledgment and swift fix signal the growing importance of terminal consistency in Windows 11.

UWP Scrolling Crashes: Smoothness Restored

The fix for UWP app crashes during scrolling targets an “underlying issue” in the interaction or rendering pipeline. Scrolling is a fundamental gesture used across countless apps—news readers, photo galleries, settings pages, and inbox apps. A crash here erodes trust in the platform's polish. While Microsoft didn’t detail the root cause, such regressions often stem from compositor or input stacking anomalies. For Insiders testing third-party UWP apps, this fix should lead to a noticeably smoother experience.

The Big Red Flag: Reset this PC Regression

However, all the goodness of the fixes is overshadowed by a single, crushing known issue: Reset this PC is completely broken in Build 27934. The feature, located under Settings > System > Recovery, is a lifeline for users troubleshooting persistent issues or preparing a device for handoff. On this build, it simply fails to initiate.

Microsoft’s mitigation is to roll back to the previous build (using Go Back, also available in Recovery) and then perform the reset from there. But there’s a catch: the Go Back option is only available for a limited window after an upgrade (typically 10 days) and can be missing if the Windows.old folder has been cleaned up. For Insiders who skipped creating a full backup or who rely on Reset as part of a routine re-provisioning workflow, this regression could leave them stranded with an unstable system and no easy escape. The official blog post states the fix will land in the next Canary flight, but no date is given.

Other Known Issues: Storage Scan and Dark Mode Quirks

Build 27934 also carries forward a couple of less critical but annoying bugs:

  • Storage > Temporary files scanning gets stuck: Windows may appear to freeze while enumerating temporary files and previous Windows installations. This can block users trying to free up disk space and may prevent the listing of large redundant files.
  • File Explorer dark mode color anomalies: In dark mode, the low disk space indicator in This PC uses incorrect colors—sometimes black on dark backgrounds—making it nearly illegible. For accessibility-focused users or those who rely on visual cues for disk management, this is a meaningful drawback.

Who Should Install Build 27934

This build is a mixed bag, so the decision to install hinges on your risk tolerance and use case.

Install if:
- You are an enthusiast running Canary on a dedicated test machine and you actively file feedback.
- You are a developer or ISV tracking DWM, terminal, or UWP regressions and need to verify the fixes.
- You have a robust backup and rollback plan in place and you are comfortable using recovery media if things go south.

Skip or postpone if:
- Your device is used for daily productivity, school, or any task where a non-functional reset would be a crisis.
- You rely on “Reset this PC” for device reprovisioning or troubleshooting in a corporate environment.
- You need consistent visual indicators for disk space in File Explorer due to an accessibility requirement.

In short: this is a build for the lab, not the living room.

Practical Guidance for Insiders

If you decide to take the plunge, follow these steps to minimize pain:

  • Back up everything: Create a full system image or at least a System Restore point before updating. Ensure your personal files are synced to a cloud service or an external drive.
  • Verify the Go Back grace period: After installing, confirm that the "Go back" option is available in Recovery. If it’s gone, your only fallback may be a clean install or recovery media.
  • If Reset becomes necessary: Immediately roll back to the previous build (Settings > System > Recovery > Go back) and initiate the reset from there. Do not attempt Reset from the broken build.
  • Watch for Storage hang: If the Temporary files scan hangs, be patient. If it remains stuck for an extended period, file feedback with diagnostic logs via Feedback Hub.
  • Test terminal behavior: Developers and IT pros should verify that launching cmd from the Run dialog now consistently opens Windows Terminal when it’s set as the default. If not, document the repro steps and report them.

How to Report Bugs Effectively

Microsoft relies on Insider feedback to prioritize fixes. To make your report count:

  • Use Feedback Hub (Win + F) and include the build number (27934) in the title.
  • Provide clear repro steps and note the frequency of the issue.
  • Attach screenshots or a short screen recording for visual glitches like the DWM black flash or File Explorer color issues.
  • For Reset failures, mark the feedback as high-severity and include system specifications and any error codes.
  • Developers can accelerate triage by attaching ETW traces or crash dumps.

Keep an eye on the Flight Hub and the Windows Insider blog for updates on when the Reset regression is resolved.

What Build 27934 Reveals About Microsoft’s Canary Strategy

This flight is a textbook example of Microsoft’s evolving approach to the Canary Channel: rapid iteration, transparency about regressions, and a willingness to ship fixes even when they carry significant side effects. Unlike the Dev or Beta channels, Canary accepts breakage as a trade-off for early feedback. The fact that Microsoft explicitly called out the Reset regression and provided a concrete workaround (roll back to the previous build) shows a pragmatic understanding that Insiders need clear guidance—but also a sobering reminder that Canary is not a daily driver.

The tight focus on compositor and shell reliability (DWM, File Explorer, terminal) hints at upcoming feature work that requires a stable visual stack. Builds like 27934 are often preludes to more ambitious experiments, so the community should expect the next few flights to either patch the Reset hole or introduce new, possibly disruptive, capabilities.

The Community’s Reaction

While this article draws primarily from the official announcement, early chatter in Windows Insider forums and social media channels indicates a predictable split: developers and enthusiasts who value the DWM and terminal fixes are already installing on spare machines, while those who depend on the Reset function are loudly warning others to stay away. The Storage scanning hang and dark mode color bugs are drawing less attention, likely because they don’t threaten system recoverability. Feedback Hub will see a surge of reports on the Reset regression, and Microsoft’s response time—whether the fix arrives in the very next flight or requires a multi-cycle delay—will be a key test of the team’s agility.

Bottom Line

Windows 11 Canary Build 27934 is a maintenance flight with teeth. It knocks out three annoying regressions that were degrading the experience for testers, but it simultaneously renders the system’s primary built-in recovery tool inert. For Insiders with proper backups and a willingness to roll back, the trade-off is worth it for the stability gains. For everyone else, the only sane move is to wait for the follow-up build that restores Reset functionality. In the gamble of living on the bleeding edge, this release is a clear-eyed reminder: the edge can cut both ways.