- #HOW TO CHANGE FILE EXTENSION WINDOWS 10 INSTALL#
- #HOW TO CHANGE FILE EXTENSION WINDOWS 10 UPDATE#
- #HOW TO CHANGE FILE EXTENSION WINDOWS 10 DRIVER#
- #HOW TO CHANGE FILE EXTENSION WINDOWS 10 SOFTWARE#
- #HOW TO CHANGE FILE EXTENSION WINDOWS 10 CODE#
This example uses INF AddComponent directive to create components that install a service and an executable.
#HOW TO CHANGE FILE EXTENSION WINDOWS 10 DRIVER#
The following snippet is a complete extension INF that is included in the Driver package installation toolkit for universal drivers.
#HOW TO CHANGE FILE EXTENSION WINDOWS 10 SOFTWARE#
HKR,FriendlyName, "New Device Friendly Name"ĭevice.ExtensionDesc = "Sample Device Extension"Įxample 2: Using an extension INF to install additional software %Device.ExtensionDesc% = DeviceExtension_Install, PCI\VEN_XXXX&DEV_XXXX&SUBSYS_XXXXXXXX&REV_XXXX The ExtensionId values replace with your own GUID To illustrate, consider the following scenario that includes a hypothetical device for which there are three extension INFs: The driver date and driver version specified in the INF are used, in that order, to choose the single INF between multiple extension INFs with the same ExtensionId. The system identifies possible extension INFs for a specific device by matching the hardware ID and compatible IDs of the device to those specified in an extension INF in a Models section that applies to that system.Īmong all possible extension INFs that specify the same ExtensionId value, the system selects only one to install and applies its settings over those of the base INF. When you write an extension INF, you generate a special GUID called the ExtensionId, which is an entry in the INF's section. It is helpful to include comments in the base INF describing which entries can be overridden by an extension INF, as well as applicable parameter value ranges and constraints. Distinct extension INFs targeted at the same devices should not attempt to alter the same settings. If multiple extension INFs are installed on the same device, there is no predetermined ordering that the extension INFs will be applied in, so one extension INF cannot deterministically override values provided by a different extension INF. Similarly, if the base INF changes, the extension INF remains and is applied over the new base INF. As a result, if an extension INF and a base INF specify the same setting, the version in the extension INF is applied. How extension INF and base INF work togetherĭuring a device installation, settings in an extension INF are applied after settings in a base INF. The diagram also shows how an extension INF can reference a component INF, which can in turn reference software modules to install. The first contains just an extension INF, and the second contains a component INF and a legacy software module. In the following diagram, two different companies have created separate driver packages for the same device, which are shown in the dotted lines. Also see DCH-Compliant Driver Package Example, which describes how the DCHU universal driver sample uses extension INFs.
#HOW TO CHANGE FILE EXTENSION WINDOWS 10 CODE#
You can find sample code for some of these scenarios in the examples below.
#HOW TO CHANGE FILE EXTENSION WINDOWS 10 UPDATE#
This resulted in large, complex driver packages that included code for all scenarios and configurations, and each minor update required an update to the entire driver package. Prior to Windows 10, Windows selected a single driver package to install for a given device.