Solution to local connection loss after XP installs the security patch kb905414

Security Patch kb905414 after the patch is installed, the system will encounter a typical fault phenomenon: 1. Open the "Network Connection" prompt: the network connection folder cannot search for network adapters on your machine. Make sure the network connection service is enabled and running. 2. You cannot use the ipconfig command in cmd mode. When you use the ipconfig command, a dialog box is displayed: unable to locate Program Enter hrisipstatecheckingenabled on the Dynamic Link Library netshell. dll. 3. A 2nd-point dialog box will pop up when the machine is started. Method 1: Go to the control panel, double-click "add or delete programs", select "show updates", and then Uninstall "Windows XP Security Update (kb905414)". After restart, the system will resume normal operation. Method 2: 1. Run Registry Editor "regeidt", find HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run, create a new string value, enter the name "Ray", double-click, enter "C: \ windows \ system32 \ mongoray.exe" and restart your computer. 2. Click search my computer, find the "cmdray.exe" file, and copy it to the startup item in the Start Menu. Reregister regsvr32 stobject. dllregsvr32 netmask X. dllregsvr32 netman. dllregsvr32 netshell. dll method 3: 2. Solution steps: How can we solve the problem when the problem arises? Step 1: Verify that the network DLL file is correctly registered. In Windows2000/XP/2003, the network-related dynamic link library file mainly includes netshell. DLL, netmask X. DLL, netman. DLL. In actual use, the DLL file registration may be invalid due to some exceptions. You only need to enter "regsvr32 netshell. DLL "(without quotation marks) to complete the registration of the DLL file. Similarly, regsvr32 netmask X. DLL and regsvr32 netman. DLL completes registration of the other two files. After registration, restart the computer. Step 2: Verify the network adapter settings and use "My Computer> Properties> hardware> Device Manager" to expand the network adapter (network adapter ), verify that the correct Nic is listed. Are you sure the NIC model is correct and there is no device in front of it? And !. Double-click the network adapter to verify whether the message "this device is working properly" is displayed in "device status" in the "General" tab. Step 3: Verify that the necessary services have been started. Go to Control Panel> Administrative Tools> services to check whether the following services have been started. It includes six services: Remote Procedure Call (RPC), network connections, Plug and Play, COM + Event System, Remote Access Connection Manager, and telephony. Note that when the Remote Access Connection Manager Service is not started, the network connection is displayed. Set all network-related services such as network connections remote prfocedure call service Simple TCP/IP Services Service Plug and Play to automatic, enable it again, and restart your computer. Generally, this step resolves Step 4: Verify network service settings, and go to Control Panel> add or delete Programs> Add/delete Windows Components ", select "Network Service-> details" to verify that "Simple TCP/IP service" is enabled. Step 5: Make sure that all windows protected files in the system folder are not affected. You can start the Windows File Checker by typing SFC/purgecache and SFC/scannow at the command prompt to fix the protected files. Step 6: fix the key values in the Registry and start the Registry Editor (START-> Run-> enter Regedit ), locate and click the Registry subitem hkey_classes_root \ interface \ {secret} to verify whether the subitem nummethods and proxystubclsid32 exist and whether their values are correct (nummethods is 4 and proxystubclsid32 is {secret }. (For example) if the registry subkeys do not exist, create them. TIPS: You must back up the registry before modifying the Registry. Otherwise, the operation may fail due to poor modification. Step 7: make sure that there are no nonexistent, illusory, or hidden network adapters in the computer. Delete all network adapters if they exist. Delete all third-party network adapter management software. Step 8: Delete the network adapter in the Device Manager and manually or enable the operating system to automatically install the NIC Driver. This step detects and corrects corrupted registry entries bound to the network adapter. If none of the other steps can solve the problem, perform this step.