| | Sage System Verifier fails on System Disk step |
| Cause | Corrupt Windows Management Instrumentation (WMI). ▼ Steps to verify corruption - Open Computer Management.
- Right mouse-click on WMI Control, in Services and Applications and select Properties.
- If you receive an access denied error, you don’t have permissions to access the WMI console. Either log into the machine as an Administrator or contact your System Administrator to reset your permissions.
- Verify text in the box on the General tab:
- This is an example of a good result:
- This is an example of a corrupted WMI:
 The text can contain different variations of errors. If you see text containing Failed to connect to local computer because Interface: class not registered, Could not be found..., Failed to initialize..., or Is corrupt... then continue with the steps below. Windows Management Instrumentation (WMI) Troubleshooting |
| Resolution | | [BCB:3:Network warning:ECB] - Open services by pressing the Windows key + R then typing services.msc.
- Locate the Windows Management Instrumentation service.
- Right-click the service and select Properties.
- Change startup type to Disabled then stop the service.
- Minimize the Services window.
- Open Windows Explorer, paste: %SystemRoot%\System32\WBEM\Repository in the address bar and press enter.
- Delete the files in that folder.
- Go back to services and open the properties of the Windows Management Instrumentation service again.
- Change the startup type back to Automatic and start the service.
- Press the Windows key + R to open the Run dialog box.
- In the Open field, type wmimgmt.msc and click OK, or press Enter.
- Select Action, Properties.
- Confirm the message in the WMI Control box starts with Successfully connected to : local computer...
- Relaunch the Sage System Verifier and confirm it no longer fails on those components.
|
|