This guide walks you through reporting a Windows bug through the official Feedback Hub and, if you have a technical fix, submitting it as a reproducible patch. You’ll learn what information Microsoft needs, how to capture it, and how to make your report stand out so it actually gets looked at.
What You’ll Need
- A Windows 10 or Windows 11 PC with the Feedback Hub app (preinstalled, search for it in Start).
- Your Microsoft account (the one you use to sign in to Windows).
- For a code fix: a GitHub account, basic knowledge of C++ or C# (Windows components are mostly C++), and a development environment like Visual Studio with the Windows SDK.
- If you’re not a developer, you can still submit a detailed bug report with reproduction steps—that’s valuable too.
Step-by-Step
- Reproduce the bug reliably. Before reporting, make sure you can trigger the issue every time. Note the exact steps: what you clicked, what you typed, what window was open. If it’s intermittent, try to find a pattern (e.g., happens after sleep, only with a specific app).
- Open Feedback Hub. Press Win + F or search for “Feedback Hub” in Start. Sign in with your Microsoft account if prompted.
- Start a new feedback item. Click the “Feedback” tab (the smiley face icon) and then “+ New feedback”.
- Choose the right category. Pick the problem type that matches: “Problem” and then the relevant subcategory (e.g., “File, folder, and online storage” for Explorer issues). Be as specific as possible.
- Write a clear title. Summarize the bug in one sentence, e.g., “File Explorer crashes when renaming a file with a # in the name”. Avoid vague titles like “Windows broken”.
- Write a detailed description. Include:
- Exact steps to reproduce (numbered).
- What you expected to happen.
- What actually happened (including any error codes).
- Your Windows version (Win + R, type
winver) and build number. - Your hardware (CPU, GPU, RAM) if it might be relevant.
- Attach screenshots or recordings. Use the camera icon to add a screenshot. For a video, use the Xbox Game Bar (Win + G) to record a short clip showing the issue. Highlight the relevant parts with the built-in annotation tools.
- Add logs and traces. In the Feedback Hub, click “Add more details” and then “Create a new trace”. Reproduce the bug while the trace is recording, then stop it. This captures system logs that engineers can analyze.
- Submit the report. Click “Submit” and note the feedback ID that appears—you can use it to track the issue.
- If you have a code fix: Search for the bug in the Windows Developer Feedback on GitHub (github.com/microsoft/WindowsDevFeedback). If it exists, comment with your analysis. If not, you can’t directly submit a patch to Windows closed-source code, but you can:
- Create a detailed technical write-up on GitHub (repro steps, root cause analysis, proposed fix).
- Link it in your Feedback Hub report.
- If the bug is in a Windows component that is open source (like PowerShell or Windows Terminal), submit a pull request with your fix to the respective repository.
Common Mistakes
- Vague reports: “It doesn’t work” tells us nothing. Always include steps, expected vs. actual behavior, and a screenshot.
- Duplicate reports: Before submitting, search Feedback Hub for similar issues. Upvoting an existing report is more effective than creating a duplicate.
- Missing logs: Without a trace, engineers have to guess. Always attach a trace when possible.
- Ignoring the build number: Bugs are often fixed in newer builds. Test on the latest Windows Insider build before reporting.
- Submitting a fix without a repro: A patch without a clear reproduction case is unlikely to be accepted.
Tips
- Be specific about the environment: Mention if you’re on a VM, if you have third-party antivirus, or if you’ve made any registry tweaks.
- Use the “Similar feedback” feature: The Feedback Hub shows related reports—merge yours with the most relevant one.
- Keep it to one issue per report: Mixing two bugs makes it harder to track.
- If you’re a developer, provide a minimal repro: A tiny C# or C++ snippet that triggers the bug is worth a thousand words.
- Check the Windows Insider forums: Sometimes posting there gets faster responses from Microsoft engineers.
Troubleshooting
- Feedback Hub won’t open: Restart the app or run
wsreset.exeto clear the Store cache. If that fails, reinstall Feedback Hub via Settings > Apps. - Trace recording fails: Make sure you have enough free disk space. If it still fails, use the Windows Performance Recorder (WPR) from the Windows SDK to capture a trace manually, then attach the .etl file.
- You can’t sign in: Check your internet connection and make sure your Microsoft account is valid. Try signing in to the Store first.
- Your report gets closed as “Not reproducible”: Add more details, especially a video. If you can, test on a clean installation of Windows to rule out third-party interference.
- You don’t know how to write a fix: That’s okay—you can still report the bug. For open-source components, read the contribution guide first.
Frequently Asked Questions
Can I really submit a fix for Windows itself?
For closed-source Windows components, you can’t submit a pull request directly. But you can provide a detailed analysis and proposed fix that engineers can use. For open-source components (PowerShell, Terminal, etc.), yes—submit a PR.
How long does it take for Microsoft to respond?
There’s no guarantee. Some reports get responses in days, others never. High-quality reports with traces and clear repro steps are more likely to get attention.
Do I need to be on the Windows Insider program?
No, but it helps. Insiders get access to pre-release builds where bugs are more likely to be fixed before the public release.
What is a “trace” and why is it needed?
A trace is a recording of system events and calls. It lets engineers see exactly what happened when the bug occurred, which is essential for diagnosing complex issues.
Can I report a bug anonymously?
No, you need to sign in with a Microsoft account. But you can choose to share your email or not—Microsoft usually doesn’t contact you directly.
What if my bug is a security vulnerability?
Do not post details publicly. Report it privately via the Microsoft Security Response Center (MSRC) instead.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- Zelle Error A101: What It Means & How to Fix It