INF-206x Exam Guide: Build a Focused Windows INF and Driver-Installation Study Plan
INF-206x should be approached as a Windows driver-installation and INF-file assessment: the supplied Microsoft Learn material centers on how INF files describe driver packages, target platforms, device models, directives, SetupAPI access, component packages, and extension-INF publishing. The available research does not include an official INF-206x blueprint, score, question count, duration, prerequisite, or delivery format. This guide therefore helps you make the practical decision that matters first: whether your current work involves enough INF and driver-packaging detail to justify focused preparation, and which technical areas to study before checking Microsoft’s current exam information.
What the available evidence says INF-206x is likely to assess
The supplied official material supports preparation around Windows INF files and driver-package installation rather than general Windows administration. Treat the topic list below as an evidence-based preparation scope, not as a published INF-206x exam blueprint, because no official domain list or measured-skill document was supplied.
An INF file is a text file in a driver package that contains the information device-installation components use to install a driver package on a device. The same file can specify drivers and device-specific configuration or settings that bring the device online. That definition is the foundation for the rest of your study plan.
The strongest evidence points to five connected abilities: reading the structure of an INF, selecting the correct manufacturer and Models section, targeting architectures and operating-system versions, interpreting installation directives, and understanding how component and extension INFs fit into a driver package. SetupAPI access and Partner Center publishing add an operational layer.
Do not turn that evidence into an unsupported claim that these are the official exam domains or that every topic receives equal attention. Before scheduling, look for a current Microsoft page that identifies INF-206x by its exact code and confirms the exam’s audience, skills measured, and delivery arrangements.
Who should use this preparation path
This path is most suitable for driver developers, device manufacturers, installation-tool developers, and engineers who review or package Windows drivers. It is also useful for technical candidates who must reason about why a device package applies to one Windows platform but not another. It is less suitable as a first introduction to programming or hardware fundamentals.
Which skills deserve the most study time
Spend the most time on decisions that connect several INF concepts: mapping a Manufacturer entry to the correct Models section, predicting Windows section selection, and checking whether directives are valid in the package type being built. Memorizing directive names without tracing their installation effect is a weak preparation method.
Start by being able to explain the path from [Manufacturer] to a per-manufacturer Models section. The Manufacturer section identifies a device manufacturer and points to the section containing that manufacturer’s device models. A localized token such as %strkey% must be defined in the INF Strings section, and the referenced Models section name must correspond to a section elsewhere in the file.
Next, practise reading decorated names rather than treating every section as universal. Windows can use TargetOSVersion entries to select different Models sections for different operating-system versions. The official material says Windows chooses the Models section that most closely matches the operating-system version on which it is executing.
Then add architecture, product type, suite, and build reasoning. For non-x86 targets beginning with Windows Server 2003 SP1, the associated Models-section names must use platform extensions such as .ntamd64, .ntia64, .ntarm, or .ntarm64. Architecture decoration is optional for x86-based targets but recommended by Microsoft.
Finally, learn to distinguish applicability from installation action. A decorated section determines when a block is considered; directives inside the selected installation section determine what files, registry entries, services, interfaces, or related components are installed.
Use a section-resolution worksheet
For each practice INF, write down the running architecture, operating-system version, product type, suite, and build when relevant. List every candidate Models section, eliminate sections whose decoration is too specific or inapplicable, and identify the closest remaining match. This forces you to reason from the rules instead of guessing from section order.
Understand the role of INX files
An INX file is an INF containing string variables for information such as version information, target architecture, and the current Windows Driver Framework version. The Build utility and Stampinf replace those variables with text representing a specific architecture or framework version. Study this as a build-and-generation concern, not as a replacement for understanding the resulting INF.
How to read an INF without missing the installation consequence
Read an INF in three passes: identify the package’s purpose, resolve which decorated sections apply, and then trace every directive in the selected installation path. This sequence prevents a common mistake—studying a directive in isolation while overlooking that Windows may never select the section containing it.
The Summary of INF Directives lists AddReg, CopyFiles, AddService, and AddInterface among commonly used directives. AddReg references registry sections; CopyFiles references file-list sections; AddService references service-install sections and may also reference event-log installation sections; AddInterface references an add-interface section that in turn uses AddReg.
Build a simple dependency map while studying. Put the selected Models entry at the top, connect it to the relevant DDInstall section, and branch from there to file copying, registry changes, service registration, interfaces, and any included or needed sections. The map should answer “what is installed, where, and under which condition?” rather than merely list directive definitions.
Pay attention to restrictions. The official directive summary identifies DelReg, DelFiles, and DelService as invalid when building a universal or Windows Driver driver package. That kind of package-specific validity rule is more useful to practise than memorizing a long alphabetical catalogue of directives.
Directive names are case-insensitive, so Addreg, addReg, and AddReg are equivalent directive specifications. Do not spend study time treating capitalization as a semantic difference. Spend it checking section references, file lists, service settings, and package constraints.
A practical annotation method
Print or copy a small practice INF into an editor and annotate each line with one label: identification, applicability, file movement, registry, service, interface, component, or versioning. Afterward, explain the installation in plain language. If you cannot explain a line’s effect or dependency, flag it for documentation review instead of inventing an interpretation.
How to reason about architectures and operating-system versions
Cross-platform INF work depends on matching both sides of a decoration: the Manufacturer entry and the associated Models section name. A platform suffix in only one place can make the intended mapping fail. Study paired names and test how Windows chooses among several candidates.
Microsoft documents platform extensions including .ntamd64 for x64-based systems supported by Windows XP and later, .ntia64 for Itanium-based systems supported by Windows XP and later, .ntx86 for x86-based systems supported by Windows XP and later, .ntarm for Arm-based systems supported by Windows 8 and later, and .ntarm64 for Arm64-based systems supported by Windows 10 version 1709 and later.
For Windows XP through Windows 10, version 1511, TargetOSVersion decoration follows the form NT[Architecture][.[OSMajorVersion][.[OSMinorVersion][.[ProductType][.SuiteMask]]]]. Starting with Windows 10, version 1607, the format can also include a build number: NT[Architecture][.[OSMajorVersion][.[OSMinorVersion][.[ProductType][.[SuiteMask][.[BuildNumber]]]]]. Learn the fields as a selection rule, not as a string to recite without context.
The supplied official examples show why ordering and specificity matter. A Manufacturer entry can point to sections such as [FooMfg.NTamd64.6.1], [FooMfg.NTamd64.10.0], and [FooMfg.NTamd64.10.0...14393]. Windows uses the closest applicable section; a more specific version or build condition can take precedence over a broader match.
An empty Models section is also meaningful. Microsoft documents that an empty section can explicitly exclude an operating-system version, product type, or suite. When reviewing a practice file, never assume an empty section is unfinished until you have checked whether it is deliberately blocking installation.
The mistake to avoid with build numbers
A build number is evaluated only when the operating-system major and minor version in the decoration exactly matches the current operating-system version or AltPlatformInfo version. If the current OS version is greater than the version named by the decoration, the section is considered applicable regardless of the specified build number. Use the official selection rules when working through edge cases.
The mistake to avoid with legacy assumptions
Do not carry old undecorated-section assumptions into newer targets. Microsoft recommends decorating Models entries for Windows XP and later. For operating-system versions earlier than Windows XP, an INF intended to work there must also contain an undecorated Models section named [FooMfg].
What to learn about component INFs
Component INF questions require you to separate basic device functionality from optional device software. A software component is a standalone driver package that can install one or more software modules, while the parent device remains the relationship that allows the software-enumerated child device to function.
An extension INF can use AddComponent in an INF DDInstall.Components section. The system creates a virtual software-enumerated child device for each referenced software component, and more than one driver package can reference the same component. Virtual device children can be updated independently as long as the parent device is started.
Microsoft recommends separating functionality into groupings that make sense for servicing and creating one software component for each grouping. That is a design principle worth understanding because it links INF structure to update and removal behavior. It is more useful than simply remembering that a component INF exists.
If a component INF specifies AddSoftware, it must be a universal INF and must specify the SoftwareComponent setup class. Type 1 of AddSoftware must be used from a Component INF. Type 2 does not require a Component INF and can be used in any INF that succeeds.
A component device does not require a function-driver service. It can use AddService for Win32 user services and AddReg or CopyFiles to install software. If the parent device has no available driver, developers can create one and optionally use the Windows pass-through driver umpass.sys so the parent can start.
A useful comparison exercise
Create two diagrams: one for a base device driver and one for an optional software component. Mark which package provides basic device operation, which package creates the child device, what must be running first, and which package can be serviced or uninstalled independently. This exposes relationship errors that flashcards rarely reveal.
What to study about SetupAPI access
Setup applications access INF content through SetupAPI functions, beginning by opening the file and ending by closing the handle. This area is practical for developers who build installation tools or inspect packages programmatically, and it should be studied as an ordered workflow.
If the application knows the file name, it can call SetupOpenInfFile to obtain a handle. If it does not know the file name, SetupGetInfFileList can obtain a list of INF files in a directory. SetupOpenAppendInfFile can append another file to the opened INF; if no file is specified, the LayoutFile entry in the INF Version section supplies the file to append.
When the information is no longer needed, SetupCloseInfFile releases resources allocated when the file was opened. Treat that close operation as part of the lifecycle, not as an unrelated API detail.
For retrieval, distinguish file-level, version-level, source, target, line, and field information. SetupGetInfInformation, SetupQueryInfFileInformation, and SetupQueryInfVersionInformation retrieve information about an INF. SetupGetSourceInfo and SetupGetTargetPath obtain source and destination information. SetupGetLineText and SetupGetStringField access line or field content directly.
A good practice question should ask you to choose the appropriate operation and explain why. For example, listing candidate files, opening one, reading its version information, querying a target path, and releasing the handle are different tasks even though they all involve the same INF.
Study API names by purpose
Group functions into a small table with columns for discovery, opening, appending, metadata, source or target paths, line or field access, and closing. Then cover the function names and reconstruct the workflow from memory. This produces usable recall without encouraging blind memorization.
How extension INF publishing changes the study problem
Extension INF preparation combines package separation, version lineage, submission packaging, and distribution. It is not enough to know what an extension INF contains; you must understand how Microsoft’s Windows Hardware Dashboard workflow treats the base driver and each extension.
Microsoft recommends a separate submission for each extension INF and a separate submission containing only the base driver. Combining the base driver and extensions in one submission can cause shipping labels to be classified as Extension Drivers and can cause users to download packages multiple times when applicable extensions are detected.
For the base package, the documented workflow uses the base driver files with the HLK results. For an extension package, the extension INF and referenced binaries are added using the same HLK results, with only one extension INF in the driver folder for that package. The process is repeated separately for additional extension INFs.
The ExtensionID is a generated GUID used for driver-lineage identification and versioning. Generate a new ExtensionID for the initial version of an extension INF. When updating an already published extension INF, keep the ExtensionID and increment the version or date in DriverVer.
Extension drivers are ranked by date and version, which are included in DriverVer. The official material also states that when a base-driver update is applied, the installed extension INF is evaluated and applied if necessary. These rules make lineage and versioning central study topics.
Publishing to Windows Update requires automatic driver-promotion selections on the shipping label, and the supplied research says extension INFs cannot be published as optional because they are not listed in Device Manager for an end user to initiate an Update Driver action. Publishing requirements can change, so verify the live documentation before acting on this information.
A publishing checklist for revision
Before reviewing a hypothetical submission, ask: Is the base package separate? Is each extension packaged separately? Is the ExtensionID new or intentionally retained? Has DriverVer changed for an update? Are referenced binaries included? Is the intended sharing or publishing action represented by the shipping label? This checklist turns policy into a repeatable review.
Which official material to read first
Read the INF overview before the detailed references, then move to Manufacturer-section selection, cross-platform decoration, directives, component INFs, SetupAPI access, and extension-INF publishing. This order follows the dependency chain from purpose to syntax, applicability, installation behavior, application access, and distribution.
Begin with Overview of INF Files: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/overview-of-inf-files. Extract the definition of an INF, the role of device configuration, and the distinction between INF and INX.
Read INF Manufacturer Section next: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-manufacturer-section. Focus on the Manufacturer-to-Models relationship, TargetOSVersion, closest-match selection, exclusions, and the examples involving architecture, version, product type, suite, and build.
Use Creating INF Files for Multiple Platforms and Operating Systems at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/creating-inf-files-for-multiple-platforms-and-operating-systems to consolidate platform suffixes and legacy behavior. Keep a comparison table rather than highlighting the page repeatedly.
Read Summary of INF Directives at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/summary-of-inf-directives after you understand section selection. Prioritize AddReg, CopyFiles, AddService, AddInterface, and the restrictions on deletion directives in universal or Windows Driver packages.
Then study Using a Component INF File at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/using-a-component-inf-file and Accessing INF Files from a Device Installation Application at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/accessing-inf-files-from-a-setup-application. Finish with Working with extension INF files in the Windows Hardware Dashboard at https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/submit-dashboard-extension-inf-files.
The pages are reference material, not a substitute for an official INF-206x skills-measured document. Check each page’s current version and related links, especially before relying on publishing or operating-system support details.
How to take notes that remain useful
For every topic, record four items: the object being described, the condition under which it applies, the action it causes, and one failure or exclusion case. For example, for TargetOSVersion, note what it targets, how Windows compares it, what section it selects, and when a build decoration is ignored or invalid.
A practical four-stage preparation roadmap
Use a staged plan that moves from recognition to explanation and then to review. The goal is not to collect more notes; it is to become able to predict package behavior, justify the prediction from Microsoft documentation, and identify an unsupported or inconsistent INF design.
Stage one: establish vocabulary and structure. Define INF, INX, Manufacturer section, Models section, TargetOSVersion, platform extension, DDInstall section, component INF, ExtensionID, DriverVer, and SetupAPI. Draw the relationship between each term and write one sentence describing its role.
Stage two: practise applicability. Take several small Manufacturer entries and resolve them against different architecture and operating-system conditions. Include a broad section, a platform-specific section, a version-specific section, and an empty exclusion section. Explain why the selected section wins and cite the relevant Microsoft Learn page in your notes.
Stage three: trace installation. For each selected Models section, follow the referenced installation sections and classify AddReg, CopyFiles, AddService, and AddInterface actions. Add a second exercise that includes a component device and identify the parent-start requirement and independent servicing relationship.
Stage four: review operational scenarios. Work through a base-driver submission, an extension submission, an ExtensionID update, a DriverVer change, and a SetupAPI inspection workflow. At the end of this stage, write a short justification for each decision without looking at the source.
Use retrieval practice between stages. Close the documentation and answer “which section applies?”, “what does this directive change?”, or “what package relationship is being created?” Then reopen the source to correct the explanation. Mark uncertainty explicitly; an unresolved question is a better next action than a confident guess.
If your study time is limited
Prioritize Manufacturer and Models selection, platform and operating-system decoration, directive effects, and component relationships. Add SetupAPI if your role includes installation applications, and add extension-INF publishing if you submit or distribute drivers. Do not spend equal time on every directive when the supplied evidence gives stronger support to these decision-heavy areas.
If you already develop drivers
Skip basic terminology only after you can explain it accurately. Use your existing package as a review object, but remove proprietary identifiers and binaries from any shared material. Compare its section names, architecture targeting, service actions, component boundaries, and versioning logic against the official references.
Mistakes that make INF preparation inefficient
The most damaging study mistakes are confusing a reference page with an exam blueprint, memorizing directives without tracing their context, and treating section names as comments rather than selection logic. Correct these habits before adding more material.
Do not infer official exam weightings from the number of Microsoft pages supplied. The research contains no INF-206x percentages, so this guide does not assign or compare blueprint weights. If a current official blueprint provides percentages later, always name the full domain beside each percentage rather than comparing unlabeled figures.
Do not assume that a newer operating system automatically selects the newest-looking section. Windows evaluates decorated sections according to version, architecture, product type, suite, and, where applicable, build rules. Work through the documented selection logic.
Do not assume an empty Models section is an error. It can explicitly exclude an operating-system version, product type, or suite. Conversely, do not assume a missing decorated section will fall back in the way you intended; verify the documented matching behavior.
Do not mix base-driver and extension-INF packaging practices. The supplied publishing guidance specifically recommends separate submissions. Treat the submission boundary as part of the design, not as an administrative step to handle after packaging.
Do not study leaked questions, dumps, or claims that memorization guarantees a pass. They cannot replace understanding INF applicability and installation behavior, and this guide does not imply access to live exam content.
Do not rely on stale delivery information. No official source supplied here confirms INF-206x’s current delivery method, location, languages, duration, score, or scheduling rules. Confirm those details through the current official Microsoft certification or exam page before paying or booking.
A quick self-audit
You are ready to move from reading to scheduling research when you can explain a section-selection result, distinguish a component INF from a base package, identify the effect of the core directives, outline SetupAPI file access, and describe why ExtensionID and DriverVer matter. If one area remains weak, study that area rather than restarting the entire sequence.
What to verify before scheduling INF-206x
Scheduling should wait until the official listing confirms that INF-206x is active and identifies its current requirements. The supplied sources explain Windows driver technology but do not verify the exam’s current status, registration process, price, delivery channel, time limit, languages, score, question count, prerequisites, or retake rules.
Search Microsoft’s official certification and exam catalogue using the exact code INF-206x. Confirm the exam title, intended audience, measured skills, prerequisites, delivery options, identification rules, accommodation process, and any policy links. Record the page’s update date because exam information can change.
If the official listing provides a skills-measured document, replace this evidence-based topic map with that document as your primary scope. Preserve the Microsoft Learn references as technical reading, but reorganize your study time around the official domains and any stated weighting.
Before booking, check whether the registration provider and account identity requirements match your situation. Because no such details are present in the supplied research, this guide deliberately does not supply a provider name, fee, appointment duration, or scheduling instruction as fact.
After scheduling, create a final review list from your own weak areas: section resolution, decoration syntax, directive restrictions, component-parent relationships, SetupAPI lifecycle, or extension packaging. Use documentation and your own controlled exercises; do not seek or use purported live questions.
A sensible final-week decision
In the final review period, stop expanding the topic list. Resolve a few representative INF scenarios from first principles, revisit only the official pages that correct errors, and confirm the exam logistics from the live official listing. If the listing does not confirm a detail, treat it as unknown rather than filling the gap with catalogue-site speculation.
The next action after reading this guide
Start with one small INF and produce a written section-resolution and installation-impact analysis. Then compare every conclusion with Microsoft Learn, identify one unsupported assumption, and use that gap to choose your next study block. Separately, locate the current official INF-206x listing before making any payment or appointment decision.
Use these next actions in order: verify the official exam page; download or record the current skills-measured information if available; read the INF overview and Manufacturer-section references; complete an architecture and operating-system selection worksheet; trace directives through a package; review component and extension-INF scenarios; and perform a final logistics check.
This approach keeps technical preparation and scheduling decisions separate. The supplied evidence is strong enough to guide study of Windows INF and driver-package behavior, but it is not a substitute for current exam-specific requirements. Let the official INF-206x listing determine whether the exam is available and how it is delivered; let the Microsoft Learn documentation determine how you understand the technology.
Conclusion
Prepare for INF-206x by practising the decisions that make INF files work: which Models section applies, what each directive installs or changes, how components relate to a parent device, how SetupAPI reads package information, and how extension packages are versioned and submitted. The supplied research does not establish the exam’s blueprint or logistics, so verify those points on the current official Microsoft listing before scheduling. A short, source-checked package analysis is the best immediate next step.
Related exams
- 77-725 exam — Microsoft Word 2016 Core: Document Creation, Collaboration and Communication (MOS)
- 77-727 exam — Excel 2016: Core Data Analysis, Manipulation, and Presentation
- 77-728 exam — Excel 2016 Expert: Interpreting Data for Insights
- 77-731 exam — Outlook 2016: Core Communication, Collaboration and Email Skills
- AZ-120 exam — Planning and Administering Microsoft Azure for SAP Workloads
- AZ-400 exam — Microsoft Azure DevOps Solutions
