New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Miner closes off after executed crypted miner .exe #2373
Comments
If it's an injection crypter (like most are) and if it does not inject into itself then you need to use the crypter Startup function instead of the miners, because when the miner is injected then it has no idea where the original file is and thus can't copy it to the installation folder. The administrator escalation shouldn't be a problem, it only tries to do that if it does not already have administrator privileges, which as you say the crypter already does. |
Yes that should likely work, though for your real build a "Remote Configuration" (or several for backups) is of course recommended in case you ever need to change the settings. |
I disabled startup, but it still doesn't working after crypted. Would that because the crypter and miner.exe BOTH support function that inject into some files like conhost.exe, explorer.exe? |
Sorry for the late response, I've been sick. The injection shouldn't be able to cause any problems, the only theoretical problem is the "Startup". Does the crypt work if you don't have any options enabled in the miner? |
I got exactly the same problem.... Anything we can do about it ? |
It does not work even with these settings? |
I tried those settings. Nope :( |
did you try to encrypt without anysettings in miner ? |
No, I havent tried yet. |
Doesn't work. I really tried every combination in the settings of the miner AND the crypter. |
Unam, pls i need help. The miner worked very well.
But my crypter seller crypted it for test and the crypted miner.exe just closes off and not start mining.
This is what the crypter seller assumed it as problem:
"After crypt it closes off in some time, exclusions aren't added"
"Crypt is not compatible, do you have other miners?"
"The miner asks for privileges at later stages of runtime, my crypt gets the first ones.
Maybe it fails for the last two prompts somewhere"
I told him it needs .Native crypt of course. But still it happens.
What if I disable the "Run as administrator function and crypt again, would the problem be solved?
Or is that because I enabled Startup function in the miner builder instead of crypter's startup function? I tested it as builder's startup function ON, Crypter's startup OFF
The text was updated successfully, but these errors were encountered: