Windows 10 Driver Publishing Workflow

Windows 10 Initial Driver Publishing Workflow (29 April 2015)

1. Driver Submission Options

The initial release of the Windows 10 driver publishing workflow will be available to hardware partners on 29 April 2015. It will consist of the features in List :

List : Windows 10 Initial Driver Publishing Features (29 April 2015)

• 
  HLK Signing
  
• 
  Driver Signing (New)
  
• 
  Submission for Missing Drivers and Update Driver scenarios
  
• 
  AutoUpdate scenario support using [e-mail]
  

Figure : Windows 10 Initial Driver Publishing Workflow (29 April 2015)

List : Windows 10 Initial Driver Publishing Workflow Steps (29 April 2015)

1. 
   The hardware partner submits a high-quality, production-release-quality driver to the DevCenter Dashboard. It may or may not be accompanied by WHLK logs. If the partner omits the optional WHLK logs then they must assert to the compatibility of the driver.
   The DevCenter Dashboard validates the logs (if provided). If the WHLK logs do not pass validation or the partner does not asert then the submission is rejected and the hardware partner is informed. The workflow then ends.
   If the hardware logs are successfully validated or the partner asserted then the workflow continues.
   Note that the submitted driver is expected to be production-release quality before submission. The hardware partner must have already performed necessary testing to ensure the submitted driver is of high quality.
   
2. 
   The driver package is archived in the DevCenter Dashboard database.
   
3. 
   The hardware partner can now download the signed driver (option in Figure ).
   
4. 
   The hardware partner may publish the driver to Windows Update (option in Figure ).
   

Publishing the driver will result in making the driver available for the Missing Driver scenario.

Once published, the partner may contact DDCHelp ([e-mail]) to include the driver for Auto Update scenarios (option in Figure ). Doing so requires Microsoft approval.

All published drivers will go to Windows Update Live and will be available broadly.

Note that there is no Windows Update Preview.

5. 
   The driver is moved into Windows Update Live.
   
6. 
   The public now has access to the driver.
   

5. Windows 10 Release Driver Publishing Workflow

   1. New Features

The Windows 10 driver publishing workflow which will be available to hardware partners at Windows 10 release will consist of the features made available at 29 April 2015 (List ) and the additional features in List :

List : Windows 10 release Driver Publishing Features

• 
  Distribution Targeting
  
• 
  Installation Targeting
  
• 
  Initial Distribution Ramp Up
  

2. Driver Publishing Workflow

Figure : Windows 10 Release Driver Publishing Workflow



List : Windows 10 release Driver Publishing Workflow Steps

1. 
   The hardware partner submits a -uality, production-release-quality driver to the DevCenter Dashboard. It may or may not be accompanied by WHLK logs. If the partner omits the optional WHLK logs then they must assert to the compatibility of the driver.
   The DevCenter Dashboard validates the logs (if provided). If the WHLK logs do not pass validation or the partner does not assert then the submission is rejected and the hardware partner is informed. The workflow then ends.
   If the hardware logs are successfully validated or the partner asserted then the workflow continues.
   Note that the submitted driver is expected to be production release quality before submission. The hardware partner must have already performed necessary testing to ensure the submitted driver is of high quality.
   
2. 
   The signed (and pre-signed) driver package is archived in the DevCenter Dashboard database.
   
3. 
   The hardware partner can now download the signed driver (option in Figure ).
   
4. 
   The hardware partner may publish the driver to Windows Update (option in Figure ).
   

The hardware partner may now specify specific OEM systems that the driver is to be distributed to. This distribution targeting is discussed later in the section on Error: Reference source not found .

Publishing the driver will result in making the driver available for the Missing Driver scenario.

Once published, the IHV may contact Microsoft to include the driver for Auto Update scenarios (option in Figure ). Doing so requires Microsoft approval.

All published drivers will go to Windows Update Live and will be available broadly.

Note that there is no Windows Update Preview.

5. 
   The driver is moved into Windows Update Live.
   
6. 
   The public has access to the driver. The driver may go through the Windows Update Live availability ramp up period as described in Error: Reference source not found.
   

3.