The problem with the connection to the remote PC about meterpeter

[r00t-3xp10it]

Let's see if i understand your problem ...

• 1º - you have used meterpeter C2 to create the Client.ps1
• 2º - you have used ps2exe.ps1 to compile the client.ps1 into client.exe

Remark: PS2EXE does not really convert PS scripts to standalone executables ..
what it really does its to create a C++ program and then use the .NET framework to compile it to executable ..
( I have been facing bugs also using the compiled executable with meterpeter mimratz post-scripts )

Thats the reason why iam starting to writte a new WIKI to describe this kind of issues ..
About beacon home we can use schtasks native appl to beacon home from xx to xx minutes of interval:
meterpeter - working with remote tasks

[ru000]

1º and 2º -- completely yes

About beacon home we can use schtasks native appl to beacon home from xx to xx minutes of interval:

Yes, I did the following manipulations with the remote PC and for some time it still "rang" every 3 hours and the session was active inside the C0b@ltStr1ke even after the computer was restarted. But at some point, the session disappeared from coba1t and the remote computer no longer rings to my Linux server. And I don't understand what could have gone wrong.

[r00t-3xp10it]

Possible causes

• 1º - Schtasks.exe in some systems its configurated to NOT run tasks under battery usage.
  

• 2º - Maybee the task is config to last only one day ..

• 3º - AV daylly check migth have deleted task or payload ..

• 4º - the standalone executable created by PS2EXE malfunctions ...
  Thats the reason why iam writting this [ WIKI ]

---

And .. the 2º screenshot Its a Privilege escalation technic rigth ??
maybee the vulnerable process have stoped after restart .. and no longer executes the priv escal and payload ..

Final Notes:

You need to review all the steps done in exploitation (one-by-one in sequence) to figure it out what went wrong ..