# Troubleshooting # OLE Dispatch Exception Code 0 SWbemObjectSet: Invalid Class You can receive error **0x80041010** from multiple applications that call WMI. For my example it was received in Computerlink while checking for the port server process. ![OLE Dispatch Exception.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/ole-dispatch-exception.png) This can be triggered by running the **systeminfo** command in a command prompt or applying patches in SCCM. No matter where you got the error the underlying issue is probably with WMI. Here is how to check! ### Confirm WMI is Broken: Launch the WMI MMC snapin by clicking **Start -> Run** then enter **wmimgmt.msc** Right click **WMI Control (Local)** and click **Properties** ![WMI Control Local.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/wmi-control-local.png) If WMI is working properly then it will show the system information. If you see **Invalid class** then your WMI is not working correctly.
[![WMI Control Invalid.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/wmi-control-invalid.png)](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/wmi-control-invalid.png) **Invalid** [![WMI Control Good.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/wmi-control-good.png)](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/wmi-control-good.png) **Good**
### The most likely cause is MOF Registration Errors To resolve MOF Registration errors the following command needs to be ran from an **elevated** command prompt. It will reregister all .MOF files with WMI. ```bash CD C:\Windows\System32\WBEM dir /b *.mof *.mfl | findstr /v /i uninstall > moflist.txt & for /F %s in (moflist.txt) do mofcomp %s ``` Here is what the command looks like while it runs: [![MOF Registration.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/mof-registration.png)](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/mof-registration.png) Once finished check wmimgmt.msc to see if it is populating the Properties correctly. [![WMI Control Good.png](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/scaled-1680-/wmi-control-good.png)](https://docs.computerlink.com.au/uploads/images/gallery/2023-06/wmi-control-good.png) # Computerlink Updater Not Working ### Things to Check - Updater application is allowed through any firewalls including Windows firewall and any 3rd party or hardware firewalls - The updater has been upgraded to the latest version which works with our new FTP software - FTP Server and Computerlink updater were both changed during the February 2022 floods. If your C:\\Computerlink\\cproupdate.exe modified date is older than February 2022, download the new [cproupdate.exe](https://computerlink.com.au/Updates/cproupdate.exe%7Ccproupdate.exe) to C:\\Computerlink # Computerlink Registration Updater Not Working ### Things to Check - Your bank payment has been processed and is sitting in our bank account. \\\\ This can take several days and payments are checked/processed each Monday. ### Which registration updater is being used? #### Registration Update in Computerlink Doesn't Work - Computerlink application is allowed through any firewalls including Windows firewall and any 3rd party firewalls - Only one instance of Computerlink is open #### Separate Computerlink Registration Application (clinkreg.exe) Doesn't Work - clinkreg.exe application is allowed through any firewalls including Windows firewall and any 3rd party or hardware firewalls - Computerlink is closed