File a New Bug

If you're using the Windows® bug management service to manage the bugs in your product, you can enter a new bug on the Bug management page on the Dashboard.

Creating and filing a new bug

You can create a new bug online, and then submit it to be filed with Microsoft.

To create and file a new bug

  1. Sign in to the Dashboard by using your Microsoft account.

  2. On the left side of the window, click Bug management.

  3. On the Bug management page, in the File a new bug tile, click File new bug.

  4. On the File new bug page, enter details about the bug, making sure that you enter information in every field that has an asterisk. See the following table for more details about the required fields.

    Field name Description of content

    Title

    Enter a title for your bug that is as descriptive as possible.

    Issue type

    Select a category for the bug, such as Code Bug.

    Assigned to

    Select Active or Microsoft to assign a bug to Microsoft. The default option is Active.

    Partner Priority

    Select an option for how quickly the bug must be fixed. For example:

    0 - The issue is currently blocking any further development in this area without a workaround. It must be fixed immediately.

    1 - This issue is blocking in some areas and must be fixed as soon as possible.

    2 - Should fix soon before product release.

    3 - This issue should be fixed if there is time before the release.

    Partner Severity

    Select a ranking for the severity of the bug. For example

    • 1- The issue causes a system crash or a loss of data.

    • 2- The issue causes major functionality or other problems, and in some cases, may cause a product failure.

    • 3- These are issues with impaired functionality.

    • 4- There are minor functionality issues that affect the fit-and-finish of the product.

    There is wording that may be unclear, or there are typographical errors that do not affect the use of the product.

    Repro steps

    Describe the actions you had taken when the issue occurred.

    Note

    For the quickest response, make sure to include the following details:

    • Expected results: Describe what you expected to happen after you completed the actions you performed.

    • Actual results: Describe what actually happened. This is the main issue of the bug.

    • The application or applications where the compatibility issue occurs.

    • The application language or languages involved.

    • If the application is downloadable, the URL where it is available.

      If the application is not downloadable, provide Microsoft with permission to share the application, or allow us to use it for reproduction and test purposes only.

    Product family

    Describe the product family where the issue occurred. For example:

    • Select Windows if it is a Client Operating System bug

    • Select Windows Server/System Center if it a Server related bug

    • Select Windows Legacy Servicing if it is a Servicing bug

    Partner type

    Select the entry that best describes the space in which you want to file your bug.

    Partner feature

    Select an appropriate feature area.

    Partner description

    Enter a detailed description of the issue.

  5. Click Browse below the Attachments label to attach a file to the bug. (Recommended)

    Attaching data at the time of bug submission helps us efficiently manage the bug process toward closure. Please use the appropriate process below for the specific issue being reported.

    For Windows Phone and IoT(ARM) devices: Please download the FieldMedic tool and run it on the devices that reproduce the issue you are reporting.

    Note

    Be sure that all providers associated with the problem you are reporting are enabled. This can be done by going to the Advanced menu within Field Medic, and selecting Choose which ETW Providers ....

    For Windows x86 and x64: Please use the log collection tool, UCSLogTool, posted on Connect and Microsoft Download Center. This tool will gather logs and traces relevant to the specific feature area selected. Follow these steps to use the tool:

    1. Download and install UCSLogTool on the problem device. When the installation is complete, start the tool using the desktop short-cut.

    2. After UCSLogTool starts, you’ll be presented with a user interface in the Command Prompt. Locate the scenario or feature that’s closest to the problem you’re reporting, enter the corresponding number, and then press Enter.

    3. After you’ve selected the scenario to be traced, a list of the selected features will be displayed. You can view additional features by entering Y, or continue by entering N.

    4. By default, any feature that’s selected will also include the General windows log collection feature. Please confirm that the correct traces have been selected, and then follow the prompts to either add additional features or to continue with the current selection.

    5. You’ll be prompted to keep the temporary folder containing a copy of the trace data. Follow the prompt, and press Enter.

      Note

      Many UCSLogTool features will open in a new window to capture their respective traces. When this occurs, follow the instructions in the new window, and then return to the UCSLogTool command window for the final steps.

    6. After the tool collects the traces, the collected trace data and logs will be compressed into a single ZIP file on the desktop (for example, GeneralDataCollection_15063.rs2_release.170317-1834.zip).

      Important

      Do not rename the file. Renaming the file will interfere with the automated processes that check it for validity

    7. Attach this .zip file to the bug

      Note

      If you are unable to execute the USCLogTool due to the system state, run the script manually by doing the following:

      1. Download and install the UCSLogTool on a working system.
      2. Copy the "UCSLogTool" directory (typically C:\Program Files\UCSLogTool) and its contents onto a USB Flash Drive.
      3. Connect the flash drive to the problem system when booted to OOBE or Windows PE.
      4. Press Shift+F10 on the keyboard to get to a command prompt.
      5. Change directory to the location on the USB Flash Drive that UCSLogTool was copied to.
      6. Run the following script manually to collect the General Windows log collection: UCSLogTool\WINDOWS_LOG\GetLogs.cmd LOGDIR
      7. After the tool collects the data, copy the data onto the flash drive and attach to the bug in a ZIP file format.

      We recommend submitting a memory dump file when the problem system is in a non-responsive state. This file will help Microsoft investigate the issue you are encountering.

  6. When all information is complete, click Save at the top of the form.

Send comments about this topic to Microsoft