INF RegisterDlls Directive

Note If you are building a universal or mobile driver package, this directive is not valid. You can use the Reg2inf tool to convert existing INF RegisterDlls directives into INF AddReg directives in order to make a driver package universal. For more info, see Using a Universal INF File.

A RegisterDlls directive references one or more INF sections used to specify files that are OLE controls and require self-registration.



Each INF section referenced by a RegisterDlls directive must have the following entry format:



A register-dll-section can have any number of entries, each on a separate line.


Specifies the destination directory ID of the file to be registered. For more information, see Using Dirids.

Specifies the directory path, relative to the current directory, to the file to be registered. If not specified, the file is in the current directory.

Identifies the file name of the OLE control to be registered.

Indicates the registration operations to perform on the OLE control. One or both of the following flags must be specified.

Call the OLE control's DllRegisterServer function (described in the Windows SDK documentation).

Call the OLE control's DllInstall function (described in the Windows SDK documentation).

Specifies the time-out, in units of seconds, for an OLE Control to complete the specified registration calls. The default time-out is 60 seconds.

If the control is an executable file, this is a command string that is passed to the executable. The default argument is /RegServer.

If the control is not an executable file, this specifies the command-line argument to pass to the DllInstall function.


Each register-dll-section name must be unique to the INF file and must follow the general rules for defining section names. For more information about these rules, see General Syntax Rules for INF Files.

The following rules apply to the use of the RegisterDlls directive for device installations:

  • Although the syntax permits filename to be either a DLL or an executable file, for device installations only a DLL is allowed.
  • The code to be registered must not prompt for user input.
  • Server-side installations execute in a system context. Therefore, you must be very sure that the code being registered contains no security vulnerabilities and that file permissions prevent the code from being maliciously modified.

For more information about OLE controls and self registration, see the Windows SDK documentation.


RegisterDlls = DialerRegSvr
UnregisterDlls = DialerRegSvr
11,,avtapi.dll, 1

See also