Improving Driver Availability Improving Driver Quality

CEIP (Microsoft Customer Experience Improvement Program) Systems report a DNF when a driver is not found for an installed device Kernel mode drivers: OCA User mode drivers: CEIP Availability gaps by systems Availability gaps by DNF events Availability gaps by market share

Sources = Microsoft CEIP, WU, Responses, and others

Device Category Windows Vista SP1 Driver Availability Windows 7 Inbox Windows 7 Inbox + WU + Response Windows Vista SP1 to Windows 7 Gap Audio99%88%96%98%1% Bus96%95% 96%0% Display99%67%98% 1% Network98%82%94% 4% Storage97%77%95%96%1%

DQR available on DQR available on OCA Crash Ratios WU install failure reports Microsoft managed DNF Response surveys Windows Vista Compatibility Center (WVCC)

Issues tracked for drivers that we see 100+ crashes per day on Windows Vista systems OCA Analysis Issues for drivers that have more than 2x the average crash ratio for the category are prioritized higher Crash Ratio Analysis Issues for drivers with a high market share within their category are prioritized at the highest level Market Share Analysis Category Average Crash Ratio Audio Bluetooth Input Networking Storage Streaming Media * Average Crash Ratio = (# times caused) / (# times seen) for all devices within a category RatingDescription 5 (best)<=.25x average 4<=.75x average 3<= 2x average 2<= 9x average 1 (worst)>9x average

CSAT = Average ( ) Yes + (Somewhat/2) Yes + No + Somewhat

SM Chips and Interfaces Reference Designs Driver Maintenance IHV SoftwareHardware IHV Hardware ODM Build and Sell Products CM Build Product PC OEMs RetailChannels CM Build Product SM = Semiconductor Manufacturer ODM = Original Development Manufacturer CM = Contract Manufacturer

Which driver? Which version? OEM specific? Update to an Inbox Driver? Is the driver PFD/SDV clean? How will the end user access/install the solution? Have all serviceability scenarios been addressed? What is the best possible driver? Managing obsolescence with the end user in mind Blocking drivers from migrating Not supported messaging What about legacy devices?

ScenarioDescription PC Purchase New PC purchased from the store Working peripheral devices from previous PC continue to work Device Purchase Device purchased from the store and installed on a working PC Software Upgrade Upgrade for driver, firmware, or application is discovered and installed on a working PC Service Update Updating OS components (Service Pack) that devices depend on Drivers supports uninstall/reinstall OS Upgrade Upgrade for OS is installed on a working PC Working drivers for peripherals are migrated Working drivers for internal devices are migrated Non working drivers are blocked from migration OS Clean Install OS is installed on a PC Drivers for peripherals and internal devices are available

StageDescription NewSmall install base with increasing adoption MainstreamHigh adoption within device category Maintenance Decreasing new sales or supported in prior OS LegacyDevice has not been sold for several years End of LifeRelatively low install base

New OS release Required inbox Optional inbox Inbox Important update Driver targeting Windows Server Update Services Windows Update OCA response DNF response Windows Vista Compatibility Center Response

Pre-Qualify for Inbox Contact Microsoft device team Pass WLK Logo, PFD, SDV, and INF tests Driver passes device team pre-qualification tests Legal and Policy NDA, IDDA, amendments MSCA, Grant ECA Onboard Partner SSD/AutoSecure setup Security group setup Bug DB setup Individuals Cardkey, RAS SSD enlist Build access (Connect) Extranet access Security group add Partner training Partner Build Submit to SSD Source uses MS structure Builds in MS Razzel environment Partner Verify Pass INF tests Pass signability Pass PFD tests Pass SDV tests Pass WLK Logo Pass Inbox Driver tests with Driver Verifier Submit to Microsoft Driver PDBs Logs Baseline PnP IDs Stakeholder list Microsoft Verifies Verify INF, signability, PFD, SDV, and WLK logs Build, test sign, and, and verify driver bits Device team verifies Inbox Driver tests with Driver Verifier External Stakeholders Provided driver to stakeholders Incorporate feedback Report Feedback Pass Fail Fail with bugs Grant exceptions Notify stakeholders Windows Update Codesign Post to WU Device team verifies driver downloads from WU and installs Windows 7 Inbox New Driver FCIB War approval Manifest changes Timebuild Device team verifies timebuild Driver check-in Monitor for build breaks Device team verifies driver installs with new build Device team verifies zero regressions on upgrade from prior OS SetupSubmissionVerification Distribution

Identify Gaps Identify Partner SM Reference driver Reference hardware Inbox driver IHV/ISV Driver modifications Inbox driver Driver distribution ODM/CM Hardware modifications OEM Driver modifications Inbox driver Driver distribution Identify Solution Best Driver Driver Version PFD/SDV clean Target system Target distribution Legacy Migration block Not supported response WER BIOS block Distribute Solution Inbox Required inbox Optional inbox Windows Update WinQual logo WinQual DDC Response OCA DNF homepage DNF direct download DNF not supported WVCC Driver Availability System view DNF Response view Market Share view Driver Quality OCA and crash ratio reports WU install failures DNF Response surveys WVCC ratings

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.