C.IS virtual desktop error

Allo im using latest version o cis 10.0.0.6092, in windows 10 wich is fully updated , an i have a small problem every time i open virtual desktop an error message shows up , the desktop opens but the error keeps opening to, it says this: “ctfmon.exe exception rapid failure” im sending a screen shot of this , if someone can help solving this please say thank you very much!

  1. Please attach a diagnostics report & configuration.

Reset Sandbox
Get ProcDump: ProcDump - Sysinternals | Microsoft Learn
Use following command : procdump.exe -w -ma -e -n 3 ctfmon.exe
Now, launch Virtual Desktop
& Provide link to dumps.

Thanks.

Allo mr qmarius thank you for your help, but ProcDump doesnt open in my windows 10 64 bits system, it opens and closes like a flash light dont know if this is normal behavior or not , but i dont think it is so if you could clarify on this i would be glad, thank you!

Open Notepad > Copy & Paste :


pushd "%~dp0"
procdump.exe -w -ma -e -n 3 ctfmon.exe
pause

Save as : name.bat
Get ProcDump : Get ProcDump: ProcDump - Sysinternals | Microsoft Learn
! make sure procdump.exe is saved in same location as previously saved .bat file

Disable Auto-Sandbox component
Run previously saved .bat file

Allo im sorry but, im not making this well it opens cmd but it says procdump.exe is not recogniged sending print screen for you to see thank you for your help!

Do this:

  1. open an elevated/administrator cmd prompt via right-click on windows start and select command prommpt (administrator)
  2. change directory to where procdump is located via the cd cmd e.g. cd C:\Users<your username>\Downloads\procdump if you saved it in your downloads folder.
  3. then execute procdump with the command line options provided earlier.

Allo again mr aquarius this is not working for me i dont understand what is wrong but thanks any way im leaving to print screens here

Hmm. Feeling like a zodiac sign now for unknown reasons.
I’ve edited my post. Please check again Reply #3.

Hope it helps.

ALLO again im sorry but is not working im giving up, dont bother with this any more mr Qmarius i dont use virtual desktop often so, this is not a big deal!thank you!

It looks like you only have procdump64 the zip should also contain procdump.exe. But you can use procdump64 with the same command line arguments so procdump64.exe -w -ma -e -n 3 ctfmon.exe then open virtual desktop.

Do note that procdump.exe launches an instance of procdump64.exe. It’s not really needed/recommended to get 64-only version based on my experience.

Allo again and sorry for not making things properly maybie, but this is not working so i would like to say that this is not a very important thing, so you dont have to bother with this! , i apreceate the help from you guys in the forum now im puting too screenshots with what is happening now and say thank you again !

It’s working, actually. Now you have to launch Virtual Desktop and .dmp files should be created.

the .dmp files are located here windows\minidups right? there is nothing there

no it would be located in the same directory where procdump is located.

Additionally to what futuretech said, do note that dumps should be created only when you encounter that error (eg if there’s a crash).

Hi,

same Problem here. Fully updated Windows 10 and Comodo

Was trying to create a dump, but no DumpFiles are created.

See attachment with screen (ctfmon.png) before procdumps closes.

(ctfmon2.png is shown when im starting ComodoDragon in VirtualDesktop)

Hi,

I’m guessing that means :
A. another instance is launched after monitored one
B. exception is not caught (plausible since a handled access violation is listed in your screenshot)

You could try to :

  1. register ProcDump as postmortem debugger : procdump -ma -i c:\dumps
    & check if dumps are created under c:\dumps
  2. log each exception: procdump.exe -w -ma -e -l -n 30 ctfmon.exe
    (a bit extreme but it should do the job)

By the way, is there any other issue besides that one? is Virtual Desktop launched correctly?

It would be great if you could provide Windows version in addition.
run > winver

Ok, tried again but no Dumps are created.

After clicking away the Error ctfmon exits. And VirtualDesktop shows up.
When starting a Process in VD same ctfmon Error shows up now


C:\>procdump -ma -i c:\dumps

ProcDump v8.2 - Sysinternals process dump utility
Copyright (C) 2009-2016 Mark Russinovich and Andrew Richards
Sysinternals - www.sysinternals.com

Set to:
  HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
    (REG_SZ) Auto     = 1
    (REG_SZ) Debugger = "C:\procdump.exe" -accepteula -ma -j "c:\dumps" %ld %ld
%p

Set to:
  HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug
    (REG_SZ) Auto     = 1
    (REG_SZ) Debugger = "C:\procdump.exe" -accepteula -ma -j "c:\dumps" %ld %ld
%p

ProcDump is now set as the Just-in-time (AeDebug) debugger.


C:\>procdump.exe -w -ma -e -l -n 30 ctfmon.exe

ProcDump v8.2 - Sysinternals process dump utility
Copyright (C) 2009-2016 Mark Russinovich and Andrew Richards
Sysinternals - www.sysinternals.com

Waiting for process named ctfmon.exe...

Process:               ctfmon.exe (9384)
Process image:         C:\Windows\System32\ctfmon.exe
CPU threshold:         n/a
Performance counter:   n/a
Commit threshold:      n/a
Threshold seconds:     n/a
Hung window check:     Disabled
Log debug strings:     Enabled
Exception monitor:     Unhandled
Exception filter:      [Includes]
                       *
                       [Excludes]
Terminate monitor:     Disabled
Cloning type:          Disabled
Concurrent limit:      n/a
Avoid outage:          n/a
Number of dumps:       30
Dump folder:           C:\
Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS
Queue to WER:          Disabled
Kill after dump:       Disabled


Press Ctrl-C to end monitoring without terminating the process.

[08:21:49] Exception: E06D7363.?AUXH@Cn@@
[08:21:49] Exception: E06D7363.?AVResultException@wil@@
[08:21:49] Exception: E06D7363.?AUXH@Cn@@
[08:21:49] Exception: E06D7363.msc
[08:21:50] Exception: E06D7363.?AUXH@Cn@@
[08:21:52] The process has exited.
[08:21:52] Dump count not reached.


C:\>procdump.exe -w -ma -e -l -n 30 ctfmon.exe

ProcDump v8.2 - Sysinternals process dump utility
Copyright (C) 2009-2016 Mark Russinovich and Andrew Richards
Sysinternals - www.sysinternals.com

Waiting for process named ctfmon.exe...

Process:               ctfmon.exe (5708)
Process image:         C:\Windows\System32\ctfmon.exe
CPU threshold:         n/a
Performance counter:   n/a
Commit threshold:      n/a
Threshold seconds:     n/a
Hung window check:     Disabled
Log debug strings:     Enabled
Exception monitor:     Unhandled
Exception filter:      [Includes]
                       *
                       [Excludes]
Terminate monitor:     Disabled
Cloning type:          Disabled
Concurrent limit:      n/a
Avoid outage:          n/a
Number of dumps:       30
Dump folder:           C:\
Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS
Queue to WER:          Disabled
Kill after dump:       Disabled


Press Ctrl-C to end monitoring without terminating the process.

[08:23:08] The process has exited.
[08:23:09] Dump count not reached.

C:\>

Windows 10 x64

WinVer:
Microsoft Windows
Version 1607 (Build 14393.953)