Looking for a lost Windows XP firewall

The author's Windows XP has a strange problem: After viewing the properties of "local connection" and switching to the "advanced" tab, the Windows Firewall (ICF) that should have appeared is gone! Instead, a hint: Windows cannot display the properties of this connection. Windows Management Instrumentation (WMI) information may be corrupted. To correct this problem, use System Restore to restore Windows to an earlier point in time ……”

But the author's system has already turned off System Restore after installation, how is it? ? The author made the following attempts in order:

Try 1: In view of the NIC failure, first choose to reinstall the NIC driver after uninstalling the NIC in the “Device Manager”, and the fault remains.

Try 2: Right click on the "Local Connection" and select the "Repair" command. Wait a moment, the system prompts “ The repair operation is completed. If the problem persists, please contact your network administrator or ISP. & rdquo; At this time, it is found that the fault still exists, and when right-clicking "Local Connection", when the "Bridge" command is selected, the system prompts "An abnormal error occurs when configuring the network bridge".

Try 3: Since the above two conventional solutions can't work, consider reinstalling or repairing Windows XP, but with a try, you will be searching for "Windows Management Instrumentation" as a keyword. Search on the engine and find a solution, the specific operation is as follows:

Step 1: Right-click "My Computer", select the "Manage" menu, and then navigate to "Computer Management (Local ) → service and application & rarr; service & rdquo; item, find the "Windows Management Instrumentation" in the right window, double-click to open, click the "stop" button in the pop-up window.

Step 2: Go to the C:WindowsSystem32WbemRepository directory of the local disk, and after restarting all the files in the directory, restart the computer. After logging in, the system will re-create the required files in the directory and automatically start the WMI service that was just stopped.

Tips

This fault is caused by a corrupted file in the C:WindowsSystem32WbemRepository directory. WMI will call the files in this directory every 30 to 60 seconds, so it will receive The above error message. Other chain reactions that can be caused by this fault are: unable to view the properties of "local connection", the system does not respond when running the msinfo32 (view system information) command, and the system prompts "wailed" when the wmimgmt.msc command is run to open the WMI snap-in. To connect to local computer due to WMI: Generic failure” error.