I received this month's Microsoft Hardware newsletter and thought it might help some of you out there, so I am pasting it below in full.
Notice about Drivers and Windows Vista SP1
As the broad availability of Windows Vista Service Pack 1 (SP1) approaches, it is important to review how to build quality device drivers that are deployable based on device installation requirements and best practices for Windows Vista (see Device Installation Rules for Windows Vista and Building Deployable Device Driver Packages). Windows Vista SP1 includes substantial improvements to the core operating system, components, driver stacks, and some inbox drivers. These improvements increase stability, robustness, and performance, enhance security, and include key changes to inbox drivers. As you are probably aware, our testing has revealed a few instances in which driver reinstallations result in unforeseen side-effects for some devices. In those instances, a manual reinstallation of the driver may be required after a Windows Vista SP1 installation. Because we do not want users to have a negative device experience, Because we do not want users to have a negative device experience, Windows Update will recognize PCs with problematic drivers and postpone offering SP1 to those PCs while we work with our partner ecosystem to mitigate these problems. For more detailed information, please review the following technical guidance and next steps. Based on the device installation requirements and best practices for Windows Vista, the Windows Vista SP1 update servicing process conducts an INF-based reinstallation of drivers that have dependencies on updated Windows Vista SP1 inbox drivers. This reinstallation helps to ensure a higher success rate for Windows Vista SP1 installation. Any software that is installed without using an INF-such as a Setup application or Windows Installer-remains unchanged, but the device itself is reinstalled by using an INF. The result is similar to using Device Manager to reinstall the device driver. If our testing identified problems during development, we contacted the appropriate partners to investigate the problems and provide fixes. Although we understand that as valued partners you have engaged in testing and have addressed driver problems that you discovered throughout the Windows Vista SP1 development cycle, we request your help now to mitigate any potential impact to end users who upgrade to Windows Vista SP1 by doing the following: Compare the behavior of your device before and after a Windows Vista SP1 update by doing the following:1. Perform a clean installation of the released version of Windows Vista.2. Install all Windows Vista critical and important updates from Windows Update.3. Confirm your device and driver functionality before the Windows Vista SP1 update, including making changes to the default device configuration.4.
To configure your PC to download Windows Vista SP1 over Windows Update, run the following commands at an elevated command prompt:. reg
deleteHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSp1 /f
> NUL 2>&1. reg deleteHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSP1 /f > NUL 2>&1. reg addHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSp1 /v Beta1 /t REG_SZ /d dcf99ef8-d784-414e-b411-81a910d2761d /f5.
Install Windows Vista SP1 from Windows Update.6. Confirm that your device and driver functionality and configuration have not changed after the Windows Vista SP1 update. Review your completed Windows Vista SP1 update installation test efforts and results by:. Assessing your test results for any driver-specific update problems that require our attention.. Focusing on any problems that could result in the potential for a negative device experience after installing Windows Vista SP1. For example, look for changes in device behavior or configuration. Take the following steps for any devices or drivers that exhibit problems after a Windows Vista SP1 update:. Focus on drivers that could be problematic in servicing as a result of an installation that is based on an INF.. Be aware that drivers that require an end-user action or co-installation application may have specific problems with Windows Vista SP1. Ensure that your driver complies with all recommended guidance for Windows Vista driver development described on the WHDC Driver Installation page. Help remedy device or driver problems by doing the following:. If you identify a problem, contact your IHV/OEM technical account manager. They will assist you to resolve the problem through an updated driver and temporarily suspended automatic update.. If you do not have an IHV/OEM technical account manager, see Microsoft Help and Support to submit a request for support. All requests that result in a bug will be fully refunded. We thank you for your hard work on Windows Vista SP1 and value your continued partnership with Microsoft.
Edition forMarch 11, 2008
In This Issue:
From the Editor
Notice about Drivers and Windows Vista SP1
Tools and Links for Developers
Windows Driver Developer Kits, Tools, and Programs
•
Debugging Tools v.6.8.4.0 (October 2007)
•
Windows Driver Kit and Windows Logo Kit
•
WDK Documentation (monthly updates)
•
Windows Symbols (January 2008)
•
Logo Point (Windows Logo Program requirements and news)
•
WDK Documentation in 7 Languages: Try the Beta
Developing Drivers with Windows Driver Foundation
Buy the Book
WDF Resources on WHDC Web
Hardware and Driver Developer Community
•
XML Paper Specification (XPS) Developers Forum
•
Blogs, Newsgroups, and Video on WHDC
•
Notes from Windows Development Teams
The Microsoft Hardware Newsletter provides manufacturers and developers the latest technical details for how to succeed with the Windows platform. Register now, if you're not already receiving the Microsoft Hardware Newsletter. To cancel your subscription to this newsletter, reply to this message with the word UNSUBSCRIBE in the Subject line. You can also unsubscribe at the Microsoft.com Web site. You can manage all your Microsoft.com communication preferences at this site.Legal Information.This newsletter was sent by the Microsoft Corporation1 Microsoft WayRedmond, Washington, USA98052
No comments:
Post a Comment