Reliability WaaS Scalability Visibility
Windows Update Certification [& Client] • Intent: when • Targeting should the driver • Classification • Signing and • Ranking be offered? Who validations should receive it? • Customization • Sharing Planning Publishing Driver Servicing Hardware Dev Center Optional: clean WU applicability: install, missing driver CHID centric Co-development Dynamic Update: PnP ranking: FS, upgrade support HWID, Version, Date Missing Driver Critical: automatic push to all clients
Critical Optional Dynamic Update (DU) (Automatic) • New device detected (missing • Upgrade • New device detected (missing driver) driver) • Clean Install • Clean Install • Device Manager "Update • Device Manager "Update Driver…" Driver…" • Client Windows Update • After OOBE Promotion
Check Production Hardware Live for Flighting for Quality partner Signature General WU/AU WU/AU Control Population Telemetry Feedback Flighting Pool
PCI\VEN_1000&DEV_0001& SUBSYS_00000000&REV_02
PnP Ranking General Specific Rank Feature Score (from Windows 10) 0xFF Lower value (0xE8) 1 HWID 2-part HWID 4-part HWID 2 Driver Date 1/1/2015 Newer Date (9/15/2015) 3 Driver Version 1.1.1 Higher version (1.1.2) 4
Driver A Driver B Optional Optional + CHID Driver C Optional Windows Update Driver A is offered and installed. WU applicability applies to CHID.
Driver A Driver B Optional Optional + CHID Driver C Optional Driver D 4part HWID, 2/1/16, Windows Update 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.
Driver B Driver A Critical Critical Driver C Optional Windows Update Driver D 4part 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 B Driver A Critical, DU Critical, DU Driver C Optional Windows Update Driver D 4part HWID, 2/1/16, Ver 1.2 Driver B is offered and installed . WU selects Driver B as a best match for this scenario.
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
Benefits Field 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. Requires Unique 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 provid vide e feedb dback ck on this s session ssion: ht http://aka.ms/ p://aka.ms/wi winhec nhecfeed feedback back
Recommend
More recommend
