Author Topic: Resources for bug reporters  (Read 108517 times)

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Backing up and restoring your CIS settings.
« Reply #15 on: November 15, 2010, 09:06:33 AM »
To back up
  • In 6.x navigate to Advanced Settings ~ General Settings ~ Configuration. In 5.x go to More ~ Manage Configurations ~ Export
  • Export your current settings to a .cfgx file with a distinct name of your choosing, in a folder *outside* the Comodo directories, saving if asked
  • Go to Program files/Comodo/Comodo internet security/Database, copy the files named Trusted.db, Vendor.h and Vendor.n


To restore
  • Go to More ~ Manage Configurations ~ Export
  • Import the configuration, highlight it, and then choose 'activate'
  • Copy the Trusted.db, Vendor.h and Vendor.n files back to their original location over writing existing. If this causes an access error, try the same in safe mode if you know how, or PM a currently active mod for help
  • Reboot to ensure all software is running under the imported rules


NB if asked to test for a bug after a clean re-install of CIS please do not import your settings before testing.
« Last Edit: January 14, 2013, 04:54:37 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Doing a clean re-install of CIS without losing your settings
« Reply #16 on: November 24, 2010, 02:16:32 PM »
You'll hardly lose any settings if you follow this guidance:


If you have been asked to do a clean reinstall to see if it solves your problem please do not restore you settings until you have done the test. Clean re-installs also clear CIS log, so please make sure you have created any log screenshots you need before doing this.
« Last Edit: January 14, 2013, 04:58:46 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Criteria for entering bugs in Bugzilla (Needs updating)
« Reply #17 on: November 25, 2010, 06:15:22 AM »
FOR MODS ONLY - Needs updating when Comodo tracker is introduced

Mods enter bugs into the mod's issue tracking system - Bugzilla - at their discretion. However mods may, if they wish, use the following criteria to determine which user-reported issues are tracked.

These are in addition to the normal criteria given for issue reports in the format and guide.

  • BSODS and crash reports with dumps normally get a Bugzilla entry with a cc to Head of Development
  • Other issues should meet the following criteria:
    • Importance. Be likely to have have a significant impact on a significant proportion of users, or a substantial effect on a smaller number, or a small effect on a substantial proportion of users. This means that they will enter Bugzilla with a severity of 'normal' or above.
    • Replicability. Be reported by at least 2 users, or be replicable on a mods/devs computer, or be accepted by devs as a valid issue, or be from a user whose expertise the mod is familar with
    • Resistance.
      • be unlikely to be resolvable by trying further, more advanced, settings changes [1].
      • Has continued despite trying disabling or uninstalling potentially conflicting security software from other vendors. This test is relevant even if the problem, does not seem to involve security software from other vendors. Such conflicts can cause complex and indirect effects.
    • Persistance. Not solved by a clean reinstall of CIS - ie not a transient version update/import problem. Not solved by a new AV database, TVL, whitelist update.

Bugs that do not fulfill these criteria may be marked [NBZ] if the mod feels they are never likely to, or be left flagged [WBZ] if they may given further information, user tests or user reports.

Footnote:
[1] Only the standard settings changes will have been tried by the time the bug reaches format verified - so others may be tried before the issue enters Bugzilla. But these changes should of course be without significant side effects. Issues with work-arounds are still bugs.
« Last Edit: January 24, 2013, 05:43:46 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Loading a standard configuration without losing your settings
« Reply #18 on: November 25, 2010, 09:55:40 AM »
CIS stores your current customised configuration in your currently active configuration, which may (confusingly!) bear then name of a standard configuration. So to be sure to load a clean configuration you need to do the following:

  • In 6.x Navigate to Advanced Settings ~ General Settings ~ Configuration. In 5.x Navigate to More ~ Manage My Configurations
  • Backup your current configuration to a non-comodo directory by choosing export, navigating to the directory, agreeing to save if asked, and naming the resulting export file with say your name and the date. To avoid confusion do not give the file the name of a standard configuration.
  • Choose import and navigate to the Program Files\Comodo\Comodo Internet Security directory
  • Choose Comodo Internet Security configuration (the default - use to test a problem under default settings) OR the Comodo Proactive Security configuration (slightly higher security) OR Comodo Firewall Security configuration (same as IS config but no AV). To be double sure choose the details view on the import dialog and check that the file date is the date of the last CIS update - if not ask for help.
  • Make this configuration your active configuration by selecting it then pressing the activate button
  • Reboot to make the configuration fully effective
  • Test to see if your prefer this configuration - for example test to see if any bug has disappeared?
  • If you want to go back to your backup configuration simply import it and activate it as above then reboot.

 


« Last Edit: January 14, 2013, 04:43:54 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Re: Resources for bug reporters
« Reply #19 on: October 31, 2011, 07:00:31 AM »
FOR MODS ONLY: How to distinguish an 'issue' from a 'wish list item'

A report refers to a valid issue if:
a) it would be a perceived as a problem by the average user
AND
b) a possible remedy would fall within a notional design specification for the CIS product, given the CIS product's current requirements scope (what sorts of security it tries to address) and design philosophy (the approach it takes in addressing it).

If it falls outside b) then it's a wish list item. If it falls outside a) then it's a design feature :)

The problem is we have no design documentation for CIS. The closest we have is an out of date help file. So this is always a matter of judgement.

« Last Edit: October 31, 2011, 07:02:41 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Re: Resources for bug reporters
« Reply #20 on: March 22, 2012, 06:44:03 AM »
How to find and save event log files.

To find the logs, see these links:

Defence plus event logs.
Antivirus Defense logs.
Firewall event logs.

To save the file you can either take a screenshot of the log, or click on More in each log view and use the full log viewer to export a file.

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Reporting your killswitch processes
« Reply #21 on: January 15, 2013, 04:32:56 AM »
You can find your Killswitch process list by going to Advanced Tasks ~ Watch Activity. More details here.

On the Main Menu ~ Killswitch use 'Save current view'.
« Last Edit: July 05, 2014, 08:17:34 PM by Chiron »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
OS version information
« Reply #22 on: January 23, 2013, 05:12:44 AM »
This information is normally available from Computer ~ Properties or My Computer ~ Properties

Version=the main version eg Windows 7

SP= Service Pack number. The main maintenance release number of a Microsoft Operating system.

x32/x64 is the number of bits the OS uses

« Last Edit: January 23, 2013, 07:19:40 AM by mouse1 »

Offline mouse1

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11862
Re: Resources for bug reporters
« Reply #23 on: January 23, 2013, 12:27:30 PM »
Please be careful to choose the right set of instructions (for CIS 5.x or 6.x) or you may lock-up your computer (reboot to resolve if you do!).  

CIS 5.x

  • Disable Defense+ by moving the level slider in D+ ~ Settings to disabled
  • Download and run Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
  • In Process Explorer, select  View->Lower Pane View->Handles.
  • In Process Explorer Process window, click on cmdagent.exe in CIS 5.x
  • At this stage, in the lower pane, you should be seeing handles opened by cmdagent.exe. You are particularly interested in "Type= File". Try and get as many of 'type file' on screen as possible and leave it visible
  • Open CIS and Run a Scan -> My Computer. Do this overnight perhaps.
  • Wait until the cmdagent hangs or the morning :) When it does you may get a crash dialog. Don't answer this dialog. When the scan hangs, please go to Process Explorer and
  • Without deselecting cmdagent, check the Lower Pane for open "File Handles". You may or may not be able to scroll at this point - hence my suggestion about getting as much as possible in view. One of those handles are causing this issue. Probably an archive file. Make a list of the handles (if you can scroll, do) or take screenshots.
  • If you cannot get a list of handles right click on cmdagent in process explorer and take a full dump using the menu.
  • Please append file-list, or if you cannot, the dump. If you are willing to right click scan each of the files in the file handle list in turn until you get a crash and append the zipped file that causes it, so much the better, but this is not required.

CIS 6.x
  • Open CIS and Run a Scan -> My Computer. Do this overnight perhaps.
  • Open Killswitch from Advanced tasks ~ Watch Activity.
  • In Killswitch right click on the cavwp.exe process (if two, the one consuming most CPU, which is the one that appears after you start to run a scan) and select  the handles tab
  • At this stage, in the lower pane, you should be seeing handles opened by cavwp.exe. You are particularly interested in "Type= File". Maximise the dialog to try and get as many of 'type file' on screen as possible and leave it visible
  • Wait until cavwp.exe hangs or the morning :) When it does you may get a crash dialog. Don't answer this dialog. When the scan hangs, please go to Process Explorer and
  • Without deselecting cavwp, check the tab for open handles of type "File". You may or may not be able to scroll at this point - hence my suggestion about getting as much as possible in view. One of those open handles are causing this issue. Probably an archive file. Make a list of the handles (if you can scroll, do) or take screenshots.
  • If you cannot get a list of handles right click on cavwp.exe in killswitch and take a full dump using the menu. If you get a refusal, you are trying to dump the wrong cavwp.exe, try the other one
  • Please append file-list, or if you cannot, the dump. If you are willing to right click scan each of the files in the file handle list in turn until you get a crash and append the zipped file that causes it, so much the better, but this is not required.
« Last Edit: July 11, 2013, 03:06:25 PM by mouse1 »


Offline Chiron

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 11951
Creating Complete OS Dumps On Command
« Reply #25 on: May 27, 2014, 04:07:03 PM »
Complete OS DUMPS
To report BSOD'S and complete OS freezes please set your computer up to record Complete OS dumps, not minidumps or kernel dumps.


Setting up your computer to collect Complete Dumps

- Windows XP users should follow the advice given on this page to configure their computers to create Complete Memory Dumps.
- Windows Vista users should follow the advice given on this page to configure their computers to create Complete Memory Dumps.
- Windows 7 users should follow the advice given on this page to configure their computers to create Complete Memory Dumps.
- Windows 8 users should follow the advice given on this page to configure their computers to create Complete Memory Dumps.
- Windows 10 users should follow the advice given on this page to configure their computers to create Complete Memory Dumps.

How to generate a manual memory dump when computer stops responding
If testing CIS, it's a good idea to have the ability to force a blue screen in the case of a total computer freeze so you can create a dump file for QA.

To perform a complete memory dump a BSOD is induced so please save all work first!


Keyboard initiated (recommended method)

Open Notepad > Copy & Paste below content
Code: [Select]
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters]
"CrashOnCtrlScroll"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters]
"CrashOnCtrlScroll"=dword:00000001
Select "File" menu > "Save As..." menu item > At "Save as type" field, select "All Files (*.*)" > At "File name" field, type : name.reg
Run name.reg file which you saved previously & Restart system
To initiate a crash, make sure you have saved all data in all user files then hold down the RIGHT Ctrl Key and press Scr Lk key twice
Wait for memory dump to be created, this may take some time.

See MSDN for more information : http://msdn.microsoft.com/en-us/library/windows/hardware/ff545499%28v=vs.85%29.aspx


NotMyFault tool
Download the NotMyFault tool : https://technet.microsoft.com/en-us/sysinternals/notmyfault.aspx
For example, run Command Prompt as administrator.
At the command line, type NotMyFault.exe /crash, and then press ENTER.



Saving dumps

Complete OS dumps can be the size of your physical memory (RAM), but can compress well if you zip them - maybe down to to 10-20% of that size.The less apps you have running the more they compress. That's still pretty big of course so you need a big upload account to upload them. I use https://mega.nz for this purposes as they give away 50Gb, and have few other restrictions, although they do require free registration.
« Last Edit: December 27, 2016, 07:45:25 AM by qmarius »

Offline qmarius

  • Star Group
  • Comodo's Hero
  • *****
  • Posts: 3843
  • making simple things complicated
Display File Tracking info by enabling a Property Page
« Reply #26 on: December 23, 2016, 11:37:36 AM »
Comodo Property Page
You can diagnose issues with File Rating technology by enabling a page extension that presents gathered file data in JSON format. Such data is very useful to developers and power users when narrowing down issues. A moderator may request a copy of such information.

Important note: To avoid any risk, since you are working with Windows Registry, please create a system restore point by following this guide:
[Create a system restore point]





Enabling property page
From attachment, run "enable_page.reg" file.
* archive password: COMODO

Disabling property page
From attachment, run "disable_page.reg" file.
* archive password: COMODO




Further note: It comes with no warranty & it might be removed in the future.

Offline futuretech

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 5349
Re: Resources for bug reporters
« Reply #27 on: April 23, 2017, 09:10:50 PM »
How to generate a diagnostic report.
When creating a bug report or when asked to provide a diagnostic report, you can do so by opening the main UI of CIS/CFW/CAV and click on the ? symbol to find the support menu item, then click on the diagnostics menu item to start the diagnostic report process. When it finishes click on create report even if no problems were detected. Then a save window appears in which you can choose where to save the report which will be saved in zip folder format. You would then attach that zip folder to your post.


Attached below are the different themes showing where to find the diagnostic task.


« Last Edit: April 24, 2017, 08:27:09 AM by futuretech »

Offline PremJK

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 501
  • Live and Let Live
Re: Resources for bug reporters
« Reply #28 on: May 17, 2017, 11:01:28 AM »
Steps to Collect Procmon Bootlog

1)Download Process Monitor from here for Windows Vista and higher and
    Process Monitor from here for Windows XP
2)Extract the downloaded .zip file and run Procmon.exe by "Run as administrator"
3)Select Enable Advanced Output from Filter Options menu
4)Click Options and select Enable Boot Logging
5)You will get Boot logging options window. Enable Generate thread profiling events and set to Every second. Click Ok to confirm your settings
6)Reboot the system
7)Allow the system to fully load windows and any associated startup programs
8)Now again run Procmon.exe by "Run as administrator"
9)You will a prompt window with information about a log of boot-time activity being created. Click Yes to save the boot log.
10)Choose a location and save the boot log, a .pml file will be generated.

« Last Edit: June 09, 2017, 02:26:04 AM by PremJK »

Offline PremJK

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 501
  • Live and Let Live
Re: Resources for bug reporters
« Reply #29 on: November 28, 2017, 10:33:24 AM »
Steps to collect msinfo32.nfo:
1. Go to Windows Run (Windows Key + R key in keyboard).
2. Type in msinfo32.exe  and press Enter key, it will launch System Information window application.
3. Click 'Save' item in 'File' menu and save as .nfo file.

 
Steps to collect Windows Event logs:
1. Go to Windows Run (Windows Key + R key in keyboard).
2. Type in eventvwr and press Enter key, it will launch Event Viewer window application.
3. Select 'Windows Logs' -> 'Application' in opened window.
4. Right click on it 'Save All Events As...'.
5. Save as 'Application' events.
6. Repeat steps 3-5 for 'Security', 'Setup', 'System' events.

 

Free Endpoint Protection
Seo4Smf 2.0 © SmfMod.Com Smf Destek