Нечасто, конечно, но иногда пользователи Windows based computer systems face an unpleasant situation. The system reports that Windows cannot connect to the service responsible for some process. Consider the most common variants of errors and appropriate methods for correcting them.
Windows can not connect to the service: likely situations
It is believed that among all the errors that occurThe most significant failures to be corrected are two main ones: the inability to start the system event notification service (the second name is SENS) and the system component responsible for installing any type of software in the system. It is not hard to guess that in the second case we are talking about the Windows Installer service, although not only this component, but also other types of installers can be used as an installer.
In the first situation, the problem is thatwhen the notification component is disabled, the system simply limits the rights of a user who is not logged in as an Administrator account. Equally, this also applies to problems related to the fact that the Windows Installer service is disabled. Hence the simplest conclusion: these components must either be turned on or restarted.
The easiest way to fix a crash
So, let's look at the simplest situation.If the user knows for sure at what point the failure occurred (before that everything worked fine), you can simply try to restore the system. Note, now we are not talking about the reasons that caused the failure or change settings due to viral exposure. Check for threats is not discussed. The user himself must understand that this is of paramount importance in terms of security.
Для отката системы следует войти в «Центр archive recovery ", where to use the appropriate section. In this case, if the control point in the presented list is missing, you need to expand the list through the line showing all available points (use another rollback point). Select the time before the first message that Windows failed to connect to the SENS or Installer service, and rolls back the system (the restart will occur automatically).
Troubleshooting system event notification service issues
This problem is almost the mostcommon. Disable Windows services, change their startup settings or settings could and viruses, and some programs installed in the system. We assume that there are no viruses in the system, but recovery does not help.
To resolve this problem will have to docomplete reset of some settings of this system component, for which you will need to run the command line on behalf of the Administrator. This is done by typing cmd in the Run console, a quick call is made using the Win + R keys. On the command line, you should write the following:
- route -f;
- netsh winsock reset.
For correctness, the two commands above are used, but in most cases only the second one can be entered. After the commands are triggered, you will need to reboot.
Windows Installer Issues
The situation with the installer is somewhat more complicated. There may be two scenarios: either the user does not have administrative rights, or the service is simply disabled.
For the first situation the most logical solutionwill be logged in under the administrator account or assigning administrator rights to the current account. However, this solution may not work, and the system will again report that Windows cannot connect to the installer service. It says only that the component itself is in an inactive state.
Troubleshooting Installer Issues
Now let's see how to start the Windows service.Installer (the solution is applicable to all services and problems with their disabled state). In this case, although we are talking about a specific component, an understanding of this issue may be useful later in correcting other errors.
Access to the management section of these components can be obtained in the "Run" menu by entering the services.msc command in the console line. You can also enter this section through the computer management menu.
После входа смотрим на правую часть редактора, where are local Windows services. Here you need to find the line with the name of the component you are looking for (in our case, this is the Windows installer) and look at the launch type that is displayed. The value must be set to manual type. If it is different (the automatic type is usually set), double-click on the additional settings window. On the appropriate tab from the drop-down list, select the desired value, and then save the changes. In principle, in most cases it is not necessary to reboot the device, but for fidelity it is better to make a complete restart, and then see how the system behaves.
One could still try to producechange of similar settings in the system registry, which, in general, duplicates the parameters set in this section. But this method is more time consuming and long, and in the absence of special knowledge without the need for a registry, it is better not to go.
Error correction using an automated utility
Finally, if the above remediesproblems did not help, which also happens often enough, and the notification that Windows cannot connect to the service such and such, appears again and again, you can use automated means of correcting the situation offered for download and installation on the official page Microsoft support.
In this case we are talking about a small program.called Microsoft Fix It. Another way to fix the problem is to boot from the same resource of the installation distribution kit of the installer with subsequent integration into the system. True, it should only be done by the administrator, perhaps even through the command line.
Conclusion
Напоследок стоит отметить, что здесь были Only two of the most frequently encountered situations and the simplest methods of eliminating the problems encountered are considered. In some cases, when using the command line to reset the parameters of the commands used, it may be much more, and after executing them you will have to dig into the network settings. Such a solution was not considered solely because it is much more complicated and most users simply do not need it. In the simplest form, one command is enough, a maximum of two. Additionally, it would be possible to verify the integrity of system components via the sfc / scannow command, but, as practice shows, it is used, so to speak, just in case.
By the way, for some reason, according to statistics, suchThe problems most often manifest themselves in the version of Windows Vista, which is already criticized for the fact that even with updates being installed, it still remains unfinished and "raw."
