Regsvr32.exe usage

Regsvr32.exe usage

Regsvr32.exe has the following command line options:

Regsvr32 [/u] [/n] [/I [: using line]Dllname
/U-cancel Server Registration
/I-call dllinstall to pass an optional [using line] for it. When used with/u, you can call the DLL to uninstall it.
/N-Do Not Call dllregisterserver; this option must be used with/I
/S-silent; no message boxes are displayed (attached to Windows XP and Windows Vista)

When regsvr32.exe is used, it will try to load the component and call itsDllselfregisterFunction. If this attempt is successful, regsvr32.exe will display a dialog box Indicating success. If this attempt fails, regsvr32.exe returns an error message, which may include a Win32 error.Code. For more information, clickArticleTo view the articles in the Microsoft Knowledge Base:

193625 (http://support.microsoft.com/kb/193625/) info: wininet error code (12001 to 12156)

For example, to manually register the sample. ocx ActiveX control, enter the following command at the command prompt:

C: \ regsvr32.exe sample. ocx

Back to Top

Regsvr32.exe error message in Windows Vista

The following lists regsvr32 error messages and possible causes.
The command flag "% 1" is invalid. Check the command usage and try again.
In the command line, pass the invalid option combination to regsvr32.exe.
This command is valid only when you open a Microsoft Visual Studio OLE custom control project.
Visual Studio calls regsvr32.exe, but the module is not specified in the command line.
To register a module, you must provide a binary name.
When regsvr32.exe is called, no module is specified in the command line.
The oleinitialize command fails to run. The computer may have insufficient memory. Close any openedProgramAnd then try again.
Regsvr32 must initialize the com library before calling the required com library function and uninitializing the library when it is disabled. If you fail to initialize the com library or cancel the initialization, these error messages will appear.
Failed to load module "% 1. \ N Ensure that the binary is stored in the specified path, or debug it to check whether the binary or related. dll file is faulty. \ N % 2.
An error occurred while loading the specified module in the command line. The error text is displayed as part of the message.
The module "% 1" has been loaded, but the entry point % 2 cannot be found. \ N please make sure "% 1" is a valid DLL or ocx file, and then try again.
Regsvr32.exe cannot find the required entry point in the module specified in the command line. This happens if the module export portal is incorrect or the module is not a. dll or. ocx file.
The module "% 1" has been loaded, but failed to call % 2. The error code is % 3. \ N to obtain detailed information about this issue, use this error code as a search term for online search.
An error occurs when regsvr32.exe calls the entry point of the module specified in the command line. This error code is displayed as part of the message
The module "% 1" may be incompatible with the running Windows version. Check whether this module is compatible with regsvr32.exe x86 (32-bit) or x64 (64-bit) versions.
For example, this error may occur when regsvr32.exe is run on an x86 computer and the module specified in the command line is a 64-bit module.

Back to Top

Regsvr32.exe error message earlier than Windows Vista

The following lists the regsvr32 error messages and possible causes.
unrecognizable logo:/invalid_flag
the keyentry mark or switch combination is ineffective (see "regsvr32.exe usage" in this document ).
NO DLL name is specified.
The. dll file name is not added (see the usage of regsvr32.exe in this document ).
dllname is loaded, but no endpoint of dllregisterserver or dllunregisterserver is found.
dllname Is Not A. dll or. ocx file. For example, enter regsvr32 wjview.exe to generate the error message.
dllname is not an executable file. No registration help program is registered for this file type.
dllname is not an executable file (.exe,. dll, or. ocx ). For example, enter regsvr32 autoexec. BAT to generate the error message.
dllname is loaded, but no endpoint of dllregisterserver or dllunregisterserver is found.
dllname may not be exported, or a corrupted dllname version exists in the memory. We recommend that you use pview to detect the file and delete it.
dllname cannot be registered by yourself, or a corrupted version exists in the memory.
for example, this error message is returned after you type regsvr32 icwdial. dll, because the icwdial. dll file cannot be registered by yourself. If you suspect a corrupted dllname version exists in the memory, restart the computer or decompress the original version of the file. If you are running Windows NT, you may need to use the kill or pview tool in Microsoft Windows NT Server 4.0 Resource Kit . For other information, click to view the following Microsoft Knowledge Base Article:

197155 (http://support.microsoft.com/kb/197155/) How to terminate an isolated process

oleinitialize failed (or oleuninitialize failed ).
regsvr32 must first initialize the com library before calling the required com library function and uninitializing the library when it is disabled. If you fail to initialize the com library or cancel the initialization, these error messages will appear. For example, the ole32.dll file may be corrupted or its version is incorrect.
loadlibrary (" dllname ") failed. Getlasterror returns 0x00000485
In winerror. in H, 0x00000485 = 1157 (error_dll_not_found) indicates "one of the library files required to execute the application cannot be found ". For example, if the missing. dll file cannot be found after you type regsvr32 missing. dll, the error message is returned.
loadlibrary (" dllname ") failed. Getlasterror returns 0x00000002
In winerror. H, 0x00000002 = 2 (error_file_not_found), indicating "the specified file cannot be found ". In other words, the system cannot find the relevant DLL. For example, if you type regsvr32 icwdial. dll and the tapi32.dll (dependency) is missing, the error message is returned.
loadlibrary ("dskmaint. dll") failed. Getlasterror returns 0x000001f
In winerror. H, 0x000001f = 31 (error_gen_failure), indicating that "the device connected to the system has no effect ". This happens if you try to register the Win16. dll file. For example, if you type regsvr32 dskmaint. dll, the error message is returned.
dllregisterserver (or dllunregisterserver) in dllname fails. Return code: string
Search for string In winerror. h.