[Johnson Licker]

Hi HF,

so I'm been looking into this for an hour and cannot figure out what is going on. If I make a new stub in DarkComet and run it, I will appear as any normal slave and a process will be created called remote service application. Here's the problem. When I crypt it with Chronic Crypter (I don't change any settings, I do that all in DarkComet) and run it, it will install itself in the temp folder, but I won't appear as a slave. BUT! When I run it a second time, it will create a process and I will appear as any normal slave. And the process will have a different name, cvtres.exe or something..

So I have never heard of anyone having this problem, if you know anything please comment below! I know it must be something to with Chronic. Have a good one,

Josh.

[sanzothegreat]

try to use other crypter.. if can solve your problem..

[xatas]

disable all the options on darkcomet and leave it default, then on the crypter enable options..startup etc. tell me how did it go

[Panthers]

Make sure you are only running one instance of your server. Just create your server in Darkcomet but don't change anything on it just leave it to the default settings. Once you load it to on your crypter try changing your settings there.
( run on start up, persistent process ect)

[muzzy.]

Try making a clean stub with no settings, then add in startup, persistence etc in the crypter and see if the problem persists.

[Johnson Licker]

There seems to be problems with Chronic at the moment, thanks for the help guys.

[Executing]

chronic is a beast crypter, maybe its just a temporary problem.

[Gunning]

Seems to be a problem with Chronic crypter, maybe you aren't choosing correct settings, I don't know any of the features to be honest on the Chronic crypter, but it has been up for a while as noted on their thread so it should be good.