Microsoft shipped a redesigned Feedback Hub to Windows Insiders on March 20, 2026, splitting the app into two distinct feedback surfaces: a new compact “small” form for rapid submissions and the existing full-featured form for detailed reports. The change, first detailed in an official Windows Insider blog post, aims to make bug reporting less disruptive during the delicate moment of reproducing an issue.
A two‑surface Feedback Hub
The update, delivered automatically through the Microsoft Store for users on Dev and Beta channels, does not replace the classic Feedback Hub. Instead, it adds a lightweight feedback capture layer that can be invoked directly from the Windows desktop or within the Hub itself. The new “small surface” is a floating, minimal window designed to capture the absolute essentials while the rest of the system remains visible. The traditional full feedback form – now called the “full surface” – remains available for advanced diagnostics, screenshots, logs, and longer descriptions.
Microsoft’s advisory breaks down the two modes this way:
- Small surface: A compact overlay with fields for feedback category (Problem or Suggestion), a one‑line title, a multi‑line reproduction steps box, and a priority toggle (High/Medium/Low). It also automatically attaches a screenshot of the active window and a brief telematic slice – no manual attachment uploads. Submitting from this surface creates a basic feedback item that can later be enriched with the full surface.
- Full surface: The familiar multi‑tab form with detailed category drill‑downs (e.g., “Devices and Drivers” → “Print”), a rich text problem description, file attachments, trace logs, and the optional “Recreate my problem” recording tool. It can be opened fresh from the Hub or launched from the small surface’s “Add details” button.
Both surfaces share the same backend, so whether an item starts small or full, it ends up in the same queue for engineering teams. The routing logic has not changed, but Microsoft now internally tags items that originated from the small surface as “rapid‑capture” to help triage them faster.
What the redesign means for you
For everyday Windows Insiders
If you’re an enthusiast who likes to contribute feedback but often hesitates because the old form felt like filing a tax return, the small surface is a game‑changer. When you encounter a glitch – say, a Start menu tile that flickers – you can press Win + F (which now defaults to the small surface on supported builds), type “Start tile flickers”, paste your reproduction steps from memory, and submit in under 30 seconds. The form stays on top, so you don’t lose sight of the bug. Later, if Microsoft asks for more details, you can open the item in the full surface and add logs.
Key workflow for home users:
1. Trigger the small surface with Win + F.
2. Fill in the title and steps. Leave priority at the default unless it’s a showstopper.
3. Submit. Done.
4. If prompted later, search for the item in the Hub’s “My Feedback” section and expand it.
For IT admins and power users
Admins who run Insider builds in test fleets should treat the redesign as a routing optimization. The small surface is ideal for capturing clean, immediate repros during acceptance testing. For example, when a line‑of‑business app crashes after a cumulative update, instead of halting testing to write a lengthy report, a tester can fire off a quick item with the exact steps and the auto‑attached window screenshot. That rapid‑capture tag helps Microsoft’s automation correlate the issue with recent telemetry spikes, potentially leading to a faster fix.
Best practices for admin‑managed feedback:
| Scenario | Which Surface to Use | Why |
|---|---|---|
| Reproducible crash or hang during routine testing | Small surface | Speed matters; the telematic snapshot and window screenshot often suffice for initial triage. |
| Intermittent issue that requires logs or video | Full surface | Use the built‑in recorder to capture the behavior over time; attach relevant event logs. |
| Feature suggestion with mockups | Full surface | The rich text editor and file attachments let you embed wireframes or references. |
| Following up on an existing feedback item | Full surface | You can link to the original item and add diagnostic traces. |
| Training new testers | Small surface first | Reducing friction increases the number of actionable reports. |
Additionally, Group Policy and MDM controls for Feedback Hub behavior remain unchanged. The “AllowTelemetry” and “AllowFeedback” policies still govern whether the surfaces appear, and the default invocation key (Win + F) can be redirected or disabled via the Settings app under Privacy & security > Feedback & diagnostics. Microsoft has not introduced a policy to force one surface over the other; the choice is always user‑facing.
For developers
Devs who build on Windows and maintain feedback pipelines may notice a shift in the types of items flowing into their dashboards. Rapid‑capture items tend to be shorter but more numerous. Microsoft has already updated the Feedback Hub API to surface the surfaceOrigin property so third‑party analytical tools can distinguish small‑surface submissions. If you run a telemetry‑driven dev shop, consider weighting or filtering these items differently – they often lack deep context but excel at pinpointing the exact moment of failure.
How we got here
The Feedback Hub has been a cornerstone of the Windows Insider Program since 2016, but it has long drawn criticism for its complexity. A 2024 Windows Central survey found that 42% of Insiders avoided filing bugs because the form “took too long to fill out.” Microsoft’s own telemetry showed that the median time to submit a feedback item was 4 minutes 20 seconds – an eternity when a bug appears fleetingly.
Redesign efforts began subtly in late 2025 with A/B tests that shortened the form by collapsing advanced options behind a “More details” link. Those tests increased submission rates by 18% but also saw a rise in low‑quality reports. The two‑surface approach tries to strike a balance: make it dead‑simple to capture the basics, but keep the depth available for those who need it. The March 2026 rollout is the first broad deployment of this vision, landing first in the Dev channel before heading to Beta.
This iteration also aligns with the broader “simplified Windows” design language seen in the 24H2 update, where Settings and File Explorer were stripped of legacy dialogs. The small surface’s clean, acrylic‑backed UI closely mirrors the Windows 11 design principles – rounded corners, a caption bar that blends with the content, and a dismissable toolbar.
What to do now
Insiders on Dev/Beta channels: Update the Feedback Hub from the Microsoft Store to version 1.2503.18055.0 or higher. The new surfaces roll out gradually via a cloud‑controlled feature ramp, so you may need to wait a few days after the update before seeing the change. You can force‑check by running feedback-hub://smallsurface in the Run dialog – if the small surface appears, you’re on the new path.
Enterprise testers: Push the updated Feedback Hub package to your Insider ring machines and inform your testing team of the new workflow. Create a quick reference card showing the two surfaces and when to use each, based on the table above. If you use the Feedback Hub’s “Duplicate Finder” tool, note that rapid‑capture items sometimes duplicate because users don’t search thoroughly; encourage a quick search before hitting submit, even on the small form.
All users: The old Win + F shortcut now launches the small surface by default. If you prefer the classic full form, you can change this behavior in Feedback Hub settings (gear icon) under “Feedback launch preference” – choose “Full feedback form.” Conversely, if you’ve ever felt the traditional form was overkill, give the small surface a try; it’s a one‑click setting to revert.
Outlook
Microsoft has not announced a timeline for bringing the redesign to the Windows 11 stable channel, but based on past feature releases, a full rollout likely coincides with the 25H2 feature update in the second half of 2026. Between now and then, expect refinements: more telemetry‑slice options for the small surface, the ability to attach a video clip without leaving the compact UI, and deeper integration with the Problem Steps Recorder.
For IT admins, the key signal to watch is an update to the Windows Insider for Business documentation. Once Microsoft publishes an official deployment guide, it will signal that the redesign is ready for broader enterprise validation. In the meantime, treat the two surfaces not as competing tools but as complementary weapons in the fight against bugs – one for quick first strikes, the other for surgical follow‑ups.