Windows enthusiasts running the bleeding‑edge Canary channel got a welcome dose of practical polish this week when Microsoft shipped Build 27943, a maintenance flight that squashes two particularly irksome regressions: a Settings freeze during Temporary files scans and an HDR toggle that would flip back to SDR seconds after being enabled. The release also quieted spurious Event Viewer errors tied to the Microsoft Pluton Cryptographic Provider, mended duplicate taskbar thumbnails, and restored Enter‑key confirmation for casting PINs. Yet the build arrives with a stern caveat—Microsoft explicitly warns of persistent installation rollbacks and a kernel‑level crash on Arm64 devices that can trigger green‑screen reboots.

This flight epitomizes the Canary channel’s dual nature. It delivers rapid fixes that directly soothe day‑to‑day friction for testers but simultaneously carries known blockers that rule out any installation on production or daily‑driver hardware. Coupled with simultaneous Release Preview updates for Windows 11 and Windows 10, the Insider ecosystem shows Microsoft methodically threading reliability improvements through multiple channels while isolating high‑risk changes to the lab.

The headline fixes unpacked

Storage → Temporary files scan no longer hangs

For weeks, Insiders who navigated to Settings > System > Storage > Temporary files could find the UI frozen as it attempted to enumerate deletable items. The scanner would stall, and critically, the “Clean up previous Windows installations” entry—often responsible for multiple gigabytes of recoverable space—simply refused to appear. Anyone who regularly upgrades or rolls back builds felt the sting immediately. Without that entry, reclaiming space required manual intervention with DISM, disk cleanup command‑line tricks, or third‑party tools.

Build 27943 patches the enumeration logic responsible for the hang. Early reports from the forum confirm that the scanner now completes reliably and restores the “Clean up previous Windows installations” option, letting testers recover disk space through the familiar Settings UI. For Insiders who juggle multiple builds, this fix removes a recurring, manual housekeeping chore.

HDR toggle stays put

A more recent regression caused HDR to switch back to SDR moments after being enabled via Settings. Creators relying on high‑dynamic‑range color for photo editing or video work found their screens suddenly flat, and gamers who expect immersive visuals watched their displays revert mid‑session. The fix in 27943 corrects the toggling logic so that HDR remains active as long as the user wants it. Community feedback suggests the fix holds steady, though a handful of testers are still monitoring for edge cases around display wake or resolution changes.

Taskbar, Event Viewer, and other quality‑of‑life repairs

  • Duplicate thumbnail previews: Heavy multitaskers who minimize apps and switch virtual desktops would occasionally see twin thumbnail previews when hovering over taskbar icons. That cosmetic distraction is gone.
  • Pluton Event Viewer noise: Administrators were tripping over meaningless error entries generated by the Microsoft Pluton Cryptographic Provider. Build 27943 silences those events, reducing log clutter.
  • Quick Settings PIN confirmation: Pressing Enter to confirm a casting PIN now works as expected—a small but vital fix for meeting‑room and presentation flows.
  • Group Policy Editor in Chinese: The gpedit.msc interface, when using the Chinese display language, had large blank areas that impeded administrative tasks. The layout now renders correctly.

These are not flashy feature drops, but their cumulative effect on perceived stability is undeniable. They remove friction points that, over time, erode confidence in insider builds.

Known issues: the real blockers

Microsoft is transparent about two high‑impact problems that remain unfixed in Build 27943, and both should give Insiders pause before installing—even on dedicated test machines.

Installation rollbacks (error codes 0xC1900101‑0x20017, 0xC1900101‑0x30017)

Some devices encounter a rollback during installation, halting the upgrade with codes from the 0xC1900101 family. Trying again typically produces the same result. The root cause can involve driver incompatibilities, particularly with graphics or storage controllers. For affected users, the build simply won’t take hold, making this a true deployment blocker. Microsoft has not provided a timeline for a fix, and forum moderators advise capturing setup logs (setuperr.log and setupact.log) to aid diagnosis.

Arm64 kernel bugcheck (IRQL_NOT_LESS_OR_EQUAL)

On certain Arm64 devices, the kernel hits an IRQL_NOT_LESS_OR_EQUAL stop error, leading to a green screen and unpredictable reboots. This is not a theoretical risk: users have reported losing unsaved work and, in write‑heavy scenarios, possible data corruption. If you run Windows on a Snapdragon‑powered machine, the advice is crystal clear—skip Build 27943. Microsoft engineers are actively investigating, but until a fix lands, Arm64 testers should remain on a previous Canary build or switch to a less volatile channel.

Additionally, the release notes flag graphics flicker scenarios and PIX playback incompatibilities for developers. GPU capture tooling remains fragile, so game developers and DirectX engineers should avoid upgrading their primary analysis machines.

Release Preview updates: safer stability improvements

In parallel, Microsoft published two Release Preview cumulative updates that matter to a far broader audience.

KB5065790 for Windows 11 version 23H2 (Build 22631.5982)

  • Fixes a SIM PIN sign‑in freeze that left users locked out without a restart.
  • Resolves Remote Desktop crashes when using multiple monitors, a persistent pain point for hybrid workers.
  • Stops printer queue UI crashes when viewing shared queues.
  • Updates mobile operator profiles (COSA) for WWAN and eSIM devices.

These are production‑grade fixes that organizations should pilot immediately, especially on devices used for remote desktop workflows and cellular connectivity.

KB5066198 for Windows 10 version 22H2 (Build 19045.6388)

A general reliability rollup focused on performance tuning and stability for the still‑sizeable Windows 10 installed base. Microsoft’s documentation for this KB remains sparse, a common pattern for early Release Preview drops. IT administrators should therefore test thoroughly before wide deployment, even though these updates are far more vetted than Canary flights.

Analysis: what this flight tells us about Windows 11’s trajectory

Build 27943 reinforces a pattern that has defined the 27xxx series: Canary is the rapid‑response lab where regressions are caught and crushed before they contaminate broader channels. The temporary files scan fix, for instance, likely prevents a serious support headache once its underlying code graduates to Dev and Beta. The HDR toggle repair saves Microsoft from a wave of community complaints that would inevitably flood Feedback Hub and social media.

Still, the stability trade‑off is real. The rollback and Arm64 kernel issues underscore that Canary exists precisely to expose such landmines. For the average Windows enthusiast reading this, the key takeaway is discipline: unless you are running a secondary test machine with a full disk image backup, Canary is not for you.

The Release Preview updates, meanwhile, show Microsoft’s commitment to servicing both Windows 11 and Windows 10 with surgical reliability fixes. KB5065790’s multi‑monitor RDP fix, in particular, addresses a problem that has frustrated remote workers for months. These types of updates may lack sizzle, but they are the lifeblood of enterprise trust.

Recommendations by user profile

Production endpoints and managed fleets

Do not install Build 27943. The risk of installation failure or kernel crashes is too high. Instead, pilot KB5065790 and KB5066198 on a representative subset of devices. Focus on machines that regularly use Remote Desktop, WWAN, or shared printer queues—exactly the scenarios these updates target.

Insiders on dedicated test rigs

  • X86/AMD64 hardware: Back up everything. Create a full disk image, verify your recovery media, then upgrade. You’ll benefit from the fixes, but be ready to roll back if you hit a 0xC1900101 error.
  • Arm64 hardware: Skip this build. Unless you are specifically triaging the kernel bug for Microsoft and can afford data loss, stay on your current build until a fix is announced.
  • Developers using PIX or GPU capture tools: Hold off or maintain a separate, non‑Canary machine for analysis. The playback incompatibilities can sabotage debugging sessions.

Troubleshooting checklist

  1. Record the exact rollback error code from Settings → Update & Security → Windows Update → Update history and locate setuperr.log in $Windows.~BT\Sources\Panther.
  2. Boot into Safe Mode and remove recently installed graphics, storage, or security drivers.
  3. If the device does not start, use your pre‑created system image or Windows installation USB to recover the previous build.
  4. For Arm64 kernel crashes, collect memory dumps (C:\Windows\MEMORY.DMP and C:\Windows\Minidump) and attach them to Feedback Hub reports. Do not run long‑duration tasks until a fix lands.

Final verdict

Build 27943 is a tightly focused servicing update that delivers meaningful relief to Insiders who have been grappling with a frozen storage scanner and an HDR toggle that refused to stick. The event log cleanup and small input fixes, while minor in isolation, add to a more polished feel. However, the two remaining known issues—installation rollbacks and Arm64 kernel crashes—cast a long shadow that makes the build unsuitable for anything beyond sacrificial test hardware.

Microsoft’s multi‑channel strategy is working as designed. Canary absorbs the initial shock of regressions so that Dev, Beta, and Release Preview channels receive fewer surprises. For most Windows fans, the real news this week is the Release Preview drops that bring practical fixes to Windows 11 and Windows 10 without the peril. The advice remains unchanged: match your operating system channel to your tolerance for risk, and never enter the Canary lab without a backup.