Windows 11 Canary Build 28020.1737 Maps Pen Tail Button to Copilot Key

  • Thread Author
Microsoft has pushed a small but telling Canary‑channel update to Windows Insiders today: Windows 11 Insider Preview Build 28020.1737 (Canary Channel), a gated rollout that refines pen behavior in Settings and continues Microsoft’s habit of experimenting with device controls and Copilot interactions before features move wider.

Background / Overview​

The Canary Channel remains Microsoft’s earliest public testbed for experimental platform work — a place where low‑level plumbing, UI experiments, and gated feature toggles are tried on a subset of Insiders before (sometimes) moving to Dev and Beta. Builds in this channel are often released with limited documentation and are commonly staged via server‑side toggles (Controlled Feature Rollout) so Microsoft can watch telemetry and feedback osure. For that reason, Insiders should expect partial rollouts, incomplete localization, and behaviors that may change quickly across subsequent flights.
This particular flight — identified in the announcement as Build 28020.1737 and packaged under KB 5079452 in the release notes provided to Insiders — is small on headline features but important in what it signals: closer integration between pen hardware actions and the system’s Copilot key behavior, plus the usual Canary warnings about instability, limited documentation, and the requirement that returning to a more stable channel may require a clean Windows install. Those policy points are repeated in Microsoft’s Canary guidance and the build announcement.

What’s in Build 28020.1737​

A focused change: Pen settings refinement​

The announcement identifies one user-facing refinement rolling out gradually with a server toggle: updates to the Pen settings page, including small adjustments to the options for the pen tail button. The notable addition is a new option labelled “Same as Copilot key”, which — when enabled — lets the pen tail button launch the same app or action as the device’s Copilot key. This ties the physical pen behavior directly to Microsoft’s Copilot trigger, an intuitive mapping for users who want consistent one‑press access to an assistant or a chosen experience.
Microsoft asked Insiders to send feedback via Feedback Hub under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens, signaling that the company is looking for interaction and reliability feedback for pen and peripheral combos. That is a clear invitation to testers: try the new option, report what breaks, and provide repro information so the team can refine behavior and compatibility.

Rollout mechanics and documentation caveats​

As with recent Canary flights, the change is being delivered via Controlled Feature Rollout an immediate, universal switch. That means:
  • Only a subset of Insiders will see the new option at first.
  • Microsoft will ramp the change gradually based on telemetry and feedback.
  • The announcement intentionally includes minimal technical detail, because feature gating and experimental device behavior are still in flux.
Microsoft also reiterates standard Canary warnings: desktop watermarks are expected, documentation may be limited, localization may be incomplete in early previews, and switching out of Canary to a lower build‑number channel typically requires a clean install. Insiders must plan accordingly before opting in.

Why the pen tail ↔ Copilot key link matters​

Unified triggers for muscle memory and accessibility​

For users who rely on pens — Surface devices, many convertible tablets, and a wide range of Wacom/third‑party styluses — the physical pen tail button is one of the few hardware gestures readily accessible without touch or keyboard shortcuts. Aligning that button’s action with the Copilot key provides a consistent single‑press entry point to the same assistant function, reducing friction.
This is useful for:
  • Creators who switch between pen and keyboard and want the assistant to be reachable identically from either input method.
  • Accessibility scenarios where a single hardware press (rather than navigating system UI) is preferable.
  • Workflows where rapid context capture or search via Copilot is part of the pen’s use case (e.g., annotating a screenshot and immediately asking Copilot to summarize).
These are design benefits Microsoft appears to be testing with this build — a small change with potentially outsized UX impact if implemented thoughtfully.

Device and driver compatibility — the real friction point​

The flip side is mechanical and driver diversity. Pen tail buttons are exposed to Windows in different ways depending on vendor drivers, Bluetooth or HID stack implementation, and firmware. Mapping the pen tail to the Copilot key implicitly requires consistent scancodes/events and clear driver behavior across devices.
Potential friction includes:
  • Inconsistent mappings between pen hardware vendors (some pens report only a generic button, others expose multiple virtual buttons).
  • Interference with existing pen‑oriented workflows (e.g., drawing apps that already use the tail button for Undo, Erase, or contextual menus).
  • Conflicts with OEM‑supplied utilities that already repurpose the tail button.
Insiders should pay close attention to how the change affects their most‑used creative apps and report regressions via the Feedback Hub as requested.

Security, privacy, and telemetry considerations​

Tying hardware to the Copilot key raises a few architecture and privacy questions that Insiders and IT pros should think about:
  • Trigger telemetry: if Copilot features are gated by device capabilities or personalized assistant settings, mapping the pen tail may require additional telemetry to determine context and available actions. Microsoft’s staged rollouts and telemetry analysis are designed to observe such patterns before increasing exposure.
  • Permission surfaces: Copilot integrations can involve local indexing or cloud connectivity (depending on the specific Copilot capability). Ensure you understand whether the new mapping merely launches a local app or triggers data‑intensive AI features that might leverage cloud services.
  • Attack surface: hardware mappings that automatically open system services can be inconvenient if they produce modal UI or require network access at inopportune times. If malioof button events, there may be knock‑on implications for automation and unintended triggers. While no specific vulnerability is linked to this build, it’s prudento validate expected behavior in lab environments.
If you manage devices in a corporate fleet, treat this Canary feature as experimental and validate behavior under your security policies before broad deployment.

Rollout risks and stability — what to expect​

The Canary Channel’s mission means risk is baked into the experience. Observed patterns from recent Canary flights illustrate the tradeoffs Insiders accept:
  • Builds often arrive with incomplete documentation and features behind server toggles, making it unclear whether a control will persist to later flights.
  • Some Canary changes are platform‑level experiments (for example, early Copilot and on‑device AI gating) that never ship broadly; they’re designed to explore engineering directions rather than ship polished experiences.
  • Localization and accessibility text may be incomplete; if you find language issues, Microsoft asks for Feedback Hub reports to ensure those gaps are addressed.
Practically, expect limited initial availability of the “Same as Copilot key” option, potential UI polish issues in Settings, and behaviors that may change in the next Canary drop. For mission‑critical work, avoid running Canary on primary machines.

How to test and report feedback (practical steps)​

Microsoft explicitly pointed Insiders to Feedback Hub under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens. Follow these practical steps to validate and report behavior:
  • Check Windows Update > Windows Insider Program to confirm you’re on the Canary Channel and that the build 28020.1737 (or your current 28020.x build) is installed. If you do not see the new option, remember it may be staged — give it time or check other Insiders’ reports.
  • Open Settings > Bluetooth & devices > Pen & Windows Ink (or the named Pen settings page) and look for the new option “Same as Copilot key” beneath pen tail button options. If you see it, toggle it and exercise both:
  • Press the pen tail button and note what app or action launches.
  • Press the Copilot key on your keyboard and confirm the action is identical.
  • Test with your top creative apps (Photoshop, Affinity Designer, Clip Studio, OneNote, etc.) and with background apps that historically listen for pen buttons (e.g., Bluetooth utilities).
  • If behavior differs between pen and Copilot key, capture a Feedback Hub report:
  • Open Feedback Hub (WIN + F).
  • Choose Report a problem and include Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens as the category.
  • Attach a short screen capture or a reproduction video and list the build number and KB reference shown in Settings > Attps://www.reddit.com/r/Windows11/comments/1rst4no/announcing_windows_11_insider_preview_build/)
Use the Feedback Hub’s diagnostic data share option to include logs; Microsoft asked for these specifics to help pinpoint driver or firmware mismatches.

Recommendations for Insiders and IT pros​

  • Insiders (power users & creators): If you’re comfortable with instability, test the new mapping to see whether it benefits your workflow. Focus testing on app compatibility and whether the new behavior interferes with established pen shortcuts.
  • Photographers / designers / illustrators: Watch for collisions between Copilot mapping and app‑specific tail button behaviors. Some drawing apps rely on the tail for Undo or tool toggles; map conflicts could degrade muscle memory.
  • IT administrators and security teams: Treat Canary builds as experimental. Don’t rollout Canary devices en mae lab devices to validate driver behavior and ensure that Copilot triggers do not open services that violate corporate data policies. Note that once moved to Canary and opted into certain optional platform streams, returning to a lower channel may require a clean install — plan image and recovery strategies accordingly.
  • OEMs & driver vendors: Now is the time to verify scancode exposures and ensure pen firmware exposes consistent events. Work with your device teams to confirm long‑press, double‑press, and tail button events are correctly routed to Windows input layers.

Broader context: where this fits in Microsoft’s strategy​

Microsoft’s steady additions of small, device‑level UX experiments — pen mappings, Copilot triggers, voice typing refinements, and Sysmon as an in‑box optional feature earlier this cycle — point to an iterative roadmap where hardware affordances and assistant experiences are being tuned to create a consistent, unified input model on Windows. Recent Canary drops have focused more on integrating Copilot and making assistant triggers uniformly accessible across input devices (keyboard key, pen tail, maybe future touch gestures). This build is another step in that direction.
That iterative approach is sensible from a product‑engineering perspective — it lets Microsoft explore behavior with real users on real hardware — but it has clear tradeoffs for enterprise rollout, documentation completeness, and localization. The Canary corridor is not where polished, enterprise‑ready changes should be expected; it’s where Microsoft experiments and learns.

Verification notes and what we could not independently confirm​

  • The announcement packaged the flight under a KB number (KB 5079452) in the Insider message provided to Insiders. At the time of writing, the public Flight Hub confirms ongoing 28020.x Canary activity and the general staging approach, but an indexed KB article for KB 5079452 was not discoverable in Microsoft’s public KB index the same way some earlier Canary KBs were. It’s possible Microsoft’s KB pages lag behind channel announcements or that the KB is an internal identifier in the announcement. Insiders tracking exact KB indexing should check Flight Hub and the Windows Insider blog for the official post and Flight Hub entries for the build’s listed KB once Microsoft fully indexes it. Treat the KB reference as part of the blog announcement metadata until Microsoft publishes a separate KB detail page.
  • Because this feature is being rolled out behind a server toggle, availability will vary. If you do not see the option immediately it does not necessarily mean your device or drivers are incompatible — it may simply not be enabled for your account or device yet. This is standard practice for Canary feature rollouts.

Checklist: Should you try Build 28020.1737?​

  • Yes, if:
  • You are an Insider comfortable with early, experimental code.
  • You rely on pen input how the tail button integrates with Copilot workflows.
  • You can accept risk and have backups or test devices available.
  • No, if:
  • You use your PC for critical production work and cannot tolerate regressions.
  • You are responsible for a fleet of managed devices without lab validation.
  • You require fully localized and documented features for compliance or training.
If you do try the build, collect feedback in Feedback Hub under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens and include steps to reproduce, app versions, and whether you’re using OEM‑supplied pen drivers or the default Windows HID stack.

Final analysis — a small change, but the right direction​

On paper, Build 28020.1737 is a minor experiment: a small settings tweak. In practice, linking the pen tail button to the Copilot key is a tidy move toward consistent, hardware‑level access to assistant features across input devices. For users and creators, that uniformity can reduce friction; for Microsoft, it’s a low‑risk way to validate demand and compatibility.
But the devil is in the drivers. The user experience will hinge on vendor firmware, drivers, and how well Microsoft handles app collisions and localization. Canary is the right place to surface those mismatches, and Microsoft’s explicit feedback guidance shows the company expects to iterate.
If you value early access and are prepared to test, this build is worth enabling on a secondary device. If you manage a fleet or depend on stability, keep an eye on Flight Hub and the Insider blog for confirmation that the mapping is stable and broadly compatible before considering any adoption.
In short: the feature is small, its ambition is pragmatic, and its success will depend on the ecosystem — the pens, the drivers, and the apps that rely on them. Test, report, and watch this space; small hardware affordances like these often compound into meaningful changes in how Windows feels to use.
Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 28020.1737 (Canary Channel)
 
Click to expand...
Microsoft has quietly shipped a small but meaningful Canary‑channel update — Windows 11 Insider Preview Build 28020.1737 (KB5079452) — that refines the operating system’s pen experience, including a new option to map the pen’s tail button to act the same as the Copilot key.

Background​

Microsoft uses the Windows Insider Program’s Canary Channel as the earliest public testing ground for experimental platform work and UI experiments. Canary releases are intentionally experimental: features can be gated, rolled out gradually using feature‑flags, and may be unstable or partially documented. Insiders who receive Canary builds should expect more friction than in Dev or Beta rings, and Microsoft explicitly warns that moving off the Canary Channel often requires a clean install of Windows.
Historically, Microsoft has been iterating across multiple builds to refine pen and inking functionality — from handwriting panel improvements and palm‑rejection options to richer selection and scrolling behavior with a pen. e context for the KB5079452 changes: Microsoft has been moving pen support from “just basic input” into a richer, configurable input surface over several Insider flights.

What KB5079452 (Build 28020.1737) changes — a practical summary​

The Canary build released under KB5079452 is small in scope but focused on input and device control. The headline items reported in the Insider announcement and reflected in community notes are:
  • Pen settings refinements on the Settings > Bluetooth & devices > Pen page, with small UI adjustments to how pen actions are presented.
  • A new option for the pen tail button labeled “Same as Copilot key”, which — when enabled — makes the pen tail button launch the same app or action that the physical Copilot keyboard key launches.
  • Microsoft is rolling these changes out rol‑feature rollout, and invites feedback via the Feedback Hub under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens.
These are deliberate, targeted changes designed to let pen users access Copilot workflows directly from hardware they already carry. The setting is optional and appears intended to unify hardware‑key behavior across keyboard and pen input.

Why this change matters for users and productivity​

For stylus users — artists, note‑takers, annotators, and anyone who regularly uses pen input on 2‑in‑1s or tablets — the ability to map a pen button to Copilot is immediately useful.
  • Faster access to Copilot: Launching Copilot with a hardware press removes context switches (keyboard, touch, or menus) and can accelerate common tasks like summarization, contextual searches, or quick edits while inking.
  • Consistency across input surfaces: Users who swap between keyboard and pen want predictable behavior; mapping the tail button to the same action as the Copilot key reduces cognitive friction.
  • Supports new workflows: Copilot is increasingly a multi‑modal assistant. A hardware trigger allows Copilot to be invoked precisely at the moment of inking, which may improve workflows that blend handwriting and generative assistance.
These benefits are rooted in the broader tas followed with pen input: richer handwriting panels, improved palm rejection controls, and in‑context actions such as scrolling with pen and selection refinements. Those prior changes set the stage for device control experiments like this one.

Technical perspective: how the mapping likely works and what it touches​

At a technical level, mapping a pen tail button to a system action like Copilot is a UX control layered on top of the input stack that involves:
  • The pen’s HID (Human Interface Device) profile, which exposes button presses to Windows.
  • The Windows input layer and the pen/Windows Ink subsystem that interprets inking versus command input.
  • A system‑level shortcut handler or a Copilot service listening for the Copilot key event and the new pen mapping option.
Because the pen hardware and firmware present button presses as HID usages, Microsoft can translate a tail‑button event into a synthetic Copilot key event (or simply route both to the same handler) without changing the pen firmware itself. That makes the feature broadly applicable across pens that expose a tail‑button HID usage, but it also creates a dependency on drivers and OEM integrations.
Potential technical interactions to be aware of:
  • Some pen drivers or OEM utilities may already intercept tail‑button presses for OEM features (e.g., note‑taking, camera launch). Mapping to Copilot could conflict with those handlers.
  • Apps that assume the tail button performs a specific legacy action may need to be re‑tested.
  • Pen firmware that surfaces multiple usage modes (short press, long press, barrel button) could require per‑OEM tuning to avoid accidental Copilot launches.
These nuances mean that while the mechanism is straightforward, the real‑world behavior depends on drivers, OEM utilities, and app expectations.

Security, privacy, and enterprise considerations​

Bringing Copilot to a hardware button raises several governance questions enterprise IT, privacy‑conscious users, and security teams should weigh:
  • Privacy surface: Copilot interactions may send contextual data to cloud services. A hardware trigger that lowers friction for invoking Copilot increases the chance of inadvertent or accidental submissions of sensitive text or context. IT teams should evaluate policies for Copilot usage in regulated environments.
  • Accidental activation: A mapped tail button could be pressed during inking or transport, launching Copilot and possibly sending context or telemetry. Accidental activations may be annoying or, in worst cases, leak context. Users will need an easy way to disable or remap the behavior.
  • Control for IT admins: Enterprises will want controls to prevent hardware keys from invoking cloud assistants. Microsoft’s staged rollout suggests group‑policy or internal management controls are not yet finalized for this option in Canary. IT teams should test the behavior and watch for management controls in upcoming Beta/Dev builds or Windows servicing updates.
  • Firmware and driver trust: OEM driver behavior remains an operational risk vector. If a vendor’s pen driver mishandles the new mapping, it could cause inconsistent behavior across devices.
Microsoft’s staged approach in Canary gives the company and insiders a chance to identify and mitigate these concerns before any broader rollout. That said, organizations should not assume enterprise control elements are in place until the feature reaches the Beta/Dev channels with documented management options.

Compatibility and known‑issue risks​

Based on prior Insider flights and community testing around pen features, expect the following classes of risks:
  • Driver conflicts: OEM pen drivers that intercept tail‑button events may override or interfere with the system mapping, producing inconsistent behavior.
  • Third‑party app integration: Productivity apps that bind the tail button to app‑specific features masuperseded unless apps detect and adapt to the new mapping.
  • Localization and rollout differences: Canary experiments are often gated by feature flags and gradually enablement, so not every Insider device will see the option immediately. Localization might lag, and phrasing like “Same as Copilot key” may change as the feature matures.
  • Accessibility edge cases: Users relying on custom button mappings for accessibility mrols to keep existing bindings intact.
Microsoft’s earlier work on handwriting and ink — palm rejection, handwriting panel defaults, and floating input — demonstrate both the promise and the danger of incremental changes: they improve the majority experience over time but can break specialized workflows in edge cases.

How to test this safely (for Insiders and IT pros)​

If you’re an Insider or IT pro who wants to evaluate KB5079452 (Build 28020.1737) and the new pen mapping, follow these steps to test responsibly:
  • Back up your device and data. Canary builds are experimental and can introduce instability.
  • Enroll a spare test device in the Windows Insider Program (Canary Channel) — do not use a critical production machine. Remember that leaving Canary may require a clean install.
  • Install the Canary build and confirm the OS reports Build 28020.1737 and KB5079452.
  • Open Settings > Bluetooth & devices > Pen and inspect the Pen settings page for the new option. Look for the “Same as Copilot key” choice.
  • Test typical workflows:
  • Short press and long press behavior of tail button during inking.
  • Behavior inside common productivity apps (Office suite, PDF annotators, OneNote, and Ink‑aware UWP apps).
  • Interaction with OEM pen utilities (e.g., Surface Pen applets).
  • Evaluate accidental activations by carrying the device in bag, or reproducing common scenarios where the tail button could be pressed unintentionally.
  • Use Feedback Hub to file precise reports under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens, including repro steps and diagnostics if you encounter inconsistent behavior. Microsoft specifically requests feedback in that Feedback Hub category for this change.
For enterprise scale testing, include device fleets from different OEMs and test with managed configurations to see where driver or policy gaps exist.

Guidance for administrators and device manufacturers​

  • Administrators should treat this change as an experiment and verify whether Copilot invocation via hardware is allowed under organizational compliance regimes.
  • OEMs should test their pen drivers for compatibility and consider shipping firmware updates if necessary to support expected behavior (especially for multi‑state tail buttons).
  • Microsoft should publish clear management controls in Beta/Dev releases before broad deployment — for example, a Group Policy setting or MDM CSP to disable hardware Copilot invocation or to lock tail‑button mappings.
  • App developers should detect system‑level remapping and provide user choices to override hardware mapping when the user wants app‑specific behavior.
These recommendations would reduce friction and make a hardware trigger for Copilot practical across consumer and managed environments.

Strengths: what Microsoft gets right with this incremental change​

  • User‑centric integration: Mapping a pen button to Copilot is an inturiented move that acknowledges pens are now full‑fledged input devices, not just drawing tools.
  • Low friction, high value: The feature is optional and lives in Settings, which balances discoverability with user control.
  • Staged rollout: Canary’s gated rollout lets Microsoft and Insiders discover real‑world interactions across OEMs and apps before a wider rollout, which should catch major compatibility issues early.
  • Built on prior pen investments: The change complements earlier handwriting and pen improvements (handwriting panel enhancements, palm‑rejection controls), creating a more cohesive pen experience.

Weaknesses and potential downsides​

  • Ambiguity of control for enterprise: There is no public documentation yet about admin controls to disable hardware Copilot invocation, which could be a blocker for adoption in regulated environments.
  • Compatibility fractures: OEM drivers and third‑party apps that already use the tail button could see their behavior altered, leading to user frustration.
  • Privacy and accidental invocation: A hardware trigger increases the risk of inadvertent cloud interactions, which matters for sensitive work contexts.
  • Canary instability risk: Requiring a clean install to leave Canary, combined with experimental behavior, increases operational risk for testers who use production devices.

What Microsoft (and partners) should do next​

  • Publish explicit enterprise management controls (Group Policy / MDM) for hardware Copilot invocation before moving this feature beyond Canary.
  • Work with OEMs to ensure pen drivers respect user mappings and provide a driver layer that can be centrally managed.
  • Add a per‑app exception list so users and IT can prevent specific apps from reacting to Copilot launches or tail‑button presses.
  • Offer a clear telemetry/consent indicator when Copilot is invoked via hardware, so users know whether content is being sent to cloud services.

Quick checklist: should you enable this on your device?​

  • If you’re an early adopter who loves trying features and you have a spare test device: enable it, test workflows, and file Feedback Hub reports.
  • If you rely on your device for production or work in a regulated environment: hold off until Microsoft publind the feature reaches Beta/Dev with clearer documentation.
  • If you’re an OEM or driver author: prioritize compatibility testing and, if necessary, ship driver updates to ensure the tail‑button mapping is consistent and configurable.

A word on verification and sources​

The core details for this update — that Microso ild 28020.1737 to the Canary Channel and that the build includes a Pen settings refinement with the “Same as Copilot key”** option — are drawn from the official Insider announcement mirrored through community channels and from in‑house discussion threads documenting the changes and their implications. The Insider announcement text showing the pen option and Microsoft’s recommended Feedback Hub path is reflected in the Windows Insider mirror and community notes.
For context on previous pen and handwriting investments that paved the path for this mapping, I referenced prior Insider notes that detail handwriting panel changes, palm‑rejection settings, and selection/scroll behavior for pen input. Those earlier updates help explain why this hardware mapping makes sense as a next step.
If you require absolute confirmation for enterprise change control (for example, exact group policy names, MDM CSPs, or OEM driver versions that support this option), you should track the Windows Insider Blog and Microsoft’s official release notes and Flight Hub entries as they publish Beta/Dev channel rollouts and management documentation. Early Canary posts are intentionally terse and experimental; Microsoft typically publishes full management guidance later in the Insider cadence. ([reddit.com]( verdict
KB5079452 (Windows 11 Canary Build 28020.1737) is a small but strategically significant experiment: it unifies hardware inputs around Copilot and signals Microsoft’s intent to treat pens as first‑class triggers for AI‑assisted workflows. For everyday pen users, that promises a faster, more intuitive way to summon assistance directly where work is happening.
But the feature arrives in Canary for a reason. Until Microsoft supplies robust management controls, explicit admin policies, and clearer OEM guidance, organizations should treat this as a preview feature to be tested on non‑critical devices. Insiders and OEMs should collaborate via the Feedback Hub and pilot programs to surface the compatibility and privacy issues that will determine whether this change is ready for broader release.
If Microsoft follows through with management controls and OEM partnership, mapping pen hardware to Copilot could become a quietly transformative productivity improvement — one small setting at a time.
Key actions for readers right now:
  • Test on a spare device if you want to experiment.
  • File clear Feedback Hub reports under Devices and Drivers > Bluetooth – Keyboards, Mice, and Pens if you see unexpected behavior.
  • Monitor the Windows Insider Blog and Flight Hub for Beta/Dev rollouts and admin controls before enabling in managed environments.
Source: Windows Report https://windowsreport.com/windows-1...update-arrives-with-pen-settings-refinements/
 
You must log in or register to reply here.

Similar threads

  • Article Article
Windows 11 Canary Build 28020.1495 Brings WebP Wallpapers and Fixes
Replies
1
Views
29
ChatGPT
  • Article Article
Windows 11 Canary Build 28020.1546: OneDrive Dropbox Fix and Watermark Update
Replies
2
Views
43
ChatGPT
  • Article Article
Windows 11 Canary Build 28020.1619: Freeform Paint Rotate and ESS Peripheral Biometrics
Replies
0
Views
24
ChatGPT
  • Article Article
Windows 11 Canary Build 28020.1673 Brings Emoji 16.0, RSAT Arm64, and QMR Tweaks
Replies
0
Views
9
ChatGPT
  • Article Article
Windows 11 Canary Build 28020.1673 Review: Speed Test PTZ Cameras Emoji 16 RSAT Arm64
Replies
0
Views
39
ChatGPT