# Invalid Class Or Provider Failure

Zee Drive uses the WMI service (Windows Management Instrumentation) to retrieve information about the computer during activation and start-up. Sometimes a Windows update may cause a problem with WMI, corrupting the WMI repository, and causing Zee Drive to fail with an error: *invalid namespace*, *invalid class, provider failure* or *not found*.

The first step to resolve this error is to check that the computer is up to date with the latest Windows updates, then restart the computer. If it is already up to date then restart the computer anyway as sometimes an error with WMI can be transitory.

If the error persists, check the WMI repository for corruption. Open a MSDOS command prompt as local admin (note the *Administrator* in the title of the MSDOS window if its opened as admin):

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2F9i1G0oObsJqn0ZauOmFY%2Fcommand%20prompt.png?alt=media&#x26;token=2f3a1541-c1a4-4da9-a31f-7c2954a34af0" alt="" width="492"><figcaption></figcaption></figure>

Then enter the following command in to the command prompt:

`winmgmt /verifyrepository`

If the WMI repository is corrupted the returned result will be *Repository is inconsistent*. If you receive this error try repairing the WMI repository with the following command (only run this command if you get the *inconsistent* error):

`winmgmt /salvagerepository`

If the repository is consistent, then try rebuilding individual components of WMI that Zee Drive requires. These components may have become corrupted due to Windows driver or system component updates.

From the MSDOS command prompt (as local admin), change your directory to  *C:\Windows\System32\Wbem* with the command:

`Cd C:\Windows\System32\Wbem`

Now enter the following commands one at a time in to the command prompt and hit return after each. These commands will rebuild the WMI components and re-register them.

`mofcomp.exe Vds.mof`

`regsvr32 Vdswmi.dll`

`mofcomp.exe CIMWin32.mof`

`regsvr32 CIMWin32.dll`

After running the commands, restart the Windows WMI service:

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FosWUPdb8HANDLI6fly76%2Fwmi%20service.png?alt=media&#x26;token=6759c31b-c072-41be-b7f3-ed8c536d56f4" alt="" width="522"><figcaption></figcaption></figure>

If the above steps do not work, try rebooting the computer and running through the steps again.