• Thread Author
Microsoft’s continued migration of legacy Control Panel features into the modern Settings app has taken another step forward: recent Windows 11 Insider preview builds contain hidden, in-progress pages that surface longstanding keyboard controls and a redesigned haptic touchpad panel inside Settings, signaling Microsoft’s steady push to consolidate device input controls into a single, discoverable interface across Windows 11’s Dev and Beta channels.

A futuristic holographic interface for input devices, displaying keyboard and touchpad settings.Background​

Microsoft began moving legacy Control Panel functionality into the Settings app as part of Windows 11’s long-running UX consolidation effort. That work accelerated with the 24H2 (2024 Update) cycle and has continued through preview builds tied to version 25H2 (Dev channel) and Beta-channel feature testing. Microsoft has repeatedly stated that many features in Insider builds are gated by feature-rollout toggles and A/B testing, meaning they will appear for subsets of Insiders before any broad release.
Over the last 12–18 months, Microsoft has moved multiple input-related controls—mouse scroll direction, touchpad gestures, and other device-specific options—out of the legacy Control Panel and into Settings, improving discoverability and aligning controls under device-centric pages. The recent Insider sightings extend that same pattern to keyboard character repeat controls and deeper haptic touchpad tuning.

What was discovered in the preview builds​

Keyboard character repeat controls arrive in Settings​

Insider observers and tipsters have reported that the classic character repeat delay and repeat rate controls—historically available only in Control Panel > Keyboard > Speed—now exist as Settings pages in recent preview builds. Screenshots shared on social platforms show slider controls and a live preview test box that lets users try different delay and repeat-rate values immediately. Some reporting notes place the new controls under Settings > Accessibility > Keyboard, while at least one outlet described them under Bluetooth & devices—a small but notable inconsistency across early reports.
Key facts gathered from preview-build coverage:
  • The controls mirror the legacy Control Panel options: repeat delay (how long a key must be held before repeated characters start) and repeat rate (how quickly repeated characters appear).
  • A live sample/test box has been included to show the immediate effect of adjustments.
  • Cursor blink-rate control appears not to have migrated in all builds; some reports still show it remaining in legacy menus for now.
These changes have appeared in Dev- and Beta-channel builds reported in the 26120–26200 build series, consistent with Microsoft’s ongoing 25H2 development and 24H2 back-port testing.

Redesigned haptic touchpad panel​

Alongside keyboard updates, Microsoft appears to be testing a refreshed touchpad settings page with more granular haptic controls. Early reports and platform documentation indicate:
  • Sensitivity options are being reworked; a slider in older UI builds is reportedly replaced by a dropdown in the preview.
  • Haptic clicks and haptic signals are exposed as separate controls—managed by individual sliders or toggles—giving users discrete control over click-detection thresholds and feedback intensity.
  • The Settings UI appears to match Microsoft’s broader touchpad parameter model (intensity, click-force sensitivity, zone sizes), which is reflected in Windows platform documentation describing ranges and registry-backed values for precision touchpads.
The presence of these controls in Settings suggests Microsoft is standardizing the UX for precision touchpads and expanding the built-in configuration surface previously provided by OEM utilities or buried device properties.

Why these changes matter​

Better discoverability and parity​

Moving keyboard and touchpad options into Settings benefits everyday users and IT administrators by:
  • Centralizing input device controls in the modern Settings UX, improving discoverability for non-technical users.
  • Reducing the need to rely on legacy Control Panel dialogs or registry hacks for common personalization tasks.
  • Aligning similar settings (mouse, touchpad, keyboard) in proximate Settings locations for consistent device management.
This parity reduces the number of support tickets and prevents risky registry edits previously used to change behaviors like scroll direction or repeat rates. Microsoft’s gradual migration has already delivered visible gains—mouse scrolling direction was added to Settings during the 24H2 cycle—serving as a precedent for keyboard and touchpad moves.

Finer hardware-level control for modern touchpads​

The updated haptic touchpad controls reflect modern hardware capabilities—especially for precision touchpads with integrated haptic actuators. Platform documentation specifies fields such as clickForceSensitivity and feedbackIntensity with 0–100 ranges, and Microsoft’s Touchpad Tuning guidance lays out recommended defaults and behavior. Exposing these values in Settings will let users adjust physical feedback without third-party drivers.

Accessibility benefits​

Keyboard repeat-rate and delay are accessibility-relevant controls that help users with motor differences and assistive technology setups. Making those controls more visible and easier to adjust through a live preview in Settings improves accessibility and discoverability—important wins from a usability and compliance perspective.

Contradictions and unresolved items — what remains unclear​

Not every early report lines up precisely, so a few points still need clarification before confident guidance can be given:
  • Where exactly the keyboard controls will live. Some coverage and tipster screenshots show the new options under Accessibility > Keyboard, while other outlets have reported them under Bluetooth & devices. This inconsistency likely reflects active UI experimentation and different feature-rollout branches within preview builds. Treat both locations as possible until Microsoft standardizes the page layout.
  • Cursor blink-rate migration status. Several reports note the blink-rate control has not been copied to Settings in the same builds that contain repeat-rate controls. That suggests Microsoft may be moving settings in stages rather than as a single batch.
  • Rollout timing and availability. These controls are hidden by default and gated behind Insider feature flags or toggles. Visibility can vary by channel, build number, and whether Microsoft is A/B testing the feature. There is no official public timetable for stable-channel rollout at this point.
When details differ across credible reports, flagging the divergence is important. The presence of multiple, independent sightings—by tipsters, platform docs, and established Windows outlets—points to a genuine work-in-progress, but precise UI placement and availability remain in flux.

Technical verification and what the platform docs say​

Microsoft platform documentation for touchpad parameters documents the same kinds of fields and ranges that are now appearing in Settings previews. The documentation lists values such as ClickForceSensitivity and FeedbackIntensity with valid ranges (0–100) and notes the user-facing UI should constrain options appropriately. That matches early screenshots showing sliders or dropdowns controlling intensity and haptic click detection.
Insider build release notes and community summaries for specific Dev/Beta builds (the 26120.xxxx and 26200.xxxx series) mention keyboard and input-related setting migrations, confirming the builds in which these UI changes were first observed. Those release notes also explain that various features are controlled by rollout toggles and may be visible only to subsets of Insiders.

How users and IT pros should approach these preview sightings​

For everyday Windows users​

  • Expect incremental changes: the presence of a hidden or behind-a-flag setting in an Insider build does not mean it will appear in stable Windows immediately.
  • If a new Settings control appears on your device, use it to tune behavior and verify your preferred settings in real-world use—especially for accessibility and touchpad feedback.
  • Avoid third-party registry hacks to force hidden UI elements to appear; these can destabilize your system or conflict with driver updates.

For Windows Insiders and power users​

  • Join the Windows Insider program if you want early access to these updates and can tolerate potential instability.
  • Install builds from Dev or Beta channels that correspond to the 26120 / 26200 build series where these changes were observed.
  • Expect A/B testing: use Feedback Hub to report layout issues, missing localization, or behavior inconsistencies so Microsoft can refine the UI.
  • Do not assume hidden UI presence equals final behavior—experiment in a controlled environment or VM if you must test extensively.

For IT administrators and enterprise teams​

  • Test management flows: confirm whether these settings will be controllable via Group Policy, MDM profiles, or AD-backed templates before rolling out to users.
  • Plan for driver conflicts: OEM utilities (e.g., Logitech Options, Synaptics/ELAN software, Microsoft Surface drivers) may still override system-level haptic behavior. Test combinations of vendor utilities and the new Settings controls in pilot groups.
  • Document fallback paths: until the Settings pages ship broadly, administrators should maintain references to legacy Control Panel locations and registry values for support or automation needs.

Potential benefits and risks​

Benefits​

  • Unified UX: Centralized Settings reduce friction and help non-technical users find controls previously hidden in Control Panel.
  • Accessibility improvements: Live-preview keyboard controls improve the experience for users with motor needs.
  • Native hardware tuning: Built-in haptic touchpad controls reduce dependency on OEM utilities and provide consistent options across devices.

Risks and downsides​

  • Driver and OEM utility conflicts: System-level Settings may be out-of-sync with vendor utilities, producing inconsistent behavior across apps and devices.
  • Fragmented rollout and discoverability: Hidden features or differing UI locations across builds can confuse users during preview testing.
  • Enterprise manageability concerns: If these controls are not surfaced in Group Policy or MDM, administrators could face challenges in enforcing organization-wide defaults.
  • Stability and regression exposure: Early releases in Dev channel can contain bugs; users who rely on precise input behavior (e.g., gamers, content creators, accessibility users) should be cautious about installing Dev builds on production machines.

How to verify whether your machine has the new settings​

Because Microsoft gates these features by channel and internal toggles:
  • Check your Insider channel and build number. Early sightings were tied to builds in the 26120–26200 series; verify your build number via Settings > System > About.
  • Look under two possible Settings areas where early reporting placed the controls: Settings > Accessibility > Keyboard and Settings > Bluetooth & devices (check both—UI experimentation means either is possible).
  • If you are an Insider and do not see the UI, the feature is likely still hidden behind a rollout toggle; file Feedback Hub reports if you want to capture telemetry or request broader exposure.
Note: intentionally enabling hidden features via third-party utilities (e.g., Vivetool) carries risk. Use caution and perform such actions only in test environments or virtual machines, and never on a critical production device.

Likely roadmap and timeframe​

Microsoft’s behavior in past cycles suggests the following pattern:
  • Migrate and test features in Dev and Beta channel builds (A/B tests, toggles).
  • Promote stable, well-tested features to broader Beta/Release Preview rings.
  • Ship completed migrations in a cumulative or feature update (24H2/25H2 cadence historically followed this path).
Given the presence of keyboard and touchpad pages in recent preview builds and the company’s prior movement of other input settings (mouse scrolling), these items are likely candidates for inclusion in an upcoming cumulative update or feature release—provided testing, localization, and compatibility checks complete successfully. However, there is no official public timetable; the visibility and final UX remain contingent on internal testing and user feedback.

Practical tips for power users and sysadmins​

  • Keep drivers up to date from OEMs (Surface, Synaptics, good-touchpad vendors) to ensure Settings-level controls and hardware-level firmware agree.
  • For organizations, establish a pilot ring for early builds and a rollback plan before broad deployment.
  • When testing, record baseline device behavior (repeat-rate, haptic intensity) so post-update comparisons clarify whether changes are Settings-driven or driver-driven.
  • Use Feedback Hub to report mismatches, localization gaps, or missing manageability controls—Insider feedback channels materially affect when and how Microsoft finalizes these transitions.

Conclusion​

The internal migration of legacy Control Panel controls into Windows 11’s Settings app continues to make steady progress with keyboard repeat-rate/delay controls and a more granular haptic touchpad pane appearing—albeit hidden and gated—in recent Insider preview builds. These changes should improve discoverability and accessibility while consolidating device input controls under the modern Settings UX. Platform documentation and multiple independent reports corroborate the technical direction, and Microsoft’s established shipping pattern suggests we’ll see wider availability once testing and manageability checks are complete. Until then, users, power consumers, and IT admins should watch preview builds carefully, validate driver interactions, and treat early sightings as previews rather than final shipping behavior.


Source: Windows Report Microsoft tests new keyboard and touchpad settings in latest Windows 11 preview builds
 

Windows 11’s next annual feature update has arrived more like a service patch than a showpiece: version 25H2 is an enablement package on top of the 24H2 servicing branch, it ships with no new headline consumer features at launch, and its most concrete changes are removals and manageability tweaks — an approach that is quietly practical for IT but oddly anticlimactic for the wider Windows audience.

A laptop on a wooden desk with a neon-glow label reading '25H2 Enablement Package.'Background / Overview​

Microsoft continues the servicing model it refined after Windows 10: new feature binaries are staged across monthly cumulative updates and then activated for a given yearly version with a tiny “enablement package” (eKB). For Windows 11, version 25H2 this means the files for most new functionality were already distributed during the 24H2 servicing year; the eKB simply flips feature flags to turn staged features on. The Windows Insider team made the Release Preview build (Build 26200.5074) available for validation, explicitly describing 25H2 as an enablement-package release rather than a full rebase.
That technical model carries two immediate consequences for organizations and enthusiasts:
  • Upgrading a fully patched 24H2 PC to 25H2 is typically fast and low-impact: the eKB is small and usually requires only a single restart.
  • The codebase for 24H2 and 25H2 is largely identical in binary terms, but the activation state — which features are enabled — is what differs. This makes month-to-month servicing identical across both versions and simplifies patching for Microsoft and IT teams.
But the second consequence creates a perception problem: when an annual version number increases without a large packaging of new features visible at first glance, public excitement naturally wanes. The 25H2 release highlights that tension: operationally tidy, publicly uninspiring.

What 25H2 actually contains: polish, removals, and manageability​

It’s mainly an enablement package​

The single clearest technical truth is that 25H2 is an enablement package. It activates features Microsoft already delivered across monthly cumulative updates to the 24H2 servicing branch. That’s explicitly documented in the Windows Insider announcement and confirmed by multiple community and technical summaries. The result is an upgrade experience that is closer to applying a monthly quality update than performing a full OS reimage.

Minimal consumer-facing additions at launch​

At the time Microsoft opened the Release Preview, 25H2 did not ship with new consumer-facing features exclusive to that version. Most visible changes are modest UI polish, accessibility improvements, and AI surfaces that were staged gradually during 24H2’s servicing cycle. In short: refinement rather than reinvention.

Notable removals and policy controls​

Rather than adding features, Microsoft used 25H2 as an opportunity to remove legacy components and introduce tighter enterprise controls:
  • PowerShell 2.0 engine removed from shipping images. The legacy PowerShell v2 runtime, deprecated for years, is no longer included by default in new images. Administrators must migrate any scripts or tools that explicitly depend on the v2 engine to supported runtimes (PowerShell 5.1 or PowerShell 7+). This removal is part of a long deprecation timeline and is intended to reduce legacy attack surface.
  • WMIC (Windows Management Instrumentation Command-line) removed for 25H2 installs. Microsoft’s support documentation confirms WMIC will be removed when upgrading to Windows 11, version 25H2; administrators should migrate WMIC-based automation to PowerShell WMI/CIM cmdlets or other programmatic interfaces. WMIC’s removal narrows the living-off-the-land tools that attackers have exploited.
  • New manageability controls for commercial customers. IT administrators in Enterprise and Education SKUs gain a Group Policy / MDM CSP that allows selective removal (or blocking of installation) of certain preinstalled Microsoft Store apps during provisioning — a useful hardening and compliance tool for managed environments.
These moves are pragmatic for enterprise security and manageability, but they create a short-term remediation burden for any customers still relying on legacy tooling.

Features that are coming — but already seeded to 24H2​

Microsoft’s messaging and public previews make clear that several user-facing improvements are in the pipeline and will appear across both 24H2 and 25H2 machines as staged features. Because these features were delivered as binaries earlier, they’re not exclusive to 25H2 when they roll out — they’re simply gated and enabled progressively.

A redesigned Start menu (more app-centric)​

After years of criticism, Microsoft has been testing a reworked Start menu that eliminates or minimizes the old “Recommended” feed and prioritizes a full app list that’s easier to scan. The new layout lets you:
  • See pinned apps and the entire app list on a single scrollable page.
  • Choose an All apps layout in grid, list, or a new category view that automatically groups apps by function (Productivity, Games, Creativity, etc.).
  • Hide the Recommended section entirely for a cleaner experience.
This redesign is being flighted in Insider builds and has been covered by multiple outlets reporting hands-on with the beta views. The category grouping is automatic and helpful for many users, but Microsoft currently does not let you create arbitrary, custom categories — grouping is inferred.

Better Windows experiences for handheld gaming PCs​

The rise of purpose-built Windows handhelds prompted Microsoft to optimize for handheld scenarios. The Xbox and Windows teams have collaborated with OEMs (notably ASUS for the ROG Xbox Ally and ROG Xbox Ally X) to deliver an Xbox full‑screen experience on Windows handhelds that:
  • Boots to a console-like full‑screen Xbox home rather than the standard Windows desktop.
  • Removes the taskbar/Start distractions and focuses resources on gameplay.
  • Provides a more console‑like “home” where Wi‑Fi, Bluetooth, and quick settings are accessible without returning to the desktop.
Microsoft’s Xbox Wire and Windows Experience Blog explain the handheld-first changes and the newly announced Handheld Compatibility Program that badges and optimizes games for handheld play. These features are specifically targeted at devices shipping this fall and will initially appear on the Ally devices, with broader rollouts to other handhelds over time.

Windows Studio Effects for external USB webcams on Copilot+ PCs​

One of the most welcome practical upgrades in preview builds is that Windows Studio Effects — the AI-powered camera features that provide eye contact, background blur, auto-framing, and more — are being extended to external cameras on supported Copilot+ PCs. Previously, Studio Effects required the built-in camera and an NPU on Copilot+ devices; Microsoft’s Insider notes and preview builds now expose a toggle in the Camera settings that lets you opt to “Use Windows Studio Effects” on a selected USB webcam or secondary camera. The rollout is staged (Intel Copilot+ PCs first, then AMD and Snapdragon), and not every external webcam will be supported immediately.

How this compares to what Apple shipped (and why that matters)​

Microsoft’s low‑drama release contrasts with Apple’s annual desktop update cycle this year. Apple’s macOS 26 “Tahoe” introduced a large, visible design language called Liquid Glass, with a system-wide visual refresh and other tangible UI shifts that are easy to spot and to sell to users who like visible change.
The difference is partly cultural: Apple’s annual updates often prioritize a cohesive consumer-facing narrative and visible aesthetic changes, while Microsoft is distributing functionality continuously and staging visible bits when they’re ready. That trade-off favors stability and shorter upgrade windows at scale — helpful for enterprises — but it reduces the “big splash” in the consumer news cycle. Multiple outlets covering macOS 26 described a clear visual hook; by contrast, 25H2’s hook is operational and incremental.

What IT teams and power users need to know (practical checklist)​

25H2 is small in consumer drama but can be operationally significant. The following checklist is practical for administrators and power users preparing pilots or rollouts.
  • Inventory scripts and management tools for WMIC and PowerShell v2 usage.
  • Search for "wmic" and explicit invocations of the v2 engine (e.g., powershell.exe -Version 2).
  • Replace WMIC calls with PowerShell CIM/WMI cmdlets such as Get-CimInstance or equivalent API calls.
  • Migrate any v2 PowerShell workflows.
  • Update automation to PowerShell 5.1 or PowerShell 7+, test compatibility, and remove hard-coded -Version 2 flags from installers or scheduled tasks. Microsoft guidance and community reporting recommend migrating proactively.
  • Validate dependent vendor agents.
  • Security agents, endpoint management tools, and monitoring agents sometimes hook into legacy binaries. Test agents post‑enablement on pilot devices before broad rollout.
  • Plan for selective app removal in managed images.
  • If you provision Enterprise/Education devices, consider using the new CSP / Group Policy option to remove selected Store apps during provisioning. This can shrink the attack surface and reduce local bloat.
  • Consider timing and media:
  • Microsoft initially signaled that ISOs would arrive quickly for lab validation but later delayed those ISOs. If your imaging pipeline requires canonical ISO media, check Microsoft’s update on ISO availability before scheduling large-scale validation. The ISO timing issue is operationally meaningful.

Migration steps: a recommended sequence (short and practical)​

  • Step 1: Run a script-search across images and repositories for "wmic" and "powershell.*-version 2".
  • Step 2: Build a compatibility matrix: scripts that run on 5.1/7+ without modification, scripts that need translation, and third-party installers that hard-call v2.
  • Step 3: Test sample converted scripts on a ringed pilot (10–50 devices) that mirror production.
  • Step 4: Use Windows Update for Business ringed deployment or WSUS to roll the enablement package in waves.
  • Step 5: Monitor telemetry and agent behavior for two monthly cumulative updates after enablement: subtle behavioral changes can surface in drivers or security hooks.
These steps minimize disruption while respecting the enablement-package model: the change is small, but feature activation can still alter runtime behavior.

Risks, edge cases, and things to watch​

  • Hidden behavioral changes. Because the eKB flips existing flags, some drivers, third-party tools, or security products might interact differently once features are active. Focus validation on runtime scenarios and agent interactions, not just file-level differences.
  • Legacy tooling breakage. Organizations that kept old installers or scripts tested against v2 or WMIC may find automation breakages. Rely on the migration checklist and consider temporary shims only as a stopgap.
  • Hardware gating for AI features. Many AI surfaces (Studio Effects, Copilot integrations) remain gated by hardware capability and licensing. Don’t expect uniform availability across a mixed fleet; Copilot+ branding and NPUs are often prerequisites.
  • Staged rollouts create uncertainty. Because features are staged and may be enabled per-device or per-tenant, the same OS version can show different behaviors across devices; this complicates help-desk triage and user support. Track which devices have feature flags enabled during pilots.
  • ISO availability may lag. If your lifecycle relies on ISOs for imaging, the delayed ISOs can be a planning friction point; test via Release Preview where safe, but prefer canonical media for final validation.

Why a “boring” update can be an honest win​

Calling 25H2 “boring” isn’t merely pejorative — it’s descriptive. Microsoft deliberately prioritized manageability, security hardening, and an operationally efficient delivery model over headline consumer features. For some constituencies that is a win:
  • Enterprises get a fast, low-impact upgrade path and better controls to lock down preinstalled apps.
  • Security teams benefit from the removal of old runtimes and living-off-the-land tools that have historically been exploited.
  • IT operations get uniform monthly servicing and less friction in large-scale patching.
But that trade-off also flattens the narrative arc of Windows’ big annual update — there’s no single “wow” feature to rally users around at launch. Instead, the story is one of cumulative improvements and staged AI surfaces that will gradually make the platform better over time.

Final assessment: pragmatic, but uneven for different audiences​

Windows 11, version 25H2 is, at its heart, a pragmatic release: an enablement package that tidies up legacy components, tightens manageability for commercial customers, and continues Microsoft’s rolling delivery of AI and quality improvements. For IT teams and cautious organizations that prioritize stability and minimal downtime, that’s good news. For the enthusiast or consumer looking for a big visual refresh or a stack of new flagship features, 25H2 will feel intentionally mild.
The notable exceptions — a cleaner Start menu, the Xbox full-screen handheld experience, and the extension of Windows Studio Effects to external webcams on Copilot+ PCs — illustrate Microsoft’s longer-term attention to usability and form-factor diversity. Those features, however, were already staged into 24H2’s servicing stream and will be rolled out by gating rather than by version number exclusivity.
In short: Windows 11 25H2 is the kind of release that rewards close reading and good change management rather than headline-driven excitement. Administrators should treat it as an important operational milestone — one that demands migration work in a few narrow areas (PowerShell v2 and WMIC) but otherwise eases the upgrade path for fleets kept current with monthly patches. End users will likely notice incremental polish and, over the months ahead, the staged rollout of the larger AI and UX investments Microsoft has been quietly integrating into the servicing stream.

Conclusion
Windows 11 version 25H2 demonstrates a clear intent: deliver modern capabilities without larger rebase pain, reduce legacy attack surface, and give IT sharper controls — all while continuing to roll out new features on its own cadence. That approach is technically sound and operationally helpful, but it also reshapes what “annual updates” mean for Windows: the calendar year number is increasingly a marker of servicing state and support timelines rather than a guaranteed package of new consumer-facing features. For administrators, this is an invitation to plan and migrate now; for enthusiasts, it’s a reminder that the most interesting work on Windows in 2025 may be happening in preview channels and incremental rollouts rather than in one annual reveal.

Source: XDA Developers Windows 11 version 25H2 is almost here — and it's so boring it almost becomes interesting
 

Back
Top