Although it is believed that the "seven" of the entire family of Windows operating systems is the most stable, however, and it is not immune from the emergence of critical failures and errors. The most common occurrence in Windows 7 is update error 80080005. What is the reason for this failure and how to fix it using the most affordable methods, read below.
Windows 7: update error 80080005. What is the cause of the failure?
If you do not take into account failures associated with a virus exposure that can block the operation of the Update Center services, the main cause of this error is the problems with the operability of the component itself, which is responsible for installing the system update packages.
Of course, there is nothing particularly critical here, since all major updates concern, as a rule, the security system, however, some applications and services may work incorrectly or may not work at all. There are at least four simple ways to fix 80080005 (Windows 7 update error), at least one of which, even the most unprepared user, will not cause difficulties.
To begin with, if such a crash occurred in the system, you just need to specify a manual search for updates, since the automated module stopped working. If updates are found, they just need to be installed. But you will not be engaged in a manual update every time? Below are simple solutions to fix the problem in a few minutes.
Windows 7 Update Center Error 80080005: Hard Disk 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 a command line check, which is invoked by cmd in the Run menu of the system menu (Win + R).
Here the chkdisk / fc command is entered: followed by pressing the enter key. This command allows you to find and fix system disk errors automatically. But that is not all.
Alternative check option
When the error code 80080005 appears on the screen when updating Windows 7, it is better to use another command that allows you to restore system components.
In this case, sfc / scannow is written on the command line. Recovery of system services and those responsible for their performance will be done automatically. In this case, you do not even need an active Internet connection (just the system itself creates backup copies of all the necessary elements and places them on the hard disk partitions inaccessible to a user of any level, even if he is an administrator).
Install the latest update agent version
If after that Windows 7 updates are not installed, you can use an alternative method, which is to download the latest version of Windows Update from the official Microsoft resource.
To do this, simply follow 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.
Reset socket settings
But the methods proposed above, unfortunately, sometimes may not work. On Windows 7, update error 80080005 may appear due to incorrect socket settings. To fix this type of problem, you need to perform a full reset.
Again, use the command line, where we write netsh winsock reset catalog. After that we reboot the system. In theory, if the problem was really related to these settings, in Windows 7 update error 80080005 will no longer appear.
Working with the SoftwareDistribution folder
Finally, there may be another unpleasant situation. Updates in manual mode are installed, but after updating Windows, 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 Windows root directory on the system drive. It should be renamed (for example, in SoftwareDistribution.old), and then restart the computer terminal. There is nothing wrong with assigning a different name to the system folder. During the restart, 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.
You can get exactly the same result if you right-click on the “Taskbar” to call the appropriate dispatcher, select the services tab and click on the services button where you need to find the update component, stop it, rename it and restart it. In this case, you do not need to restart the system (access to the “Task Manager” can also be obtained through the “Start” console, where the taskmgr command is entered).
If all else fails
In theory, all the solutions discussed in this or that case will help to avoid the fact that in Windows 7 error 80080005 appears again and again. However, it also happens that for some reason, the service still does not want to work correctly.
As a last resort, you can recommend the use of a specialized utility DLL Suite, which installs or restores missing dynamic libraries.
If the application of this program does not work, the installation site should be downloaded on the official website, but choose not the installation, but the system update. Who knows, some service pack may be damaged. By the way, the installed updates themselves can also play a trick. Therefore, you may have to remove some of them, especially those that have been installed recently, after which problems began to appear.
In the worst case scenario, you can use the special Microsoft FixIt! Utility, which can also automatically fix errors related to administering the components of the update system. Only to start it, you first need to completely disable the automatic update. Otherwise, the program itself at the installation stage will display a message stating 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 this, by the way. So it turns out that the program seems to be taken from a reliable source, and Microsoft components conflict exclusively with each other. Nonsense? Yes! But it happens in practice.
Conclusion
Actually, that’s all that concerns the problem of a crash when updating the system. Here the most common failures and methods for eliminating them were considered. But even the developers themselves clearly cannot answer the question of why such errors occur even in "clean" systems. So there can be a lot of reasons, as well as ways to eliminate the consequences.
But taking into account all the above, in practice, in most cases, checking the disk with the restoration of system components and renaming the system folder responsible for updating the system helps in most cases. All other decisions are in some ways 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 be enough (without affecting the reset of the socket service, since this situation is extremely rare). However, you never know what could be, therefore, to discount all the proposed solutions is not worth it.