Not often, of course, but sometimes you can find situations when, after closing the program in the Task Manager, the process responsible for its functioning does not end, or some additional (related) application services continue to work. In this case, the system, in addition to everything, can report that the user does not have enough rights to complete a certain process (access denied). Why this happens and how to stop unnecessary or freezing programs, read the material below.
Process does not terminate in Task Manager (permission denied). Why?
To understand which solution to solve a problem that has arisen to use in each specific case, you first need to find out the reasons due to which they arise. Why doesn't the process end in the "Task Manager" indicating the lack of access rights?
Indeed, sometimes this may be due to the fact that the user is not logged in as an administrator and is trying to terminate a critical system service or process started by another user. However, the impossibility of stopping the operation of some application is mainly associated not even with system processes, but with programs that could be installed on the user's computer spontaneously (viruses, adware, etc.). Usually they are the ones that can block the shutdown. But it is quite easy to deal with such manifestations of behavior of both system and user programs or services.
System reboot
If the process in the "Task Manager" does not end, what should I do first? As a rule, ordinary users act quite simply. If for some reason the process does not end in the Windows 10 Task Manager, they simply reboot the system. It is clear that a full restart leads to a stop of all services. But what if, after a reboot, the process is activated again? But some processes that start with the system cannot be tracked even in the standard startup section.
However, if the user is logged in not under the administrator account, but under his own account, as is already clear, you just need to change the user.
If you do not want to constantly jump from one record to another, you can disable the administrator account altogether by typing the command in the command line"net user Administrator active:no" (without quotes). After that, all programs will start only with administrator rights (for some applications, even the UAC security warnings that annoy many users will not be issued).
End active processes via command line
But the above actions may not always give a positive effect. What to do if a process does not end in the Task Manager, which, say, overloads the central processor or uses RAM too hard? In such a situation, the command console (cmd) will be the best tool among those that are available in Windows systems.
It must be run as administrator (if the superuser account is not disabled), and then use the taskkill command (all information about additional attributes can be viewed by entering the line "taskkill /?".
Of the entire list, we are most interested in the "/F" and "/IM" attributes, which are added after the main command. What does it look like? Let's suppose that the Google Chrome process does not end in the Task Manager. The command to force stop the application will look like this: "taskkill /F /IM Chrome.exe" (again, without quotes). As is already clear, such a solution is acceptable for program executable files. If you use the additional key "/T", when you enter the main command to shut down the selected application, all child applications will be automatically completed.processes.
Stop processes with IDs
If the process that was selected by the user does not end in this way in the "Task Manager", for example, if the name of the executable file of the problematic program or service is entered incorrectly, the process can be stopped by specifying the identifier.
It can be viewed in the "Task Manager" itself, additionally activating the display of the column with the process ID. The main command in this case will take the following form: "taskkill / F PID 0000", where 0000 is the process ID defined in the "Task Manager".
Microsoft tip
In principle, the problem associated with the fact that the process of a program does not end in the "Task Manager" can be solved by following the advice of Microsoft specialists, which are published on the support page. The bottom line is to download a special archive from the site containing the PSTools toolkit, then unzip it to your hard drive and move the PsExec.exe file or the PsExec64.exe object, depending on the system architecture, to the root of the system partition (drive "C"), and then through the command console run the command "c:\psexec -i -d -s taskmgr.exe" (without quotes). After that, in the "Task Manager" you will need to perform all the necessary actions related to stopping certain processes, then close the "Manager" and delete the original PsExec file from the system partition.
Note: it is recommended to use this method even on the corporate website only at your own risk.
Using Process Explorer
It is much easier to use a small application Process Explorer, which is an alternative to the "Task Manager", but with advanced features. The advantage of this program is that you do not need to install it on your hard drive, since the application is initially portable and runs from a single executable file. After starting the program, it is enough to select the desired non-terminating process in it or even the whole process tree with child applets by selecting the Kill Process or Kill Process Tree commands from the RMB menu.
In addition to "killing" unnecessary processes and tasks, this utility also provides additional information. So, for example, if this is required, it is quite easy to find out which program is running this or that process.
Unblocking access to process files
Finally, if it is impossible to terminate certain processes only because access to the file responsible for it is blocked, it may very well be possible to correct the situation by using the Unlocker utility.
First, as is already clear, access to the original file is restored (you can find it directly in the "Task Manager" by selecting the view file location from the RMB menu), and then the process ends in the usual way.
Viral exposure issues
Viruses, unfortunately, restrict access to stop processes and services toocan. And this is not always directly related to the virus applets themselves. If this situation is observed, it is recommended to first check the system with some portable antivirus, and if it is impossible to neutralize threats, turn to the Kaspersky Rescue Disk program, with which you can boot even before the system starts from removable media, and then perform a deep scan, which includes even RAM itself.
Summary
That, in fact, is all that concerns the forced termination of processes in the "Task Manager". As for the best tool, the simplest one seems to be the Process Explorer alternative manager. If there is no such program at hand, the command line will do. The only condition for executing all the above commands is to start the console itself with administrator rights.
