In This Article
This section describes precautions and precautions installation driver errors that can result from the automatic INF check performed by Microsoft Visual Studio or each time you run the InfVerif tool.
Starting with Visual Studio 2015 with WDK 10, when you create a driver, you can typically get the following INF file errors in the Error List window. When you run InfVerif.exe via the command line type, this tool throws command line errors, according to the HTML version of my results.
Guidelines For Rules, Errors
Confirm that the lower the error, the more serious the problem.
Most error codes can be either a warning or an error, depending on the reasons given in infverif.
Error Handling
You must run all bugs to submit for testing drivers in the Hardware Development Center dashboard. Errors are possibleUnder the following conditions:
While you don’t need to resolve the issue before submitting the driver to the development center, we recommend that you take the time during the day to sort out the issue. If you are not supported by a warning, your INF may not behave as far as you would expect.
General warnings related to:
Problems related to a generic setting will show up as errors if:
flag
Support questions related to universal setup appear as warnings in the following cases:
Error Codes
Discount codes are errors classified into the following categories:
How do I find the root of a program in Windows?
No driver, (1320–1329)
INF File Syntax (1100-1299)
Even though the infverif error causes the driver upload to fail, the driver installation can still complete successfully.
Because when installing the driver, sometimes there are errors in the INF fileWindows tries to use the default value for the parameter.
Windows cannot increase the driver due to errors in which range, but errors in this range indicate that the behavior may be reversed depending on the operating system or SKU version.
Where the where driver is set correctly, these errors indicate that, under normal circumstances, the where driver may not be set correctly.
[Original DisksFiles]
DriverFile.sys=1.x64
[target directories]
CopyFileSection=13,Subdirectory
[copy la section of file]
DriverFile.sys
A driver store that preserves the form of the package’s original driver directory. In the code above, the From source location is DriverFile.sys Inf, locationd, statement, but CopyFiles places the INF in location\SubDirectory. Display errorShrinks just as if the file had been renamed copy to pages. Section
[My installation section]
CopyFiles=driver_file.sys
This error is reported primarily when the copyfiles directive expects a section name die (with often the most related list of files to copy). directive However CopyFiles can specify the name of a person from a file. To differentiate between the a section, and hence naming the file, the name is preceded by a real @, as shown here:
[My setup]
CopyFiles=@driverFile section.sys
[Performance]
Signature=”$WindowsNT$”
class = pattern
Class Guide = 78A1C341-4539-11d3-B88D-00C04FAD5171
Provider=”Microsoft”
Note that although most of the time this is actually an error, in some cases the message 1205 is displayed without questions, although the condition may be intentional.

In this example, the entire setup section of a .INF refers to the useful equivalent in the setup section of b .INF.
A.INF contains:
A.INF
[Install Section A]
Enable=B.INF
Required = installsectionb URL
AddReg=; 1220

[InstallSectionA warning.Services]
Enable=B.INF
Requirements means InstallSectionB.Services
How do I get the description of a system error?
B.INF contains:
B.INF
[InstallSectionB]
AddReg = AddRegB
[InstallSectionB.Services]
…
[AddRegB]
… Needs
The directive must refer to the appropriate section to be processed in the current message setup. For example, the statement Needs [InstallSectionA in .Services] is no doubtMust refer to .Services in another installation section. The needs directive can also be used for the include behavior from another DDInstall section of the INF file itself. This policy requires sections, which may result in undesired behavior. not possible
If you are using HKR, the no-log value will persist until the device needs to be installed.
[Original Volumes
Pay DisksFiles]
filename=identifier note that this errorThis is repeated when [sourcedisksfiles] architecture versions differ [SourceDisksFiles (e.g. .But amd64], architectures, all non-INF supported ones that have a [sourcedisksfiles] section.
catalog file = wudf.cat
This error often occurs when your .inf file contains a value containing a registry aspect of the environment. For example:
This line causes the INF parser to try to find my “SystemRoot” token from the [Strings] head, rather than the expected character storing the literal “%SystemRoot%” in register. To use the actual value of %systemroot% as meaningful instead of string substitution, useUse the %% sequence bus.
[MyAddReg]
HKR,,DllPath,%SystemRoot%\System32\myDll.sys
[MyAddReg]
HKR,,DllPath,%%SystemRoot%%\System32\myDll.sys