First, the system file loss recovery method
Due to improper operation, sudden power outage, virus damage or frequent installation and uninstallation operations, etc., may cause system file loss or damage failure. After the general system file is lost, we can easily get the damaged file name and path from the fault prompt window that appears, so the repair is very simple.
1. The most common Rundll32.exe file is missing
The Rundll32.exe program as its name implies is a 32-bit DLL file, it is an essential system file, and some projects and programs that are missing it will not be executed. However, due to its particularity, it can be easily destroyed. If you open certain items in the control panel, "Windows cannot find the error message 'C:\\Windows\\system32 \\Rundll32.exe'” (Figure 1), you can solve it by the following operations.
Step 1: Insert the Windows XP installation CD into your CD-ROM drive, then click & ldquo; start & rarr; run & rdquo ;. Step 2: In the “Run” window, enter the “expand x:\\i386\
undll32.ex_c:\\windows\\system32 \
undll32.exe” command and press Enter (where “x” is the drive letter of the CD-ROM drive) . Step 3: After the repair is complete, restart the system.
2. The DLL link file has "Backup". There are many DLL dynamic link library files in the system. They are usually stored in the Windows\\System32 folder under the system disk. When a program is run, the corresponding DLL file will be called. Since DLL files can be shared by multiple programs, it is easy to uninstall them or perform incorrect modifications when uninstalling or installing some programs. If the MFC42u.DLL file is missing when trying to open the system information program to check the system status, the MFC42u.DLL file is missing. The general method for resolving such a fault is as follows: br>
first, you find out whether there is MFC42u.DLL file in Windows XP installation CD if copied directly to the file to the Windows \\ System32 folder. If it is in a compressed format (similar to the rundll32.ex_ file in the previous example), you can use the expand command to extract the files from the CD to the System32 folder.
If you can't find the MFC42u.DLL file and can't find its compression format (this is the case in this case), then this is the Microsoft search page (http://search.microsoft.com /search/search.aspx?st=b&na=80&qu=&View=en-us)Enter “MFC42u.DLL”Search as a search keyword and open the relevant search page to view related content. According to the content of the open page prompt, in order to obtain this MFC42u.Dll file, we can install the Vcredist.exe program developed by Microsoft. After downloading and installing the program, you can find the MFC42u.DLL file in its installation folder and copy it to the System32 folder. If you find this kind of trouble, you can go to some professional DLL file download site to download, so you can fix it by finding the corresponding download link in the webpage and downloading it to the corresponding folder. Of course, if you have the conditions, you can also copy the relevant files on other computers to fix.
Tip: Some DLL files need to be registered after copying to the corresponding directory. If the abc.dll file in the System32 folder needs to be registered and authenticated, you can execute "ldsvr32 c:\\" in the running window. Windows\\system32\\abc.dll” command to register the component.
3. Troubleshoot the loss of alternative files
When such a fault occurs, it usually gives a set of CLSID registration codes instead of telling the user the name of the file that is damaged or lost, so it often makes some rookies feel overwhelmed. For example, when the author executed the “gpedit.msc” command in the running window to open the group policy, there was a prompt window (see Figure 3) that the management unit failed to initialize (see Figure 3), click “determine & rdquo;卮蚩?嘤Φ淖椴呗? Figure 4), and after inspection, it was found that the gpedit.dll file was lost, although the missing files were not prompted in the window, but in the actual solution to such failures Not very difficult.
In fact, the CLSID (Class IDoridentifier) class identifier in the window is a clue to solve the problem, because each object is assigned a unique one in the registry. Identification, so that we can find relevant clues by looking in the registry, the specific method is as follows.
Execute the “regedit” command in the "Run" window, then click “Edit →Find & rdquo; in the open registry window, then enter the CLSID ID in the input box (in this case The CLSID logo is "8FC0B734-A0E1-11D1-A7D3-0000F87571E3}”), then select the “InProcServer32” item in the searched class identifier, and then double-click the "Default" option in the right window. In the “Value Data”, you will see “%SystemRoot%\\System32\\GPEdit.dll”, where GPEdit.dll is the missing or damaged file in this example. Simply unpack the relevant files on the installation CD or copy them directly into the appropriate directory to fix them completely.