ndOffice is stuck in a login loop and reinstalling or clearing the echo does not help.
If ndOffice is stuck in a login loop and reinstalling or clearing the echo does not help, it is possible that a component of your PC called WMI classes has some corruption.
To confirm this is true;
- Go to start>run and type in wmimgmt.msc
- Right-click on “Wmi Control (Local)” and select properties
- On the General tab, if there are any failures noted on that box, that indicates a core WMI issue
A failure will look something like this
The above is the most common class failures and the below steps outline how to fix them.
If you have different invalid classes you may need to repair different MOF’s and register different DLL’s, see the end of this article on how to find out what MOF and DLL you need or Click Here to jump to it now..
If you have failures it’s most likely CIMV2 so we need to repair its MOF and register its DLL
- Open CMD with elevated permissions
- Change the directory to C:\Windows\System32\Wbem by entering CD C:\Windows\System32\Wbem
- Now enter the below to repair the MOF
- mofcomp.exe CIMWin32.mof
- Now enter the below to register the DLL’s
- regsvr32 CIMWin32.dll
- regsvr32 Wbemcore.dll
If this is all successful go back to the wmimgmt.msc as mentioned at the start of this article and check the properties of “Wmi Control (Local)” again. You should see processor and operating system information like the below. If you do you will now be able to log into ndOffice.
Different Invalid Classes?
If the failed Classes don’t match those in this article you will need to find out the correct MOF and DLL to repair.
To do this Search here for the name of the failed class https://docs.microsoft.com/en-gb/ e.g search “win32_processor class” will give you the results that include this page (you will need to use your judgment on what article to view but it’s usually the first one, it will be in the same format as this) https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-processor On the left hand side under the heading “In this article” click on “Requirements” to find the name of the MOF and DLL (There might not be an associated DLL). The requirements section will look like the below. Now you just substitute the MOF and DLL you found in the article with the ones listed in the steps above.