Reliability

Scalability

WaaS

Visibility

• Intent: when

should the driver

be offered? Who

should receive it?

Planning

• Signing and

validations

• Customization

• Sharing

Certification• Targeting

• Classification

Publishing

• Ranking

Windows Update

[& Client]

Driver Servicing Hardware Dev Center Optional: clean

install, missing driver

WU applicability:

CHID centric

Co-development Dynamic Update:

upgrade support

PnP ranking: FS,

HWID, Version, Date

Missing Driver Critical: automatic

push to all clients

Optional

• New device detected (missing

driver)

• Clean Install

• Device Manager "Update

Driver…"

Critical

(Automatic)

• New device detected (missing

driver)

• Clean Install

• Device Manager "Update

Driver…"

• Client Windows Update

• After OOBE

Dynamic Update (DU)

• Upgrade

Promotion

Hardware

partnerFlighting for

WU/AU

Live for

WU/AU

Production

Signature

Check

Quality

Control

Flighting

Pool

General

Population

Telemetry Feedback

PCI\VEN_1000&DEV_0001& SUBSYS_00000000&REV_02

Rank PnP Ranking General Specific

1 Feature Score (from Windows 10) 0xFF Lower value (0xE8)

2 HWID 2-part HWID 4-part HWID

3 Driver Date 1/1/2015 Newer Date (9/15/2015)

4 Driver Version 1.1.1 Higher version (1.1.2)

Windows Update

Driver AOptional+ CHID

Driver BOptional

Driver COptional

Driver A is offered and installed.

WU applicability applies to CHID.

Windows Update

Driver AOptional+ CHID

Driver BOptional

Driver COptionalDriver D

4part HWID, 2/1/16,

Ver 1.2

No driver is offered.

WU picks Driver A as a best match but PnP ranking against local system picks Driver D because Driver D has newer driver date.

Windows UpdateDriver D4part HWID, 2/1/16,

Ver 1.2

Driver B is offered and installed.

WU selects Driver B then PnP ranking also selects Driver B as a better match.

Driver ACritical

Driver BCritical

Driver COptional

Windows Update

Driver B is offered and installed .

WU selects Driver B as a best match for this scenario.

Driver ACritical, DU

Driver BCritical, DU

Driver COptional

Driver D4part HWID, 2/1/16,

Ver 1.2

After RTM + 90 days: Must use RS1 HLK certified driver

After RTM + 90 days: Must use RS1 HLK

All RS1 HLK drivers must be HyperVisor Code Integrity (HVCI) compliant

Sysdev.Microsoft.com

Current portal will be used for RS1

RS1 driver signing will be enabled from RTM

Publishing block list will be updated

Sysdev@Microsoft.com

DDCHelp@Microsoft.com

Launch this fall

• Once rolled back, driver not re-offered

• Utilize feedback to improve understand customer intent

Administrators can set this key to test their environments

Don’t be the last one to move to Minifilter model.

DDChelp@Microsoft.com

BenefitsField update for system and device firmware through WU

Enables resolution of firmware based vulnerabilities and issues

Improve customer experience overall and keep systems up to date for improved customer satisfaction.

RequiresUnique GUID (per version of firmware) in EFI System Resource Table (ESRT)

UpdateCapsule() enabled

Capsule with self contained payload tested and uploaded to Windows Update

UEFI firmware requires PCR7 compliance

http://sysdev.microsoft.com

https://msdn.microsoft.com/en-us/library/windows/hardware/ff549731(v=vs.85).aspx

https://msdn.microsoft.com/en-us/library/windows/hardware/br230778(v=msdn.85).aspx

http://go.microsoft.com/fwlink/p/?LinkId=617374

https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx

http://download.microsoft.com/download/A/D/6/AD6D9B14-5810-4BB3-A548-E128E7509032/Windows Device Driver Installation Applications.docx

https://msdn.microsoft.com/en-us/library/windows/hardware/ff546225(v=vs.85).aspx

https://msdn.microsoft.com/en-us/library/windows/hardware/dn917887(v=vs.85).aspx

https://msdn.microsoft.com/library/windows/hardware/br230796.aspx

https://technet.microsoft.com/itpro/windows/plan/windows-update-for-business

Please provide feedback on this session:

http://aka.ms/winhecfeedback