Microsoft KB Archive/171261

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft Win32 Application Programming Interface (API), included with:
 * Microsoft Windows NT, versions 3.51, 4.0

-

SYMPTOMS
The Remote registry API, RegConnectRegistry, allows a Win32 application to make registry API calls across the network. When an application calls this API, a named pipe connection between the two machines is created. Registry information is communicated between the machines through this named pipe connection. When the application is finished with the remote connection, it must call RegCloseKey to close the registry handle.

A problem occurs when the named pipe connection, through which the registry information is communicated between the two machines, stayed open after RegCloseKey closed the connection handle.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Windows NT 4.0, Service Pack 2.

Additional query words: winnt regapi

Keywords         : kbprg kbKernBase kbRegistry kbGrpKernBase Version          : winnt:3.51,4.0 Platform         : winnt Issue type       : kbbug
 * }