The author's Windows XP has a strange problem: When you view the properties of the local Area Connection and switch to the Advanced tab, the Windows Firewall (ICF) that should have been missing! Instead, a hint: Windows cannot display properties for this connection. Windows Management Instrumentation (Windows Management Architecture Component WMI) information may be corrupted. To correct this problem, use System Restore to restore Windows to an earlier point in time ... ".
However, the author's system after the installation has already turned off the System Restore function, what should be good? The author in turn made the following attempts:
Try 1: In view of the network card failure, first choose to uninstall the NIC in Device Manager to reload the NIC driver, the result is still the fault.
Try 2: Right click on "Local Area Connection", select "Fix" command, wait a moment, the system prompts "repair operation completes." If the problem persists, please contact your network administrator or ISP. "The failure still exists, and when you right-click Local Area Connection and select the Bridging command, you are prompted to" Configure the Network Bridge with an unexpected error. "
Try 3: Because the above two more conventional solutions do not work, consider reloading or repairing Windows XP, but try to look at the "Windows Management instrumentation" as a keyword search engines, found a solution , the following actions are as follows:
Step one: Right click on "My Computer", select the "Admin" menu, navigate to the "Computer Management (local) → service and application → services" item, locate the "Windows Management instrumentation" Item in the right window, double-click Open, click in the pop-up window "Stop" button.
Step two: Go to the Local Disk C:\Windows\System32\Wbem\Repository directory, delete all files in the directory, restart the computer. Once logged in, the system will re-create the required files in the directory copy and automatically start the WMI service just stopped.
Small tip:
This failure is caused by a corrupted file in the C:\Windows\System32\Wbem\Repository directory, and WMI calls the files in that directory every 30-60 seconds, so you receive the error message above. Other ripple effects that can be caused by this failure are: Unable to view the properties of the local area connection, running Msinfo32 (viewing system Information) command when the system is unresponsive, running the wmimgmt.msc command to open the WMI snap-in system prompts "Failed to connect to" Computer due to wmi:generic failure "error. Finish Computer Basics Tutorial Network）
