Mrrrr's Forum (VIEW ONLY)
Un forum care ofera solutii pentru unele probleme legate in general de PC. Pe langa solutii, aici puteti gasi si alte lucruri interesante // A forum that offers solutions to some PC related issues. Besides these, here you can find more interesting stuff.
|
Lista Forumurilor Pe Tematici
|
Mrrrr's Forum (VIEW ONLY) | Reguli | Inregistrare | Login
POZE MRRRR'S FORUM (VIEW ONLY)
Nu sunteti logat.
|
Nou pe simpatie:
deea_printesa
 | Femeie
24 ani
Dolj
cauta Barbat
24 - 48 ani |
|
Mrrrr
AdMiN
 Inregistrat: acum 17 ani
Postari: 2186
|
|
1. Open the Command Prompt as Administrator and run the Tasklist command, it will show you a list of all the running processes.
2. To view the processes, type Taskview and hit Enter.
3. To kill any particular process use the Taskkill command. For example to kill Chrome, run the command as:
Taskkill /IM chrome.exe /F
Where /F is used to kill the process forcefully.
4. You can also kill any particular process by using its ID, the tasklist command displays the process ID’s as well. You can see the PID column in the screenshot. To kill any process using its ID, run the command as:
Taskkill /PID 2704 /F
5. Now to kill multiple processes simultaneously, run the above command with the PID’s of all the processes followed by spaces
Taskkill /PID 2704 5472 4344 /F
Source:
_______________________________________
|
|
| pus acum 4 ani |
|
Mrrrr
AdMiN
Inregistrat: acum 17 ani
Postari: 2186
|
|
Do this with powershell & wildcards:
Stop-Process -name "*Autohotkey*"
More info:
_______________________________________
|
|
| pus acum 1 an |
|
Mrrrr
AdMiN
Inregistrat: acum 17 ani
Postari: 2186
|
|
Convert your powershell scripts to EXE with:
Usage (by me):
1) Put the .ps1 script you wanna convert to .exe and the .ico file in the same directory as ps2exe.ps1.
2) Open Powershell as administrator and navigate to the folder where you have the files above
3) Set-ExecutionPolicy RemoteSigned
When asked about Execution Policy Change, ansewer Y
This disables the script execution policy that says you cannot run scripts as they could be potentially dangerous. We'll re-enable it at the end.
4) .\ps2exe.ps1 .\KillO.ps1 .\KillO.exe -noconsole -iconFile KillO.ico
You should receive something similar to:
Reading input file C:\Users\Mrrrr\Desktop\ps2exe-gui-main\KillO.ps1
Compiling file...
Output file C:\Users\Mrrrr\Desktop\ps2exe-gui-main\KillO.exe written
5) Set-ExecutionPolicy Restricted
When asked about Execution Policy Change, answer Y
This enables the script execution policy that says you cannot run scripts as they could be potentially dangerous. Now you are safe again.
You can test safety by trying to run the 4) command. If you receive an error containing the following text, you're good:
"\ps2exe.ps1 cannot be loaded because running scripts is disabled on this system."
_______________________________________
|
|
| pus acum 1 an |
|