| 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:setupapi.SetupLogFileW |
SetupLogFileW function (setupapi.h) |
The SetupLogFile function adds an entry to the log file. (Unicode) |
|
setup\setuplogfile.htm |
setup |
bc738212-ff81-4b52-b2ef-50aabf6658ab |
12/05/2018 |
SetupLogFile, SetupLogFile function [Setup API], SetupLogFileA, SetupLogFileW, _setupapi_setuplogfile, setup.setuplogfile, setupapi/SetupLogFile, setupapi/SetupLogFileA, setupapi/SetupLogFileW |
setupapi.h |
Windows |
Windows XP [desktop apps only] |
Windows Server 2003 [desktop apps only] |
SetupLogFileW (Unicode) and SetupLogFileA (ANSI) |
Setupapi.lib |
Setupapi.dll |
Windows |
19H1 |
|
|
|
|
|
|
[This function is available for use in the operating systems indicated in the Requirements section. It may be altered or unavailable in subsequent versions. SetupAPI should no longer be used for installing applications. Instead, use the Windows Installer for developing application installers. SetupAPI continues to be used for installing device drivers.]
The SetupLogFile function adds an entry to the log file.
Handle to the file log as returned by SetupInitializeFileLog. The caller must not have passed SPFILELOG_QUERYONLY when the log file was initialized.
Optional pointer to the name for a logical grouping of names within the log file. You should use a null-terminated string. Required if SPFILELOG_SYSTEMLOG was not passed when the file log was initialized. Otherwise, this parameter can be NULL.
Name of the file as it exists on the source media from which it was installed. This name should be in whatever format is meaningful to the caller. You should use a null-terminated string.
Name of the file as it exists on the target. This name should be in whatever format is meaningful to the caller. You should use a null-terminated string.
Optional pointer to a checksum value. Required for the system log.
Optional pointer to the tagfile for the media from which the file was installed. You should use a null-terminated string. The null-terminated string should not exceed the size of the destination buffer. Ignored for the system log if SPFILELOG_OEMFILE is not specified. Required for the system log if SPFILELOG_OEMFILE is specified. Otherwise, this parameter can be NULL.
Optional pointer to the human-readable description of the media from which the file was installed. You should use a null-terminated string. Ignored for the system log if SPFILELOG_OEMFILE is not specified in the Flags parameter. Required for the system log if SPFILELOG_OEMFILE is specified in the Flags parameter. Otherwise, this parameter can be NULL.
Optional pointer to additional information to be associated with the file. You should use a null-terminated string. This parameter can be NULL.
This parameter can be SPFILELOG_OEMFILE, which is meaningful only for the system log and indicates that the file is not supplied by Microsoft. This parameter can be used to convert an existing file's entry, such as when an OEM overwrites a Microsoft-supplied system file.
If the function succeeds, the return value is a nonzero value.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
Note
The setupapi.h header defines SetupLogFile as an alias which automatically selects the ANSI or Unicode version of this function based on the definition of the UNICODE preprocessor constant. Mixing usage of the encoding-neutral alias with code that not encoding-neutral can lead to mismatches that result in compilation or runtime errors. For more information, see Conventions for Function Prototypes.