Required Format For Reporting Bugs

[Chiron]

We'd very much appreciate it if you would follow the guidelines below  

If you do your report will be in full standard format, and will be forwarded to the format verified issues board. Devs fix issue reports in standard format more quickly & reliably as the info needed to replicate the bug is available & easily accessible. If you don't we'll forward it to Incomplete Issue Reports section. However, the devs will not be able to investigate and fix the reported bug as not enough information would have been provided.

Before you post, please check

• Is it a bug/issue? Follow links to post wishes and requests for help.
• Already reported? If so add to existing topic. See the issues reported in this section.
• One bug per post? It's difficult to track issues if there are more than one per topic.
• Have you tried? Reinstalling by following these steps or the advice on how to make programs work with CIS? If not, please do.
• Current version? Please report only bugs/issues for Version 6 or Version 7.

When you post please:

• Use the report format below.
  
  • Main format, for most issues. We explain why here.
  • Simple GUI Errors. For  issues relating solely to the GUI.
  • Help File Errors. For issues related solely to the online Help Files.
  • Translation errors. For errors in translations to languages other than English.

[Chiron]

To use the Main Bug Reporting Format:
1. Copy the format code between the dotted lines below
2. Create a new topic and paste the format code into it
3. Fill in the format, replacing the question marks with your answers
4. Summarize the bug in the topic title

Orange words are links to help

When filling out the form, in your own post, use Preview to see what it will look like.

-----------------------------------------------------------


[center][u]A. THE BUG/ISSUE (Varies from issue to issue)[/u][/center]
[b]Can you reproduce the problem & if so how reliably?[/b]:
?
[b]If you can, exact steps to reproduce. If not, exactly what you did & what happened[/b]:
1:?
2:?
3:?
[b]One or two sentences explaining what actually happened:[/b]
?
[b]One or two sentences explaining what you expected to happen[/b]:
?
[b]If a software compatibility problem have you tried the advice to make programs work with CIS?[/b]:
?
[b]Any software except CIS/OS involved? If so - name, & exact version[/b]:
?
[b]Any other information, eg your guess at the cause, how you tried to fix it etc[/b]:
?

[center][u]B. YOUR SETUP[/u][/center]
[b]Exact CIS version & configuration[/b]:
?
[b]Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV[/b]:
?
[b]Have you made any other changes to the default config? (egs here.)[/b]:
?
[b]Have you updated (without uninstall) from CIS 5, 6 or 7?[/b]:
?
     [b]if so, have you tried a a a clean reinstall - if not please do?[/b]:
     ?
[b]Have you imported a config from a previous version of CIS[/b]:
?
     [b]if so, have you tried a standard config - if not please do[/b]:
     ?
[b]OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used[/b]:
?
[b]Other security/s'box software a) currently installed b) installed since OS, including initial trial security software included with system[/b]:
a=?        b=?

[center][u]C. ATTACH REQUIRED FILES (delete this section (section C) after attaching required files)[/u][/center]
Always attach the diagnostics file (instructions on how to do this provided here) and the KillSwitch Process List (instructions on how to do that provided here) and put the resulting file in a zip file. Both should then be attached to your post.
Note that additional information may be requested by the processing Moderator.


---------------------------------------------------

[Chiron]

To use the GUI Bug Reporting format:
1. Copy the format code between the dotted lines below
2. Create a new topic and paste the format code into it
3. Fill in the format, replacing the question marks with your answers
4. Summarize the bug in the topic title


-----------------------------------------------------------



[b]1: CIS version:[/b]
?
[b]2: OS version:[/b]
?
[b]3: What you did:[/b]
?
[b]4: What you actually saw:[/b]
?
[b]5: What you expected to happen or see:[/b]
?
[b]6: If possible attach a screenshot illustrating the GUI problem[/b]


-----------------------------------------------------------

[Chiron]

To use the Help File Error reporting format:
1. Copy the format code between the dotted lines below
2. Create a new topic and paste the format code into it
3. Fill in the format, replacing the question marks with your answers
4. Summarize the help file error in the topic title


-----------------------------------------------------------



[b]1: A link to the relevant help file page:[/b]
?
[b]2: What the help files says on the issue of concern (if anything)[/b]
?
[b]3: What you think it should say or explain[/b]
?
[b]4: Why you think it should say or explain that[/b]
?

-----------------------------------------------------------

[Chiron]

To use the Translation Error reporting format:
1. Copy the format code between the dotted lines below
2. Create a new topic and paste the format into it
3. Fill in the format, replacing the question marks with your answers
4. Summarize the Translation Error in the topic title


-----------------------------------------------------------

[b]Information Enabling Reproduction On Other Machines[/b]

[b]1. Environment information:[/b]
  [b]a) CIS Version, if it was a clean-installed or updated from a previous version, indicate installation language:[/b]
      ?
  [b]b) OS version:[/b]
      ?
[b]2. Details of GUI area where the error was found e.g.: 'CIS Advanced settings'->'HIPS'->'HIPS Settings'->'Monitoring Settings'):[/b]
      ?

[b]Defect Description[/b]

[b]3. Describe the error in the terms of 'Expected result:'/'Actual Result:' or in any other clear form suggesting alternative texts/spelling corrections/etc:[/b]
     ?
     [b]a) If necessary, provide additional information supporting the reason of changes (reference to grammar/dictionaries/etc.):[/b]
     ?
[b]4. Attach the necessary number of screenshots with the problematic area(s) highlighted, preferably with colored frames/background/arrows/etc. to easily understand the issue.[/b]

-----------------------------------------------------------