| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:fileapi.SetFileInformationByHandle | SetFileInformationByHandle function (fileapi.h) | Sets the file information for the specified file. |
| fs\setfileinformationbyhandle.htm | fs | ea4981e6-a8f1-4977-aca9-b2f53604d449 | 12/05/2018 | SetFileInformationByHandle, SetFileInformationByHandle function [Files], fileapi/SetFileInformationByHandle, fileextd/SetFileInformationByHandle, fs.setfileinformationbyhandle, winbase/SetFileInformationByHandle | fileapi.h | Windows.h | Windows | Windows Vista [desktop apps \| UWP apps] | Windows Server 2008 [desktop apps \| UWP apps] | Kernel32.lib; FileExtd.lib on Windows Server 2003 and Windows XP | Kernel32.dll | Windows | Windows SDK on Windows Server 2003 and Windows XP. | 19H1 |
|
|
|
|
|
|
Sets the file information for the specified file.
To retrieve file information using a file handle, see GetFileInformationByHandle or GetFileInformationByHandleEx.
A handle to the file for which to change information.
This handle must be opened with the appropriate permissions for the requested change. For more information, see the Remarks and Example Code sections.
This handle should not be a pipe handle.
A FILE_INFO_BY_HANDLE_CLASS enumeration value that specifies the type of information to be changed.
For a table of valid values, see the Remarks section.
A pointer to the buffer that contains the information to change for the specified file information class. The structure that this parameter points to corresponds to the class that is specified by FileInformationClass.
For a table of valid structure types, see the Remarks section.
The size of lpFileInformation, in bytes.
Returns nonzero if successful or zero otherwise.
To get extended error information, call GetLastError.
Certain file information classes behave slightly differently on different operating system releases. These classes are supported by the underlying drivers, and any information they return is subject to change between operating system releases.
The following table shows the valid file information classes and their corresponding data structure types for use with this function.
| FileInformationClass value | lpFileInformation type |
|---|---|
| FileBasicInfo 0 | |
| FileRenameInfo 3 | |
| FileDispositionInfo 4 | |
| FileAllocationInfo 5 | |
| FileEndOfFileInfo 6 | |
| FileIoPriorityHintInfo 12 |
You must specify appropriate access flags when creating the file handle for use with SetFileInformationByHandle. For example, if the application is using FILE_DISPOSITION_INFO with the DeleteFile member set to TRUE, the file would need DELETE access requested in the call to the CreateFile function. To see an example of this, see the Example Code section. For more information about file permissions, see File Security and Access Rights.
If there is a transaction bound to the handle, then the changes made will be transacted for the information classes FileBasicInfo, FileRenameInfo, FileAllocationInfo, FileEndOfFileInfo, and FileDispositionInfo. If FileDispositionInfo is specified, only the delete operation is transacted if a DeleteFile operation was requested. In this case, if the transaction is not committed before the handle is closed, the deletion will not occur. For more information about TxF, see Transactional NTFS (TxF).
In Windows 8 and Windows Server 2012, this function is supported by the following technologies.
| Technology | Supported |
|---|---|
| Server Message Block (SMB) 3.0 protocol | Yes |
| SMB 3.0 Transparent Failover (TFO) | See comment |
| SMB 3.0 with Scale-out File Shares (SO) | See comment |
| Cluster Shared Volume File System (CsvFS) | Yes |
| Resilient File System (ReFS) | Yes |
SMB 3.0 does not support rename of alternate data streams on file shares with continuous availability capability.
The following C++ example shows how to create a file and mark it for deletion when the handle is closed.
//... HANDLE hFile = CreateFile( TEXT("tempfile"), GENERIC_READ | GENERIC_WRITE | DELETE, 0/* exclusive access */, NULL, CREATE_ALWAYS, 0, NULL); if (hFile != INVALID_HANDLE_VALUE) { FILE_DISPOSITION_INFO fdi; fdi.DeleteFile = TRUE; // marking for deletion BOOL fResult = SetFileInformationByHandle( hFile, FileDispositionInfo, &fdi, sizeof(FILE_DISPOSITION_INFO) ); if (fResult) { // File will be deleted upon CloseHandle._tprintf( TEXT("SetFileInformationByHandle marked tempfile for deletion\n") ); // ... // Now use the file for whatever temp data storage you need,// it will automatically be deleted upon CloseHandle or // application termination.// ... } else { _tprintf( TEXT("error %lu: SetFileInformationByHandle could not mark tempfile for deletion\n"), GetLastError() ); } CloseHandle(hFile); // At this point, the file is closed and deleted by the system. } else { _tprintf( TEXT("error %lu: could not create tempfile\n"), GetLastError() ); } //...