EN
本內容沒有您的語言版本,但有英文版本。

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. From either the or the , sign in to the Dashboard by using your .

  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.

    noteNote
    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

    Release type

    Select the scope of your bug. For example, select Kit if your bug refers to the Windows Hardware Certification Kit (HCK/HLK).

    noteNote
    Select an option on the type of kit if you have picked the Release Type as Kit.

    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. (Optional)

    Please include all files as appropriate so that Microsoft can analyze the issue quickly. For Windows deployment/setup issues, please attach the following files in zip format to speed up the diagnosis:

    %windir%\Panther\*.*
    %windir%\inf\setupap.dev.log
    %windir%\winsxs\popexec.log
    %windir%\inf\setupapi.dev.log
    %windir%\logs\cbs\cbs.log
    %windir%\windowsupdate.log
    %windir%\winsxs\pending*.xml
    %windir%\*.dmp (if BSOD issue)
    
    

    For Display/GPU-related issues please include:

    dxdiag log [start - dxdiag.exe - save all info]
    dispdiag log [run dispdiag.exe from command-prompt and send the .DAT file]
    
  6. When all information is complete, click Save at the top of the form.

顯示:
© 2015 Microsoft