After investigating this particular error code, it turns out that there are several different underlying circumstances that might trigger this problem on Windows 10. Here’s a list of potential culprits that might cause this issue on Windows 10:
Method 1: Enabling the Volume Shadow Copy
As it turns out, if you’re encountering this issue while attempting to use a DllRegisterServer command inside a terminal, chances are you’re dealing with this issue because the main Volume Shadow Copy service is disabled. Keep in mind that when attempting to register a DLL file via a CMD or Powershell terminal, you NEED to have the Volume Shadow Copy service enabled on your computer in order for the operation to be successful. If you’re unsure if this service is enabled or not, follow the instructions below for step by step instructions on using the Services screen to ensure that the Volume Shadow Copy is enabled:
Method 2: Resetting the Windows Security App
If you’re encountering the 0x80070715 error code when attempting to open the Windows Security app or when attempting to perform a scan using it, chances are you’re dealing with some kind of corruption that is preventing the security app from opening normally. Note: Windows Security is the newer built-in security entity on Windows 10 that incorporates antivirus, anti-phishing, anti-ransomware, and a firewall solution. Most commonly, this error code occurs when certain files belonging to the security suites are tainted by corruption. Several affected users that were dealing with the same issue have confirmed that the issue was finally resolved after they have successfully reset the Windows Security app. When it comes to doing this, you have 3 available options:
Resetting the Windows Security App via the Start MenuResetting the Windows Security App via PowerShellResetting the Windows Security App via Command Prompt
Feel free to follow the guide that is closest to your preferred approach to doing things under Windows 10:
A. Resetting the Windows Security App via the Startup Menu
B. Resetting the Windows Security app via Powershell
C. Resetting the Windows Security App via Command Prompt
In case the issue is still not resolved even after you’ve successfully refreshed the Windows Security component, move down to the next potential fix below.
Method 3: Enabling the Windows Update Service
If you’re encountering the 0x80070715 error while attempting to initiate a scan inside Windows Security (and you’ve already tried resetting it using the method above to no avail), it’s possible to face this error due to the main Windows Update service not being enabled so new security signatures cannot be downloaded. Several affected users that were previously encountering the same kind of issue have reported that the issue was finally resolved after they used the Services screen to force-start the Windows Update service and modify the Startup type before initiating the Windows Security scan once again. To ensure that the Windows Update service is Enabled from the Service tab, follow the instructions below:
Method 4: Install every Pending Windows Update
If you are using Windows 10 and you are encountering the 0x80070715 error when attempting to open Windows Security, it’s important to ensure that you have all the pending updates installed to ensure that you have every security dependency required installed. Several users that were also encountering the 0x80070715 error when attempting to open the Security utility (or initiate a scan with it) have reported that the installation was finally successful after they took the time to install every pending Window 10 update from the Windows Update screen. If you think this scenario looks like it could be applicable and you are not running in the latest version of Window 10, follow the on-screen prompts to install every pending Windows 10 update on your computer:
Fix: DllRegisterServer Failed Error 0x8002801cFix: DllRegisterServer failed with error code 0x80070005Fix: Mshtml.dll was loaded, DllRegisterServer entry point was not found[FIX] Windows Failed to Install the following Update with Error 0x800F0986
