Windows 7, update error 80080005: how to fix?

Although it is believed that the "seven" of the entire family of Windows operating systems is the most stable, nevertheless, and it is not immune from the emergence of critical failures and errors. The most common phenomenon in Windows 7 is the update error 80080005. What is the cause of this failure and how to fix it by the most accessible methods, read below.

Windows 7: update error 80080005. What is the cause of the failure?

If you do not take into account the failures associated with the virus impact, which can block the work of the "Update Center" services, the main cause of this error is called problems with the health of the component itself, responsible for installing the system update packages.

Of course, there is nothing particularly critical here, since all the major updates relate, as a rule, to security systems, however some applications and services may work incorrectly or not work at all. Fix 80080005 (error updating Windows 7) can be at least four simple methods, understanding of which none, even the most unprepared user, will not cause difficulties.

To begin with, if there was such a failure in the system, you should simply set the manual search for updates, because the automated module stopped working. If updates are found, they need to be installed. But in fact you will not be engaged each time manual update? Below you will find simple solutions to solve the problem within a few minutes.

Error 80080005 "Update Center" Windows 7: Hard Drive Check

In the simplest case, you just need to check the hard drive for errors. You can do this using the system drive properties menu.

However, many experts recommend using the command line check, which is called by the cmd combination in the console of the system menu "Run" (Win + R).

Here you enter the chkdisk / fc command: followed by pressing the enter key. This command allows you to find and fix system disk errors automatically. But that's not all.

Alternative verification option

When the error code 80080005 appears on the screen when upgrading Windows 7, it is better to use another command that allows you to restore system components.

In this case, the command line specifies sfc / scannow. Recovery of system services and files responsible for their operation will be done automatically. It does not even need an active Internet connection (simply the system itself creates backup copies of all the necessary elements and places them in hard disk partitions that are inaccessible to the user of any level, even if it is an administrator).

Installing the Latest Update Agent Version

If you do not install Windows 7 updates after that , you can use an alternative method, which is to download the latest version of Windows Update from the official Microsoft resource.

To do this, just go to the link to download the component, after which the site will offer to install the updated agent in online mode. After that, you will need to reboot the system.

Resetting the socket settings

But the methods suggested above, unfortunately, sometimes do not work. In Windows 7, upgrade error 80080005 may appear due to incorrect socket configuration. To resolve this type of problem, you must perform a full reset.

Again, we use the command line, where we register the netsh winsock reset catalog. After that, we overload the system. In theory, if the problem really was associated with these settings, in Windows 7, the 80080005 update error will no longer appear.

Working with the SoftwareDistribution folder

Finally, there may be another impartial situation. Updates in the manual mode are installed, but after the Windows update, the system still does not use automatic mode.

The SoftwareDistribution folder and its contents are to blame for this situation. The directory is located in the root directory of Windows on the system disk. It should be renamed (for example, in SoftwareDistribution.old), then restart the computer terminal. There is nothing wrong with assigning a different name to the system folder. During the restart process, Windows will create a new directory, importing data from the renamed folder.

You can rename from the command line, where the following is written:

• Net stop wuauserv;
• Rename c: \ windows \ SoftwareDistribution softwaredistribution.old;
• Net start wuauser;
• Exit.

Exactly the same result can be obtained if you right-click on the "Taskbar" to call the corresponding dispatcher, select the services tab and click on the services button where you need to find the update component, stop it, rename it, and start it again. In this case, the system will not be restarted (access to the "Task Manager" can be obtained through the "Start" console, where the taskmgr command is entered).

If nothing has helped

In theory, all the solutions considered in this or that case will allow to avoid the fact that in Windows 7 the error 80080005 appears again and again. However, it also happens that for some reason the service does not want to work properly anyway.

As a last resort, you can advise the use of a specialized utility DLL Suite, which installs or restores missing dynamic libraries.

If the application of this program does not work, you should download the installation distribution on the official site, but choose the system update, not the installation. Who knows, some service pack might be corrupted. By the way, the updates themselves can also play a cruel joke. Therefore, it may be necessary to remove some of them, and precisely those that have been installed recently, after which problems began to appear.

In extreme cases, you can use the special utility Microsoft FixIt !, which can also automatically correct errors related to the administration of the components of the upgrade system. Only to run it, you must first completely disable the automatic update. Otherwise, the program itself at the installation stage will give a message that the user has some problems with the Internet connection, and it is simply not possible to download the necessary files from the Web. By the way, not all users remember that. So it turns out that the program seems to be taken from a reliable source, but the components of Microsoft conflict only among themselves. Nonsense? Yes! But it happens in practice.

Conclusion

Actually, that's all, as to the problem of the occurrence of a failure when updating the system. Here, the most common failures and methods for their elimination were considered. But even the developers themselves can not unequivocally answer the question of why such errors occur even in "clean" systems. So there can be a lot of reasons, as well as ways of eliminating the consequences.

But taking into account all of the above, in practice in most cases helps to check the disk with the restoration of system components and rename the system folder responsible for updating the system. All other decisions are in some way secondary, although in some cases they may have an effect.

On the other hand, you first need to find out the cause of the failure, and only then apply one solution or an integrated approach to solving the problem. But in practice, two methods will suffice (without affecting the reset of the socket service, since this situation is extremely rare). However, there is little that can be, therefore, all proposed solutions should not be discarded.