Absolutely all users know that Windows systems are prone to unexpected crashes and errors more often than other OSs. One of the most common is a failure, the message about which contains error code 0x80070005. In this case, Windows 7 or any other version of the OS is used on a computer, it is not so important, it is important that for some reason the operating system is denied access to a remote server or performing one or another action. The reasons for this phenomenon can be quite a lot, as well as methods for solving the problem.
What does this failure indicate?
This type of error is thought to occur in several situations. Most often, its occurrence is associated with an attempt to install updates, activation or restoration of the system. However, these are far from all cases of its manifestation. The fact is that even when registering dynamic libraries, the code will be the same, but the failure descriptions will be different.
However, in the general case, error code 0x80070005 says that the system is trying to access the Microsoft server or another resource (for example, when installing games), but receives a ban in response. On the other hand, such a failure may be associated with the installation of the vbscript.dll and jsscript.dll libraries, in which they are registered in the system in manual mode.
Further, we offer several solutions that, although not guaranteed, will help to rectify the situation. But it is not guaranteed because the message may contain the same code, and the root causes may be different.
If the cause is antivirus ...
So, if you received an error code 0x80070005 (Windows 8) during the upgrade, the reason may be the installed full-time antivirus, which is able to block some system processes.
In this case, you need to deactivate it for a few minutes and repeat the update by manually searching for updates. Even better is to go into the basic settings and disable self-defense. Perhaps this will work. However, in most cases the reason is not this.
Error code 0x80070005: how to fix by online system recovery
It may well be that the appearance of a failure is associated with a violation of the integrity of the system components. They need to be checked. To do this, use the command line, which must be run exclusively on behalf of the administrator or a local registration account with such rights.
The first step is to write the sfc / scannow command. If, upon completion of the process, the failure appears again, then with a constant connection to the Internet, you can check or restore the system online.
To do this, the command shown in the image above is used in the same console. If this does not work, move on.
Using SublnACL Utility and Scripts
Many experts call one of the most powerful troubleshooting tools containing error code 0x80070005 (Windows 8.1 for example) a small program called SublnACL, which can be downloaded directly from the official Microsoft resource as a single executable EXE file.
When installing as a location, it is desirable to specify the root of the system partition or create a folder of the same name on the system drive. After that, you should use the standard Notepad and write the text there, as in the image below.
The created file must be saved in BAT format by selecting “All files” in the object type, and manually specify the extension through the point.
You need to save the file in the same folder where the above utility was installed. Now, through RMB, you need to run the saved BAT file on behalf of the administrator. After execution, close the command console, reboot the system and try to perform the operation, the execution of which produced an error code 0x80070005.
If the failure appears again, you can change the contents of the BAT file and write the text shown in the photo below.
After that, the procedures described for the first script are performed.
Error Code 0x80070005 DllRegisterServer
Now a few words about registering dynamic libraries when using the system tool regsvr.32.exe. As already mentioned, in this case, the message may contain error code 0x80070005.
In this situation, three types of solutions are possible. First, try to run it exclusively with administrator rights. If it doesn’t work out, just change the type of your own account to administrator in the corresponding section of the “Control Panel” and then reboot.
Finally, turn off the “account” control (UAC), using the registration management settings for this, where the security level slider needs to be moved to the lowest position, save the changes and restart the system.
After completing each action, you need to check whether the problem is resolved by reusing the registration tool (regsvr32.exe).
If nothing helps
Depending on the root cause of the situation, error code 0x80070005 may be issued again and again. If none of the above helps, follow these steps:
- Check if there is enough space on the local disk or in the logical partitions where the backups can be stored. In case of overflow, clean using the properties section of the selected section and the standard cleaning tool.
- Locate the System Volume Information folder in the system section, having previously unchecked the checkboxes for hiding protected system files and hidden objects, call up the properties menu and remove the “Read Only” attribute.
- Call the system configurator (msconfig), disable all startup items and set selective startup, leaving the original configuration item active.
- Call the services section (services.msc) and check the shadow copy service . If it is inactive, double-click to enter the parameter editing menu, launch it and set it to start automatically.
- Reset the repository. To do this, boot the system in safe mode (F8 at startup), start the command console and enter the net stop winmgmt command. Then navigate to the repository directory located in the wbem directory of the System32 folder and rename it by giving it a name, for example, repository-old. Reboot the system in safe mode again and re-enter the command indicated above a little in the console. After its completion, write the line winmgmt / resetRepository. When finished, close the command console and boot the system as usual.
Instead of a total
As you can see, there can be a lot of varieties of the failure described above with the same error code, as well as options for fixing the problem. Immediately it is difficult to determine what exactly was the root cause of such a situation, therefore, if there is at least some description, you need to choose the correction method based on its content. If an unknown error appears, you have to act at random. There is nothing to be done.