Error 80070002 when updating Windows: patch method

Quite often, users of Windows 7 (and not only her) have problems when the automatic system update is turned on, but for some reason it does not work, and "Windows" issues a message in which the error 80070002 is indicated. Let's see why it arises, And tell you how to fix it with the simplest methods.

Why does error 80070002 appear?

Strictly speaking, there can be a lot of reasons for this failure, but in general terms it all boils down to the fact that the service responsible for searching for and installing update packages is either working incorrectly or is in conflict with other processes.

That's where the error 80070002 (Windows 7) appears when installing updates. In this regard, and you can offer several basic solutions on how to get rid of failures of this type, the more so that it is not so difficult to do, as it may seem at first glance. A little patience, and everything will turn out.

Code 80070002 (error updating Windows 7): how to fix it in the simplest way?

To begin with, consider, so to speak, the classic version. So, we assume that the system issued an error 80070002 when installing updates to Windows 7. What should I do? In the simplest version of the methodology for solving this problem, we use the "Update Center", access to which can be obtained directly from the standard "Control Panel".

Here you need to use the manual update search function. It is very likely that if they are found and installed without any complaints, then everything will fall into place, and error 80070002 will not appear more.

Date and time settings

There is one more common reason for the occurrence of such a failure - the incorrectly set date and time. After all, when trying to update what happens? The system date is compared with the parameters of the center on the remote server and with the date of the update releases themselves. As a consequence, with this discrepancy, packages are not installed.

How do I fix 80070002 in this situation? There is nothing easier. You just need to set the correct current settings. But here we should pay attention to one thing: changing these should not be done in the system itself, as some users do, calling the parameters by clicking on the icon in the system tray. This approach will not work.

Make settings only in the BIOS. When you enter the main section there is such a line. After that, you need to save the changes (usually done with the F10 key), and then the system will reboot with the new settings. If the reason was exactly this, then the update process will go without any problems.

Using the restart of the update service

Now we will consider a more complicated procedure, which excludes the appearance of failures in most cases. To use it, you need to enter the services.msc command in the "Run" menu bar (Win + R) and go to the appropriate editor.

Here you need to find the appropriate service of the update center and stop it. Now in the root directory of the system, we find the SoftwareDistribution folder and rename it to SoftwareDistributionOLD, and then agree with the User Account Control warning .

Now go back to the services window and turn on the Update Center process again. Again, if the update does not start automatically, you can use manual search and installation.

Third-party utilities

Another solution, by means of which bug 80070002 is corrected, is the use of specialized utilities that allow to perform such actions completely in automatic mode.

For this, the "native" Microsoft Fix It Tool is best suited. Just run the application, then follow the instructions of the "Wizard", which will first perform a full scan of the system for problems, and then fix the problems found. Otherwise, other problems can be found along the way, again with their subsequent correction. This, in fact, is the universality of this utility.

What can be more?

Of course, this is far from being all solutions that can be used in the event of such an error. As practice shows, sometimes problems can be connected even with the installed Microsoft Office package (for the worse the 2003 release differs). What to do in this situation? Yes, just remove it, and instead put it, say, version 2007 or even higher. But, in principle, you can use all of the above methods as general solutions for all cases.

In fact, in a sense, it's better to perform each step, except for setting the date and time settings, if they are correct. In any case, the method of restarting the service is universal. And for those who do not want to spend time and dig into these settings, the standard "Microsoft" utility is also perfect. However, which exactly way to use depends on the user's preferences.

It remains to add that this is not all the reasons for the failure of the update. Who knows, maybe the virus got into the system, and the error is a consequence of his activity. Maybe somewhere there are conflicts at the system level in the sense of problems associated with the newly installed software. Yes, you never know what can be. In extreme cases, if nothing helps at all, you can try to roll back the system to the previous state, and then see how the above service will behave.