READ: HOW TO SUBMIT BUGREPORTS v2.1 (READ THIS IF YOU WANT THEM FIXED)

[Guest]

[gibran]

When you need to submit a bug please search if it was already posted and join that Topic if that bug affect your V3 Version as well.
If you discovered a new bug please make your topic title as descriptive you can.

Remember to read IMPORTANT: APPEND CFP VERSION NUMBER AND BIT (X32 or X64) TO YOUR BUGREPORTS to look at some examples.

TIP: always look at topmost topics in every childboard you post.
   Important topics have an icon like or a drop shadow like


In order to provide enough informations to fix bugs please include those infos in your posts:

Please submit ONE bug per post and change the subject to describe your post and append the Version number and BIT(X32 or X64) of your CFP

If you added some info to the topic title remember to duplicate them in your posts too.

Make sure that this info is placed in all your bugreports even if you join an existing topic to confirm that you are affected too.

• CPU (32 bit or 64 bit)
• Operating System information (including Service Pack Version)
• Actively-running security and utility applications  (Optional if you post a  Comodo Firewall Pro Configuration Report) 
• Specific symptoms of the bug, and steps you can take to reproduce it (step by step).
• Specific steps you have taken to try to resolve it.
• Brief description of your Defense+ and  Firewall+ mode (Custom, Train with safe) plus mention if you modified any setting in ADVANCED section of D+ and F+ (Optional if you post a  Comodo Firewall Pro Configuration Report)
• If you pc reboots or you have a BSOD post in  BSODs: Please add your minidump files here
• Report if you are using an Administrator account Or a Limited User account. Vista users please Report if you have UAC Disabled or Enabled (Optional if you post a  Comodo Firewall Pro Configuration Report) 

NOTE:

• If you can please add screenshots about relevant error dialogs, CFP Log entries or CFP settings or alerts.
  You can attach images clicking the Additional Options... link when you write your post
• If you'll attach a report from Comodo Firewall Pro Configuration Reporting Script you can skip Steps 3,6,8.

In order to enable crashdumps and to find them please read:

• How to find crashdumps in Windows XP
• How to find crashdumps in Windows Vista

If you wish please raise a Support Ticket.

NOTE: If your reply from Comodo Support states that your support ticket was closed please don't worry. You can reply to that email to reopen that ticket. Tickets are usually closed by default after a reply.

[gibran]

How to find crashdumps in Windows XP
In order to confirm that Dr.Watson MS Crashdump utility is enabled run  drwtsn32 -i


If some application crashed and you think it is related to CFP please run drwtsn32.exe without any options or switches and look for a crash dump in the path listed in Dr.Watson dialog (Make sure it was created at the time the crash happened) please confirm that Dump symbol table, Dump all thread contexts, Append to existing log file and Create crash dump file checkboxes are enabled. "Create crash dump file" checkbox is the most important option to enable.

[gibran]

How to find crashdumps in Windows Vista
Windows Vista uploads the crash logs to Microsoft but does not save a local copy. You need to enable this option running a file contained in Windows Error Reporting.zip
You need to uncompress Windows Error Reporting.zip and then run Windows Error Reporting.reg

NOTE: in some cases you will only see the name Windows Error Reporting without the .zip or .reg part . You can right click and coose Properties to confirm the filetype.

When an application crashes you can find the required crash informations in %LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueue

Just paste that bolded text in explorer and hit go


Be sure to include the following files in a compressed zip file:

WERxxxx.tmp.mdmp
This is the most important file. It contains the crash dump that can be opened inside Visual Studio or other Windows debuggers.

WERxxxx.tmp.version.txt
Contains the operating system version and other hardware information.

WERxxxx.tmp.appcompat.txt
Lists all of the DLLs loaded at the time of the crash with their version information.

[Tags:]