This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
Closes an open object handle.
BOOL CloseHandle( [in] HANDLE hObject);
[in] hObject
A valid handle to an open object.
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, callGetLastError.
If the application is running under a debugger, the function will throw an exception if it receives either a handle value that is not valid or a pseudo-handle value. This can happen if you close a handle twice, or if you callCloseHandle on a handle returned by theFindFirstFile function instead of calling theFindClose function.
TheCloseHandle function closes handles to the following objects:
Generally, an application should callCloseHandle once for each handle it opens. It is usually not necessary to callCloseHandle if a function that uses a handle fails with ERROR_INVALID_HANDLE, because this error usually indicates that the handle is already invalidated. However, some functions use ERROR_INVALID_HANDLE to indicate that the object itself is no longer valid. For example, a function that attempts to use a handle to a file on a network might fail with ERROR_INVALID_HANDLE if the network connection is severed, because the file object is no longer available. In this case, the application should close the handle.
If a handle is transacted, all handles bound to a transaction should be closed before the transaction is committed. If a transacted handle was opened by callingCreateFileTransacted with the FILE_FLAG_DELETE_ON_CLOSE flag, the file is not deleted until the application closes the handle and callsCommitTransaction. For more information about transacted objects, seeWorking With Transactions.
Closing a thread handle does not terminate the associated thread or remove the thread object. Closing a process handle does not terminate the associated process or remove the process object. To remove a thread object, you must terminate the thread, then close all handles to the thread. For more information, seeTerminating a Thread. To remove a process object, you must terminate the process, then close all handles to the process. For more information, seeTerminating a Process.
Closing a handle to a file mapping can succeed even when there are file views that are still open. For more information, seeClosing a File Mapping Object.
Do not use theCloseHandle function to close a socket. Instead, use theclosesocket function, which releases all resources associated with the socket including the handle to the socket object. For more information, seeSocket Closure.
Do not use theCloseHandle function to close a handle to an open registry key. Instead, use theRegCloseKey function.CloseHandle does not close the handle to the registry key, but does not return an error to indicate this failure.
dwPriorityClass = 0;hProcess = OpenProcess( PROCESS_ALL_ACCESS, FALSE, pe32.th32ProcessID );if( hProcess == NULL )printError( TEXT("OpenProcess") );else{dwPriorityClass = GetPriorityClass( hProcess );if( !dwPriorityClass )printError( TEXT("GetPriorityClass") );CloseHandle( hProcess );}
To see this example in context, seeTaking a Snapshot and Viewing Processes.
Requirement | Value |
---|---|
Minimum supported client | Windows 2000 Professional [desktop apps | UWP apps] |
Minimum supported server | Windows 2000 Server [desktop apps | UWP apps] |
Target Platform | Windows |
Header | handleapi.h (include Windows.h) |
Library | Kernel32.lib |
DLL | Kernel32.dll |
Was this page helpful?
Was this page helpful?