The installer of Windows modules is one of the most important system services of all the latest versions of the system, but many users are incredibly confused by the fact that on its part there is very often an increased load on system resources. In general, if the load manifests itself briefly, this is normal. If the installer process starts earlier than the operating system itself, or in the process of its operation, the impact on the processor and RAM is very strong, you will have to take action. But far from everyone knows what this component is and what actions can be applied to it. The solutions proposed below will allow you to get rid of increased loads. But first you need to find out why, in fact, this service is needed, and why it is constantly in an active state.
What is a windows module installer?
If we talk about the purpose of this system component, it should be mentioned that it is present in all versions of Windows for which updates are provided. It is for their integration into the OS environment that the service is responsible. True, the service of installers of Windows modules in the XP version was called Windows Installer, and in the seventh modification and above it was renamed TrustedInstaller. In addition, she received additional extended super administrator rights, without the consent of which it may be impossible to install some software products. Moreover, even disabling the account of the so-called superuser hidden from the eyes does not give anything, and the module itself and the active process responsible for it in the form of the TiWorker.exe executable file still remains active.
Business is not limited to updates only, since an increase in the load on system resources can also be associated with viral exposure. Despite the fact that the file itself in the system cannot be deleted, moved or renamed, some viruses can infect it, at the same time disguising their own executable applets as an active system service. If there is a suspicion about such a phenomenon, it is better to immediately check the computer for virus threats. As for fixing problems with the installer, let's see why there is an increase in the load on system resources, and what can be done to correct the situation using regular means.
In passing, pay attention to the fact that the installer service for Windows XP modules usually does not cause problems, since it is inactive (sometimes it is not even in a “clean” installation distribution without accompanying service packs). You can get full access to it or restore functionality by installing the optional KB942288 update package or by downloading and then registering additional libraries and related components yourself. But further we will proceed from the fact that versions 7 and higher are used as the current operating system, since it is in them that such a problem manifests itself most often.
Why does the Windows module installer load the processor?
As you probably already understand, working with installing updates is far from the greatest strength of all Windows systems. When installing them, quite often there are a lot of errors that can even lead to the appearance of a blue screen or to a failure of the entire system. If it is noticed that the installer of Windows modules loads willow resources when the OS starts, and during its operation (this usually manifests itself as a slowdown of the computer and a decrease in Internet access speed), this only means that the active process is trying to integrate the found updates into the system, but for some reason, can not do this, because of what appears as if a looped-through task execution.
How to reduce the load on resources in the simplest way?
So, how to reduce the load from the installer of Windows modules using the simplest methods? To begin with, you can use the system troubleshooting tool, the link to which is located in the standard "Control Panel".
From the list you should select the components of interest to us (as a rule, these are the services of the Update Center, intelligent background transmission and system maintenance), and then activate the troubleshooting. It is possible that the found failures will be fixed. However, this does not always help, therefore, in most cases it is necessary to correct the situation independently.
Actions with cache and system updates
In order not to completely disable the installer of Windows modules, the functioning of which is often just necessary, you can clear the cache of updates (temporary downloaded files) that are dead weight on the hard drive. The directory for their storage has a fixed size and is set by the system itself, so when the limit is exceeded, downloaded packages can not be placed there. To do this, completely disconnect the Internet connection, invoke the command line (cmd) on behalf of the administrator, and then specify two lines for execution:
- net stop wuauserv;
- net stop bits.
After executing the commands, find the SoftwareDistribution directory on the hard drive in the root directory of the system, delete all the components located there, and then in the command console, execute the reverse commands to enable the update:
- net start bits;
- net start wuauserv.
After completing all the steps, restart the computer, after which you will need to activate Internet access again, set up a manual search for updates and install them.
Full service shutdown
If the above actions failed, the installer service for Windows modules can be completely disabled.
To perform such operations, you need to call the appropriate section by entering the services.msc command in the "Run" console, find the item you are looking for, double-click to enter the parameter editing, and then (very important) by stopping the service, first stop the service, and only then from the drop-down list just above, select the disabled startup type. After saving the changes, it is advisable to perform a complete restart of the system.
Actions with directories and files
Finally, another method of deactivating a service, but for performing actions with specific files and folders, is to go to the security tab through the properties of the selected component in Explorer and change the owner (TrustedInstaller or SYSTEM) to your or administrator account , and then install the entire set of permissions for possible actions by marking the corresponding items in the settings with checkboxes.
After this, the obstacles on the part of the installer, for example, when trying to install some program, will be eliminated.