COMODO Virtual Service Manager termination [M227]

Hi,
I thought just to let you know that in a windows 8 64-bit log in a event viewer under the system log I am receiving error log " The COMODO Virtual Service Manager service terminated unexpectedly. It has done this 1 time(s)."
I think it is related to a virtual kiosk and it appears in a logs after using it.

Thank you very much for your issue report.

We would very much appreciate it if you would be kind enough to edit your report to put it in the standard format as this will make it much easier for the developers to diagnose and fix the problem.

The reasons we need all the information in the format, though they may not seem directly relevant to the issue are explained here.

If you are able to do this we will forward this post to the format verified board, where it is more likely to get looked at by developers. You can find assistance using red links in the format and here. If you need further help please ask a mod. If you do not add the information after a day or two we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.

In the current process we will normally leave it up to you whether you want to make a report in standard format or not. However we may remind you if we think a bug of particular importance.

Many thanks again

Mouse

When your virtual kiosk hangs and you reset the sandbox you should get this event viewer listing.
Or Possibly if you reboot the pc after the virtual kiosk hangs (says looding virtual kiosk forever)you would get this event viewer listing.
The kiosk bug has been reported and fixed.
expect a new release in the future with lots of fixes. I have no time frame. just be patient.

I thought just to let you know that in a windows 8 64-bit log in a event viewer under the system log I am receiving error log " The COMODO Virtual Service Manager service terminated unexpectedly. It has done this 1 time(s)." I think it is related to a virtual kiosk and it appears in a logs after using it.

While related to virtual Kiosk, it is probably not the same issue, so we’d still appreciate an issue report please. There should also be a dump file - please see resources for bug reporters regarding how to find and append it.

Best wishes

Mouse

PM sent

[color=blue][/color]A. THE BUG/ISSUE

[ol]- Comodo Virtual Service Manager termination appears in a windows log after using Virtual Kiosk .

  • Can U reproduce the problem & if so how reliably?: [color=blue]:yes
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened: Running virtual Kiosk than exiting and reseting sendbox
  • If not obvious, what U expected to happen:
  • If a software compatibility problem have U tried the conflict FAQ?:
  • Any software except CIS/OS involved? If so - name, & exact version:nop
  • Any other information, eg your guess at the cause, how U tried to fix it etc:nop
  • Always attach - Diagnostics file, Killswitch processes list, dump (if freeze/crash). If complex - CIS logs & config, screenshots, video, zipped program (not m’ware)
    [/ol]

B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- CIS version & configuration:proactive

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:D+/HIPS=Safe, ASB/BB=Enabled, Firewall=Safe AV=Max,
  • Have U made any other changes to the default config? (egs here.):just switched to proactive config. and adjusted antivirus options( see picture)
  • Have U updated (without uninstall) from a previous version of CIS:yes however the installation first removed the previous version
    [li]if so, have U tried a a clean reinstall - if not please do?:yes just to be sure,
    [/li]- Have U imported a config from a previous version of CIS:no
    [li]if so, have U tried a standard config - if not please do:
    [/li]- OS version, SP, 32/64 bit, UAC setting, account type, & VM used:windows 8 Pro 64 with media center, all updates, UAC + account=windows default
  • Other security/sandbox software a) currently installed b) installed since OS: a) no b) no, meaning no as of I was and I am using only CISv6 with a killswitch.
    [/ol]

[attachment deleted by admin]

Thank you very much for your bug report in standard format. We very much appreciate the effort you have made to document this bug.

We are sorry to trouble you further but there are some items of information missing or unclear in your post:

B.7 Do you mean a) no b) no

The reasons we need these items of information, though they may not seem directly relevant to the issue are explained here.

We would be very grateful if you would add these items of information so we can forward this post to the format verified board, where it is more likely to get fixed. You can find assistance using red links in the Format and here. If you need further help please ask a mod. If you do not add the information after a week we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.

In the current process we will normally leave it up to you whether you want to make a report which includes all necessary information or not. We may remind you if we think a bug of particular importance.

Many thanks again

Mouse

Thank you very much for your report in standard format, with all information supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.

Developers may or may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.

Many thanks again

Mouse

After update to CIS v6 .2708 problem is still not resolved.

Can you please check and see if this is fixed with the newest version? Please let us know whether it is fixed or you are still experiencing the problem.

Thank you.

PM sent.

Hi,
Problem still persist.
product version: 6.1.276867.2813
database version: 16340

Can you please check and see if this is fixed with the newest version (6.2.282872.2847)? Please let us know whether it is fixed or you are still experiencing the problem.

Thank you.

PM sent.

Not fixed in _2847.

This is happening because the ‘cmdvirth.exe’ process starts when opening a virtualized application or VK and it is not terminating when you close VK or any virtualized application(Screenshot of process).
Then when you come to reset the sandbox the process is forced to close from this action so the reset process can complete.
The error is not logged if the system has been rebooted in between running virtualized and resetting as the system shutdown terminated the ‘cmdvirth.exe’ process.
Exiting the sandbox should terminate the ‘cmdvirth.exe’ process.

[attachment deleted by admin]

Thanks for checking this.

I’ve updated the tracker.

In version 6.2.282872.2847 the problem with a VSM-t in the logging report appears to be still not fixed.

Regards,

Thanks for checking this.

Hopefully this gets fixed within the next few updates.

CIS v. 6.3.294583.2937

VSM unexpected termination log not fixed.

Win 8 pro 64

[attachment deleted by admin]

Thank you for checking this.

I have updated the tracker.

Can you please check and see if this is fixed with the newest version (7.0.313494.4115)? Please respond to this topic letting us know whether it is fixed or if you are still experiencing the problem.

Thank you.

PM sent.

I am experiencing the same issues as the originial poster.
Running CIS 7.0.317799.4142 on Win 8.1 64. Problem still NOT fixed.