Windows can not connect to the service. How to fix it

Not often, of course, but sometimes users of computer systems based on Windows face an unpleasant situation. The system reports that Windows can not connect to the service responsible for any process. Consider the most common variants of errors and the corresponding methods for correcting them.

Windows can not connect to the service: probable situations

It is considered that, among all the errors that occur, the most significant failures to be corrected are the two main ones: the inability to start the System Event Notification Service (the second name is SENS) and to the system component responsible for installing any type of software on the system. It is not difficult to guess that in the second case it is 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 that when the notification component is disabled, the system simply limits the rights of the user who entered not under the Administrator account. Equally, this also concerns the problems associated with the fact that the Windows Installer service is disabled. Hence the simplest conclusion: these components must either be enabled or restarted.

The simplest method of fixing a failure

So, let's look at the simplest situation. If the user knows exactly when the failure occurred (before that everything worked fine), you can try to just restore the system. Note, now we are not talking about the reasons that caused the failure or modification of settings due to virus exposure. A check for threats is not discussed. The user himself must understand that this is a paramount task in terms of security.

To roll back the system, you must enter the Recovery Recovery Center, where you can use the appropriate section. In this case, if there is no control point in the presented list, you need to expand the list through the display line of all available points (use another rollback point). We select the time before the first message that Windows could not connect to the SENS or Installer service, and roll back the system (the reboot will happen automatically).

Troubleshooting System Event Notifications

This problem is almost the most common. Disable Windows services, change their startup parameters or settings, and could viruses, and some programs installed in the system. We assume that there are no viruses in the system, and recovery does not help.

To fix this problem, you will have to make a complete reset of some settings of this system component, for which you will need to run a command prompt 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. At the command line, you should write the following:

• Route -f;
• Netsh winsock reset.

To be true, the two above commands are used, but in most cases you can enter only the second one. After the commands are triggered, a reboot is required.

Problems with the Windows Installer service

With the installer, the situation is somewhat more complicated. There can be two variants of the development of events: either the user does not have administrator rights, or the service is simply disabled.

For the first situation, the most logical solution would be to log on as an administrator or to assign the current account administrator rights. However, such a solution may not work, and the system will again report that Windows can not connect to the installer's service. This only indicates that the component itself is in an inactive state.

Troubleshoot installer problems

Now let's see how to start the Windows Installer service (the solution is applicable for all services and problems with their disabled state). In this case, although it is a question of a specific component, an understanding of this question may be useful later when correcting other errors.

Access to the management section of these components can be obtained from the "Run" menu by entering the services.msc command in the console line. You can also enter this section through the computer management menu.

After logging in, look at the right side of the editor, where the local Windows services are located. Here you need to find a line with the name of the component you are looking for (in this case it's the Windows Installer) and look at the type of launch that was set. The value must be set to a manual type. If it is different (usually an automatic type is installed), double click to call the additional settings window. On the corresponding tab, select the desired value from the drop-down list, and then save the changes made. In principle, you do not need to reboot the device in most cases, but for accuracy it is better to make a full restart, and then to see how the system will behave.

You could also try changing the same settings in the system registry, which, in general, duplicates the parameters that are installed in this section. But this method is more time-consuming and long, and in the absence of special knowledge, it is better not to climb into the register without the need for a register.

Correcting errors with the help of an automated utility

Finally, if the above troubleshooting methods did not help, which is often enough, and the notification that Windows can not connect to such and such a service appears again and again, you can use the automated remediation tools offered for Download and install on the official Microsoft support page.

In this case we are talking about a small program called Microsoft Fix It. Another method to eliminate the problem may be to download the installer's distribution distribution from the same resource, and then integrate it into the system. True, it must be produced exclusively by the administrator, possibly even through the command line.

Conclusion

Finally, it should be noted that only the two most frequently encountered situations and the simplest methods of eliminating the problems that have arisen here were considered. In some cases, when using the command line to reset the parameters of the commands used, there can be much more, and after they are executed, you will have to dig into the network settings. This decision was not considered only because it is much more complicated and most users simply will not be useful. In the simplest version, one command is enough, a maximum of two. Additionally, you could check the integrity of the system components through 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, such problems are most often manifested in the version of Windows Vista, which is already criticized for the fact that it is still under-developed and "raw" even with the updates being installed.