Код ошибки 80010002

When opening certain programs on a Windows client or server computer, the Call was canceled by the message filter with error code 0x80010002 may be triggered. In other cases, the same issue is encountered when a legacy application is called. This post provides the most applicable fixes to this issue.

Unexpected error occurred.

Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))

If you get an error prompt stating Call was canceled by the message filter, 0x80010002 when you try to open an application or when the application is called on your Windows 11/10 computer, then the following suggested fixes we have presented below in no particular order should help you fix the error on your system.

1. Check the Remote Procedure Call (RPC) service
2. Restart the Windows Management Instrumentation (WMI) service
3. Run WBEMTEST
4. Re-register DLLs, Recompile the .mofs in the wbem folder, and Re-register WMI Service and Provider
5. Repair/Rebuild Windows Management Instrumentation
6. Temporarily disable or uninstall antivirus
7. Run WBEMTEST
8. Troubleshoot RPC errors using PortQry
9. Convert Windows service component monitors from WMI to RPC

Let’s see the suggested fixes in detail. If your system hasn’t been updated in a while, before you proceed any further, we suggest you check for updates and install any available bits (including Optional Updates) on your system then see if the issue is resolved or not. Reinstalling the application throwing the error may also help.

1] Check the Remote Procedure Call (RPC) service

The RPCSS service is the Service Control Manager for COM and DCOM servers. It performs object activations requests, object exporter resolutions, and distributed garbage collection for COM and DCOM servers. If this service is stopped or disabled, programs using COM or DCOM will not function properly. Additionally, the RpcSs service uses the rpcss.dll file that is located in the C:\Windows\system32 directory. If the file is removed or corrupted, you may encounter this Call was canceled by the message filter, 0x80010002 error.

This solution requires you to check and make sure the Remote Procedure Call (RPC) (RpcSs) Service is started and set to Automatic startup which is the default configuration. To restore the default startup configuration of the service, run the Command Prompt as an administrator, then copy and paste the command below and hit Enter.

sc config RpcSs start= auto
sc start RpcSs

Once the command executes, close the command window and restart the computer.

2] Restart the Windows Management Instrumentation (WMI) service

Windows Management Instrumentation (winmgmt) Service provides a common interface and object model to access management information about the operating systems, devices, applications, and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start. Also, the winmgmt service is using the WMIsvc.dll file that is located in the C:\Windows\system32\wbem directory – if the file is removed or corrupted, you are likely to encounter issues with dependent services.

This solution requires you to ensure the winmgmt service is set to its default startup configuration on your target server by running the command below in an elevated CMD prompt. Restart the service if it’s already running.

sc config winmgmt start= auto
sc start winmgmt

Read: WMI Provider Host (WmiPrvSE.exe) High CPU Usage

3] Run WBEMTEST

If you are unable to restart WMI as described above, you can run WBEMTEST locally to test WMI connectivity on the node. For this, refer to this Microsoft documentation.

4] Re-register DLLs, Recompile the .mofs in the wbem folder, and Re-register WMI Service and Provider

For this solution, you need to re-register all of the DLLs and recompile the .mofs in the wbem folder, and re-register WMI Service and Provider. To perform this task, you need to create and run a batch file by following these steps:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type notepad and hit Enter to open Notepad.
• Copy and paste the syntax below into the text editor.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

• Save the file with a name and append the .bat file extension – eg; Re-registerWMI.bat; on the Save as type box, select All Files.
• Now, run the batch file with admin privilege (right-click the saved file and select Run as Administrator from the context menu) or simply double-click the .bat file to run it.
• Once the batch file runs, you can delete it.
• Reboot the machine and test WMI.

5] Repair/Rebuild Windows Management Instrumentation

You can quickly repair or rebuild WMI on a local machine or server (as the case may be) by creating a batch file as shown above with the source code below or you can follow the step-by-step instructions provided in the linked guide.

Echo Rebuilding WMI.....Please wait. > c:\wmirebuild.log
net stop sharedaccess >> c:\wmirebuild.log
net stop winmgmt /y >> c:\wmirebuild.log
cd C:\WINDOWS\system32\wbem >> c:\wmirebuild.log
del /Q Repository >> c:\wmirebuild.log
c:
cd c:\windows\system32\wbem >> c:\wmirebuild.log
rd /S /Q repository >> c:\wmirebuild.log
regsvr32 /s %systemroot%\system32\scecli.dll >> c:\wmirebuild.log
regsvr32 /s %systemroot%\system32\userenv.dll >> c:\wmirebuild.log
mofcomp cimwin32.mof >> c:\wmirebuild.log
mofcomp cimwin32.mfl >> c:\wmirebuild.log
mofcomp rsop.mof >> c:\wmirebuild.log
mofcomp rsop.mfl >> c:\wmirebuild.log
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s >> c:\wmirebuild.log
for /f %%s in ('dir /b *.mof') do mofcomp %%s >> c:\wmirebuild.log
for /f %%s in ('dir /b *.mfl') do mofcomp %%s >> c:\wmirebuild.log
mofcomp exwmi.mof >> c:\wmirebuild.log
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof >> c:\wmirebuild.log
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof >> c:\wmirebuild.log
mofcomp exmgmt.mof >> c:\wmirebuild.log
net stop winmgmt >> c:\wmirebuild.log
net start winmgmt >> c:\wmirebuild.log
gpupdate /force >> c:\wmirebuild.log

Read: WMI Repository reset failed, Error 0x80070005, 0x8007041B, 0x80041003

6] Temporarily disable or uninstall antivirus

There is probably either security/antivirus software causing problems on the server, the WMI/DCOM configuration is bad, or the WMI repo is damaged. So, if the issue persists after you have applied the solutions 1, 2, 4, and 5 mentioned above, you can try uninstalling any antivirus software, disabling the Windows firewall, or any third-party dedicated firewall, and see if that helps.

7] Troubleshoot RPC errors using PortQry

PortQry provides quick insight into how RPC is functioning before you delve into network trace data. As the exception being thrown references RPC, you can troubleshoot RPC errors using PortQry.exe commands to quickly determine whether you can make a connection on the client or server computer as the case may be.

8] Convert Windows service component monitors from WMI to RPC

This fix applies to SolarWinds users that encountered the issue and received the error message in the web console. This potential workaround can help resolve the issue without drastic steps such as rebuilding performance counters or rebuilding the WMI repository — instead convert Windows service component monitors from WMI to RPC by following these steps:

• Browse to the SAM Summary page in the Orion web console.
• Edit the application template that has the windows service component.
• Expand the Windows Service component.
• Change from WMI to RPC method.
• Save.

To change all possible Windows Service Monitors to the RPC method across all your applications, you can use the SQL Script available at support.solarwinds.com to convert all existing Windows service component monitors fetching methods from WMI to RPC.

I hope this post helps!

How do I fix error code 0xc8000402?

Reportedly, the error code 0xc8000402 will most likely be encountered by Windows Insiders running Windows 10 who join the Dev or Beta Channels while trying to download the latest build on their device. If you’re affected by this, as a workaround, you can join the Release Preview Channel first, and then install Windows 11 from there.

What is Unsuccessful 0x80070002?

The error 0x80070002 in SCCM deployment means The system cannot find the file specified. In another instance, the error 0x80070002 is a Windows update error that can result from corrupt or missing system files. Also, if the system doesn’t have enough space to download the update, you may encounter this error. The problem can also appear due to conflict between hardware devices attached to the system.

The error code 0x80010002 is an update-related issue and it occurs primarily when you are downloading and installing cumulative updates on Windows 11/10. Since you are here, you must be facing this error code as well. In this post, we will discuss what possibly could trigger this error code and five working ways to address this issue on Windows PC. 

What causes Error 0x80010002 on Windows 11/10?

Corrupt system files, the presence of a faulty antivirus program, and corruption inside the Windows Cache folders are the main reasons invoking an error 0x80010002 on Windows.

Try troubleshooting Windows Update, running SFC & DISM scans, and resetting update components might address this problem. If you have already tried these methods, you better manually download and install pending updates on your computer. 

Ways to Solve Update Error 0x80010002 

If you are encountering an error code 0x80010002, go through the below list of solutions, and check if any addresses this bug for you. The probable fixes are as follows – 

• Troubleshoot Windows Update
• Disable Third-party Antivirus
• SFC and DISM Scans
• Reset Windows Update Components
• Manually download and install pending updates

1] Troubleshoot Windows Update

The update troubleshooter is the built-in tool on Windows 11/10 that can look for the underlying causes on your system and have them resolved in no time. Since you are not able to install available Windows updates, we suggest following these steps – 

Windows 11:

• Open Settings using the Win & I shortcut.
• Navigate to System > Troubleshoot, and click to expand Other troubleshooters.
• Locate Windows Update under Most frequent, and hit the Run button available beside it. See the Snapshot below –

• Wait for this tool to detect and resolve the underlying causes. 
• After this is over, restart your PC.
• When Windows 11 reloads, check if you can download and install pending updates now. 

Windows 10:

• Press Win and I key to launch Settings.
• Click Update & Security and then Troubleshoot on the left pane. 
• Move to the right pane and click Additional troubleshooters.
• Look for Windows Update under Most frequent, and when it expands, click Run the troubleshooter.

• Follow the on-screen instructions to let this tool find and address the persisting problems. 

After this tool finishes the troubleshooting part, restart your PC and check if the error 0x80010002 resolves this way. 

2] Disable Third-party Antivirus

Many a time, update-related errors occur just because of some third-party applications running on your Windows PC. This holds true for an external antivirus program as well. If you are using such software, we suggest disabling them first and checking if you can Windows 11/10 next. For that, you need to reach out to the below path and hit the Check for updates button. 

Note: If you don’t want to uninstall your antivirus program, you better disable the security app and check how this goes. When the updates start installing next, you need to let go of the external antivirus program. 

Windows Security is a perfect built-in security app on Windows 11/10. In addition to protecting your device against viruses and malware, this tool also lets you use its parental control tool. You better try this software as this presents way more options than a freely available antimalware application.

3] SFC and DISM Scans

The presence of a buggy application on Windows 11/10 often corrupts some system files or drivers. For example, certain antivirus programs are known to modify the system services and as a result of this, Windows update simply fails on some error code 0x80010002.

In such a scenario, the SFC and DISM present the perfect way to automatically detect missing or damaged files on your system and have them repaired. Follow the below instructions on how to use both these tools on an elevated console. 

• Click on the Search box and type CMD in the text area.
• Right-click on Command Prompt and select the first option i.e. Run as administrator.
• If the UAC prompts for authentication, click Yes.
• On the elevated prompt, type sfc /scannow and hit Enter to begin the scanning/repairing process.

• This takes around 10-15 minutes to complete repairing missing as well as corrupt system files or folders.
• When the SFC scan reaches 100%, you may run the DISM code next. The DISM command will ensure no corruption lies within the System image. Here’s what you need to run on the elevated console –

DISM /Online /Cleanup-Image /RestoreHealth

• This command will also take 10-15 minutes to automatically detect corruption inside the System image and have them resolved. 
• When the DISM command completes 100%, you may close CMD, and reboot your Windows PC. 

When Windows 11/10 reloads, check if you can update Windows normally without getting into an error 0x80010002.

4] Reset Windows Update Components

The one prime reason that might cause Windows updates to fail on some error codes is corruption within the Update components. This includes unnecessarily stored cookies and caches inside Windows Cache folders and disabling any essential service. 

Try resetting all components on your Windows 11/10 PC, and check if this update issue resolves afterward. If not, you can always manually download and install the pending updates on your computer. 

5] Manually download and install pending updates

If none of the above solutions work to address the error code 0x80010002, it comes down to manually downloading the updates and installing them. The steps are more or less the same for Windows 11 or Windows 10. For your convenience, we have written down separate topics on how to download and install standalone packages on your specific version of Windows. 

Note: While choosing to download the standalone package, make sure to download the update matching your system architecture. Otherwise, all your data would be wasted, and you need to re-download the Windows setup file. 

• Manually Download and Install Windows 11 Updates
• Manually download and install Windows 10 Updates

I sincerely hope the error code 0x80010002 resolves after trying out the above-enlisted solutions. In case you do have queries or suggestions related to this post, let’s know in the comment section. 

How do I Solve Windows Update Error 0x80070002?

Just like error 0x80010002, 0x80070002 is another update-related issue and you may fix it by going through the above solutions. In case you have already tried some of these methods and failed, you better skip to the last solution, i.e. manually downloading and reinstalling pending updates.

Here’s a complete guide on how to fix Windows Update Error 0x80070002.

How to Solve Update Error 0x80004002

If you are struggling with an error code 0x80004002 while downloading or installing available Windows updates, we suggest going through this post and checking if the problem resolves this way. 

When opening certain programs on a Windows client or server computer, the Call was canceled by the message filter with error code 0x80010002 may be triggered. In other cases, the same issue is encountered when a legacy application is called. This post provides the most applicable fixes to this issue.

Unexpected error occurred.

Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))

Call was canceled by the message filter, 0x80010002

If you get an error prompt stating Call was canceled by the message filter, 0x80010002 when you try to open an application or when the application is called on your Windows 11/10 computer, then the following suggested fixes we have presented below in no particular order should help you fix the error on your system.

1. Check the Remote Procedure Call (RPC) service
2. Restart the Windows Management Instrumentation (WMI) service
3. Run WBEMTEST
4. Re-register DLLs, Recompile the .mofs in the wbem folder, and Re-register WMI Service and Provider
5. Repair/Rebuild Windows Management Instrumentation
6. Temporarily disable or uninstall antivirus
7. Run WBEMTEST
8. Troubleshoot RPC errors using PortQry
9. Convert Windows service component monitors from WMI to RPC

Let’s see the suggested fixes in detail. If your system hasn’t been updated in a while, before you proceed any further, we suggest you check for updates and install any available bits (including Optional Updates) on your system then see if the issue is resolved or not. Reinstalling the application throwing the error may also help.

1] Check the Remote Procedure Call (RPC) service

The RPCSS service is the Service Control Manager for COM and DCOM servers. It performs object activations requests, object exporter resolutions, and distributed garbage collection for COM and DCOM servers. If this service is stopped or disabled, programs using COM or DCOM will not function properly. Additionally, the RpcSs service uses the rpcss.dll file that is located in the C:\Windows\system32 directory. If the file is removed or corrupted, you may encounter this Call was canceled by the message filter, 0x80010002 error.

This solution requires you to check and make sure the Remote Procedure Call (RPC) (RpcSs) Service is started and set to Automatic startup which is the default configuration. To restore the default startup configuration of the service, run the Command Prompt as an administrator, then copy and paste the command below and hit Enter.

sc config RpcSs start= auto
sc start RpcSs

Once the command executes, close the command window and restart the computer.

2] Restart the Windows Management Instrumentation (WMI) service

Windows Management Instrumentation (winmgmt) Service provides a common interface and object model to access management information about the operating systems, devices, applications, and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start. Also, the winmgmt service is using the WMIsvc.dll file that is located in the C:\Windows\system32\wbem directory – if the file is removed or corrupted, you are likely to encounter issues with dependent services.

This solution requires you to ensure the winmgmt service is set to its default startup configuration on your target server by running the command below in an elevated CMD prompt. Restart the service if it’s already running.

sc config winmgmt start= auto
sc start winmgmt

Read: WMI Provider Host (WmiPrvSE.exe) High CPU Usage

3] Run WBEMTEST

If you are unable to restart WMI as described above, you can run WBEMTEST locally to test WMI connectivity on the node. For this, refer to this Microsoft documentation.

4] Re-register DLLs, Recompile the .mofs in the wbem folder, and Re-register WMI Service and Provider

For this solution, you need to re-register all of the DLLs and recompile the .mofs in the wbem folder, and re-register WMI Service and Provider. To perform this task, you need to create and run a batch file by following these steps:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type notepad and hit Enter to open Notepad.
• Copy and paste the syntax below into the text editor.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

• Save the file with a name and append the .bat file extension – eg; Re-registerWMI.bat; on the Save as type box, select All Files.
• Now, run the batch file with admin privilege (right-click the saved file and select Run as Administrator from the context menu) or simply double-click the .bat file to run it.
• Once the batch file runs, you can delete it.
• Reboot the machine and test WMI.

5] Repair/Rebuild Windows Management Instrumentation

You can quickly repair or rebuild WMI on a local machine or server (as the case may be) by creating a batch file as shown above with the source code below or you can follow the step-by-step instructions provided in the linked guide.

Echo Rebuilding WMI.....Please wait. > c:\wmirebuild.log
net stop sharedaccess >> c:\wmirebuild.log
net stop winmgmt /y >> c:\wmirebuild.log
cd C:\WINDOWS\system32\wbem >> c:\wmirebuild.log
del /Q Repository >> c:\wmirebuild.log
c:
cd c:\windows\system32\wbem >> c:\wmirebuild.log
rd /S /Q repository >> c:\wmirebuild.log
regsvr32 /s %systemroot%\system32\scecli.dll >> c:\wmirebuild.log
regsvr32 /s %systemroot%\system32\userenv.dll >> c:\wmirebuild.log
mofcomp cimwin32.mof >> c:\wmirebuild.log
mofcomp cimwin32.mfl >> c:\wmirebuild.log
mofcomp rsop.mof >> c:\wmirebuild.log
mofcomp rsop.mfl >> c:\wmirebuild.log
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s >> c:\wmirebuild.log
for /f %%s in ('dir /b *.mof') do mofcomp %%s >> c:\wmirebuild.log
for /f %%s in ('dir /b *.mfl') do mofcomp %%s >> c:\wmirebuild.log
mofcomp exwmi.mof >> c:\wmirebuild.log
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof >> c:\wmirebuild.log
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof >> c:\wmirebuild.log
mofcomp exmgmt.mof >> c:\wmirebuild.log
net stop winmgmt >> c:\wmirebuild.log
net start winmgmt >> c:\wmirebuild.log
gpupdate /force >> c:\wmirebuild.log

Read: WMI Repository reset failed, Error 0x80070005, 0x8007041B, 0x80041003

6] Temporarily disable or uninstall antivirus

There is probably either security/antivirus software causing problems on the server, the WMI/DCOM configuration is bad, or the WMI repo is damaged. So, if the issue persists after you have applied the solutions 1, 2, 4, and 5 mentioned above, you can try uninstalling any antivirus software, disabling the Windows firewall, or any third-party dedicated firewall, and see if that helps.

7] Troubleshoot RPC errors using PortQry

PortQry provides quick insight into how RPC is functioning before you delve into network trace data. As the exception being thrown references RPC, you can troubleshoot RPC errors using PortQry.exe commands to quickly determine whether you can make a connection on the client or server computer as the case may be.

8] Convert Windows service component monitors from WMI to RPC

This fix applies to SolarWinds users that encountered the issue and received the error message in the web console. This potential workaround can help resolve the issue without drastic steps such as rebuilding performance counters or rebuilding the WMI repository — instead convert Windows service component monitors from WMI to RPC by following these steps:

• Browse to the SAM Summary page in the Orion web console.
• Edit the application template that has the windows service component.
• Expand the Windows Service component.
• Change from WMI to RPC method.
• Save.

To change all possible Windows Service Monitors to the RPC method across all your applications, you can use the SQL Script available at support.solarwinds.com to convert all existing Windows service component monitors fetching methods from WMI to RPC.

I hope this post helps!

How do I fix error code 0xc8000402?

Reportedly, the error code 0xc8000402 will most likely be encountered by Windows Insiders running Windows 10 who join the Dev or Beta Channels while trying to download the latest build on their device. If you’re affected by this, as a workaround, you can join the Release Preview Channel first, and then install Windows 11 from there.

What is Unsuccessful 0x80070002?

The error 0x80070002 in SCCM deployment means The system cannot find the file specified. In another instance, the error 0x80070002 is a Windows update error that can result from corrupt or missing system files. Also, if the system doesn’t have enough space to download the update, you may encounter this error. The problem can also appear due to conflict between hardware devices attached to the system.