Fix wmi repository windows 2008

Any MOF files containing the pragma autorecover preprocessor statement are restored to the registry. Once the salvage operation has completed, you should run another consistency check.

EXE process as needed. EXE to rebuild the repository automatically, be aware that you may have to stop or disable some dependent services while performing the maintenance. Remember that the switches we discussed here are not available on any operating systems prior to Windows Vista. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures.

Any additional feedback? Submit feedback. Thank you for your feedback! This error message usually indicates that the WMI repository is corrupted, but sometimes may also indicate that some other system files are corrupted. If you have any previous backup, I would highly suggest that you try restoring to that backup to see if the problem remains. Or, would you please try the following steps to see if they can be of any help? Disable and stop the WMI service.

Run the following commands. Re-enable the WMI service and then reboot the server to see how it goes. If the problem remains, then try the following steps to rebuild the repository:. Re-enable the WMI service. Reboot the server to see if the problem remains. If the above steps cannot help, you may also need to check if some disk sectors or system files are corrupted. Otherwise, you may need to reinstall the whole server.

Best regards,. We had similar problems and the procedure above worked, however in addition we had to rejoin the computer account to the domain. This procedure worked for me on an SBS server which has had SBS console crashing and other applications crashing.

Thanks for the solution Chang Yin. Still valid after 5 years. Thanks for helping me out. I have had this problem on our 8 year old DC for the last few months and nothing has worked until I finally saw your post.

It took some tweaking but in the end it finally stopped. My users will be happy, well as happy as users get anyways, with an increase in responsiveness. Its under domain group with hardening. But the error was different. Can you provide your inputs for my below query please.. Why most of the windows OS issues will get fixed by simply just reboot. Its good, but want to know what exactly the actions taken place during the booting process. Turned to be nasty disk issue with what the system saw as removable disks and an AD GPO effectively denied access to these should have affected removable USB drives only.

These hotfixes are associated with the operation and functionality of the WMI service and its related components. When experiencing issues related to WMI on a system the symptoms can vary widely depending upon the root cause. The following are a few examples of high-level symptoms noted in support incidents that may be resolved with the application of the indicated hotfixes:.