Looking for a lost Windows XP firewall

  
                              

I have a strange problem with Windows XP: After looking at the "Local Area Connection" property 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, please use System Restore to restore Windows to an earlier point in time..."
However, the system of the author has already turned off the system restore function after the installation is completed. How is this good? The author has done the following in order Try:

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: At “Local Right click on the connection, select the "Repair" command, wait a moment, the system prompts "Repair operation is completed. If the problem persists, please contact your network administrator or ISP. "At this time, the fault still exists, and when you right-click "Local Area Connection" and select the "Bridge" command, the system prompts "An abnormal error occurred while configuring the network bridge."

Try 3: Because of the above two comparisons The conventional solution can't work. Consider reinstalling or repairing and installing Windows XP. However, with the attitude of trying to search for "Windows Management Instrumentation" as a keyword on the search engine, I found a solution. The specific operation is as follows:

Step 1: Right-click on "My Computer", select the "Manage" menu, navigate to the "Computer Management (Local)→Services and Applications→Services" item, and find "Windows Management Instrumentation" in the right window. "One item, double-click to open, click the "Stop" button in the pop-up window.

Step 2: Enter the C:WindowsSystem32WbemRepository directory of the local disk, delete all the files in the directory, restart the computer After logging in, the system will re-create the required files in the directory and start automatically. The WMI service is 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 You 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, run the wmimgmt.msc command to open the WMI snap-in The system prompts "Failed to connect to local computer due to WMI: Generic failure" error.

Copyright © Windows knowledge All Rights Reserved