Filing USB feedback with Repro Mode in Windows 10


Authored by Mike Ma [MSFT] & Michelle Vogel [MSFT]

Feedback from users is one of the many ways the USB team identifies and prioritizes issues and fixes. However, not all feedback is actionable; many times, we need detailed logs to understand what is causing and issue and sometimes which component the issue is even in. For example, you might have a USB keyboard that is not working, to fix the issue our team first needs to determine if the issue is the USB Controller, the device, the HID layer, or even in an intermediate hub. Gathering all the logs to investigate an issue can a bit painful, so we have worked to make it easy to use the capabilities of the Windows Feedback Hub application to provide the most actionable feedback as possible.

This blog post details the resources available to end-users in providing the most actionable feedback to the USB team under Windows 10. A key requirement to filing actionable USB feedback is to use the Monitoring feature in the Windows Feedback Hub application. Monitoring mode allows us to configure a rich set of custom log collection to help root root-cause USB issues. At the time of this writing, USB host logs can be captured on either Desktop or Mobile. If you use Monitoring we will get logs containing ETW traces of USB2, USB3, UsbUcx, and hub events, which are not filtered. USB function logs will not be captured. Otherwise, if you do not use Monitoring, we will not get these logs. Be aware that logs may be as small as 10mb or as large as 100mb depending on how much USB traffic and how much time you spend with Monitoring enabled. When you send feedback using Monitoring, please make sure you actually reproduce the issue.

Please continue to provide feedback on our blogs! This blog will be updated as necessary with new guidance and information. If you choose to capture your own USB logs outside of Windows Feedback Hub Repro Mode, look through our other blog entries on how to do this, for example this blog.

Windows Feedback on Desktop

1. Launch the Feedback Hub from the Start menu. The Feedback Hub tile should be located in the alphabetical menu or may be pinned to your favorites.

StartMenu

2. After launching the Feedback Hub, select the feedback tab from the drop down menu on the left hand side of the screen

pic02a

3. From the Category drop down menu select Hardware, Devices, and Drivers.

Hardware, Devices, and Drivers

4. From the Subcategory drop down menu select USB attached devices.

pic04

5. Click on Add new feedback.

pic05

6. You should see a screen like this. Make sure you select “Problem” when filling out the form. Please disconnect all other USB devices from the system except for the device on which you reproduce the issue before selecting the Begin monitoring button. Then Select Begin monitoring.

pic06

7. After clicking Begin monitoring you will see this screen. The stopwatch logo in the top right corner indicates that logs are being collected.   Proceed to duplicate whatever action caused the issue.  This will capture the USB logs while you repro the issue.

pic07

8. Navigate back to the application and select Stop monitoring. You should see the attachment icon below the grayed out Begin monitoring button. If you need to abort, hit Cancel and go back. If you need to try again, click Remove next to System monitoring file and try again. Do not click the Submit button if you do not want to submit your logs.
pic08

9. This feedback will be sent to the USB team with logs. Thank you!

Windows Feedback on Mobile

1. Launch the Windows Feedback Hub app from the Start screen. The Feedback Hub tile should look like this:

phonepic01

 

2. After launching the Feedback Hub app, select the menu icon on the top.

phonepic02

 

3. Select Feedback from the drop down menu.

phonepic03

4. On the next page select the + to add new feedback.

phonepic04

 

5.On the next page, make sure you select Problem for the kind of feedback. Give a brief summary of your issue.

phonepic05

6. Next scroll down to select a category and subcategory and under Category select Hardware, Devices and Drivers. Under Subcategory select USB attached devices.

phonepic07

7. Next scroll down until you expose Begin monitoring. Click on it and you have 60 seconds to repeat the action that caused the error problem. This will capture logs for the USB team to investigate while you reproduce the issue. The red stop watch in the bottom corner of the app indicates that logs are being captured.

phonepic08

8. Click Stop monitoring to stop collecting logs.

phonepic09

9. After hitting stop you will see a file icon with the name "System monitoring file".  If you want to try to reproduce the issue again, select Remove. If you no longer want to send any logs, select Cancel.  Otherwise select Submit to send your logs.

phonepic10

10. This feedback will be provided to the USB team with logs. Thank you!


Comments (3)

  1. Larry Darby says:

    Was liking windows 10 Till it was upgraded today. can you re do it!

  2. Sean Liming says:

    can the 60 second delay be extended?

  3. ryanpavlik says:

    So here’s a tricky one – can this monitor and log (and submit) feedback on a Windows 10 WDF_VIOLATION bugcheck/bluescreen that only, but reliably, happens on system shutdown when a particular USB device is plugged in? (Can the logman-based ETW/WPP logging do it?)

    I’ve already looked at the minidump (power policy related – https://github.com/OSVR/OSVR-Core/issues/389#issuecomment-236602835 – note that the issue is on totally the wrong github repo, but…), but since it’s just using stock Windows drivers, it’s not clear what exactly is going on or whose issue it is – Windows driver, USB device firmware, etc. (though fingers get pointed at our “drivers” because we have a driver pack containing CDC infs pre-Win10, other infs that exist primarily just to name stock devices, and device metadata packages for Drivers and Printers…)

Skip to main content