To use the bug reporting format for Betas:
- Copy Format between dotted lines
- Create new topic and paste format into it
- Fill in format, replacing question marks with your answers
- Explain the problem in the title of the bug report
- Always attach a diagnostics report to each post
(To Create diagnostics report click on Help(Question Mark icon) in the main menu, choose Support->Diagnostics. When diagnostics scan is complete, click on “Create Report…” and save the report. )
[nobbc]
1. The full product and its version:
?
2. Your Operating System (32 or 64 bit) and ServicePack revision. and if using a virtual machine, which one:
?
3. List all the configuration changes you did. Are you using Default configuration? If no, whats the difference?:
?
4. Did you install over a previous version without uninstalling first, or import a previous configuration file?:
?
5. Other Security, Sandboxing or Utility Software Installed:
?
6. Step by step description to reproduce the issue. Or if you cannot reproduce it, what you actually did before it happened, step by step:
1: ?
2: ?
3: ?
7. What actually happened when you carried out these steps:
?
8. What you expected to see or happen when you carried out these steps, and why (if not obvious):
?
9. Any other information:
?
[/nobbc]
Please add extra info for specific problem types as follows
[ol]- BSOD/Crash: Always append: Diagnostics reports, Complete Dumps. If relevant samples/download links. If many config changes export config.
- Logic problems: Append where relevant: Diagnostics reports, Samples/download links, CIS logs, Killswitch process list. If many changes, export config. If AV issue, AV database version
- Performance: As 2 above, plus always append screenshots to show CPU and memory usage of all processes.
- Difficult to explain issue: Video or very detailed steps [/ol]