Wmi error when opening sharing tab in network adapter

Question

_{Wednesday, October 14, 2015 1:09 AM}

I get the message when I try to open the sharing tab of any network adapter Windows cannot display the Properties of this connection. The Windows Management Instrumentation (WMI) information might be corrupted. To correct this, use System Restore to restore Windows to an earlier time (called a restore point). System Restore is located in the System Tools folder in Accesories. Any help would be appreciated Thanks

All replies (4)

_{Thursday, November 5, 2015 11:22 PM ✅Answered}

Thank for submitting the feedback for Windows Server TP3.

I cannot repro this issue in a later build and appears to be resolved.

Regards,

Steven Graves

Windows Beta Support Team

_{Wednesday, October 14, 2015 7:14 AM}

Hi,

According to your description, this problem may occur because of a damaged Windows Management Instrumentation (WMI) database. 

In general, you may try to restore system to a previous restore point, or use repair installation to repair the database. 

Besides, you may try to delete and then re-create the files in the %SystemRoot%\System32\Wbem\Repository folder:

1. Open Run, type Services.msc and press Enter.
2. locate and right-click Windows Management Instrumentation to Stop this service.
3. Open Run, and type %SystemRoot%\System32\Wbem\Repository, press Enter.
4. Delete all of the files in the Repository folder. Then, restart the computer. 

NOTE : The Windows Management Instrumentation service starts automatically when you restart the computer.

Best Regards,
Eve Wang

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Wednesday, October 14, 2015 3:51 PM}

Thanks

I already did that, same problem.

I also notice that the folder %SystemRoot%\System32\Wbem\Repository  contains the files, while

%SystemRoot%\syswow64\Wbem\Repository

is empty. I don't know if that's a problem****

_{Thursday, November 5, 2015 8:49 PM}

I am also experiencing this issue with TP3 - I tried the steps provided and still have the same error.