As you know, the service for automatically installing updates on Windows systems, starting with the seventh version, often crashes. Among the most common errors is the appearance of a message with the code 0x80070005 (Windows 7). How to fix this situation, now let's see. Please note immediately that this problem is not unique to the Seven. It can equally make itself felt in the eighth and tenth versions.
Windows Update Error 0x80070005. Windows 7: Causes of Failure
It is believed that in order to determine the means of eliminating the disease, you need to know the root causes of its appearance. The error of the “Update Center” Windows 0x80070005 (we take Windows 7 as an example, no more) can occur exclusively in cases where the system cannot access some system files and components, or the user does not have the necessary access rights.
The most common situations when the system issues a warning that access to a specific object is denied may be the following:
- attempt to download and install updates;
- Windows activation crashes
- System Restore.
As you can see, the main emphasis is on the inability to access files and OS components. It would seem easier to use the Administrator account? But no. The problem, despite its apparent simplicity, is much deeper. And one of the most unpleasant situations is precisely the one where the error 0x80070005 (Windows 7) occurs. How to fix this failure, now let's see. True, in this case, standard methods may not work, so you have to strain your brains.
Automatic adjustment of parameters
The first way to fix the problem is to use automatic error correction. It is about checking the integrity of system components.
First, we call the command line by writing cmd in the Run (Win + R) console (required on behalf of the administrator). Then we introduce three commands that allow us to eliminate the problem in the automatic mode by the means of the system at the first stage. First, we write the sfc / scannow command, and then two more: dism / online / cleanup-image / scanhealth and dism / online / cleanup-image / restorehealth. The probability of correcting the situation is quite high, although in some cases it may not work (if the integrity of the system components is not broken).
Windows Update Error 0x80070005. Windows 7: how to fix a crash using SubInACL?
One of the most universal tools, many experts and users call a small utility that can be downloaded on the official Microsoft website as an executable installation file SubInACL.exe.
You need to install the program in the system according to strictly defined rules, because if you install it incorrectly, you may see a failure with the code 0x80070005 (Windows 7). How to fix the error in this way?
First, run the downloaded installer with administrator rights and specify the directory located in the root of the system partition of the disk as the destination folder (for example, C: / subinacl). It is a companion component for script execution, and not a means to fix the problem.
After that, the most difficult begins. In the standard Notepad, you need to register the code that you see in the picture below.
The created file must be saved in the executable BAT format in any convenient location. Then, by right-clicking on the object, call up the submenu and select launch as Administrator. When the execution of the script ends, the word “Gotovo” appears on the screen of the command console. Next, you just need to press any key to exit, restart the computer and repeat the operation that caused the failure 0x80070005 (Windows 7). How to fix the situation is clear. But in some cases, the script may not work. Not to mention the reasons, we note that you can apply other scripts, one of which is shown below.
True, according to experienced users, the implementation of this particular scenario can lead to the inoperability of the entire system, so you should use it only at your own peril and risk.
Error correction when trying to restore the system
It also happens that restoring a system at a certain stage entails the appearance of error 0x80070005 (Windows 7). How to fix the failure of the recovery process? First, for the account, you need to check the access rights to the System Volume Information directory (it is hidden, so you need to enable the display of the corresponding objects in the view menu). If there is a checkmark opposite the item "Read Only", it must be removed.
In some cases, you can use access to the system configuration via the msconfig line in the Run console, where on the general tab, uncheck all the boxes and apply either a diagnostic or selective launch.
Finally, you can try to start the services editor (services.msc) and set the automatic startup type for the shadow copy component .
In the most recent version, it is supposed to reset the repository with renaming the initial folder. First, we reboot in safe mode and enter net stop winmgmt on the command line, after which we find the wbem folder in the System32 directory of the system’s main directory, and in it the repository directory, which you need to give a different name to (just add the Old name to the name).
Next, we reboot the system again (again in safe mode), use the command line and write the line of the primary stop command. After it we enter winmgmt / resetRepository. After all that has been done, we reboot the system as usual. The problem will disappear.
Conclusion
As you can already see, this situation is not one of those that can be fixed with standard, simple methods. If such an error occurs, you really have to spend a little time and effort to bring the system to life. However, all the described actions in most cases help 100%, apart from the automatic correction of errors, which may not work. If nothing helps at all, you need to check the free space on your hard drive. Perhaps this is the limiting factor.