Release Notes: Important Issues in Windows 7
Updated: May 4, 2009
Applies To: Windows 7
These release notes address critical late-breaking issues and information about the Windows® 7 operating system. For information about by-design changes, new features, and fixes in this release, see Miscellaneous Changes in Windows 7 (http://go.microsoft.com/fwlink/?LinkId=160338).
Unless otherwise specified, these notes apply to all editions of Windows 7 that support the features mentioned in each note.
The Window-Eyes screen reader application incorrectly reports the state of all option buttons in the First Run Wizard.
To work around this, set the focus on the option button and activate it with the SPACEBAR or the ENTER key—ignore the Window-Eyes report that the option button has not been activated.
Applications that run in a partial trust scenario (such as hosted ASP.NET sites) and use the Entity Framework to query a database will fail with a security exception.
There is no workaround at this time.
This issue affects Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows Server 2008 R2 for Itanium-Based Systems.
Any ASP.NET applications that connect to SQL Server Express user instances will fail and receive an error.
To correct this, first open Internet Information Services (IIS) Manager and select the Load User Profile check box for the affected application pool. If the issue persists, edit the application pool so that it uses the Network Services account.
Internet Explorer 8
Some Web sites may not display correctly, and may have misaligned text, missing images, or other rendering problems. To fix this, click the Compatibility View button on the address bar.
Network File System
This issue affects Windows Server 2008 R2 Enterprise and Windows Server 2008 R2 Datacenter.
If you use Network File System (NFS) version 2 or 3 in conjunction with the RPCSEC_GSS security mechanism and the rpc_gss_svc_integrity value (that is, with the –sec=krb5i option) you will be unable to mount shares over the User Datagram Protocol (UDP).
To use the –sec=krb5i option, configure the NFS client and server to use the TCP protocol. If you use the –sec=krb5 option, you can configure the client and server to use either TCP or UDP.
Routing and remote access
Not all non-Microsoft virtual private network (VPN) client applications are currently compatible with this release. For a list of compatible applications, see the VPN client compatibility information (http://go.microsoft.com/fwlink/?LinkId=148745).
If you use international characters for authentication credentials in a username for Password Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP), or Microsoft Challenge Handshake Authentication Protocol Version 2 (MS-CHAPv2), Network Policy Server (NPS) for Windows Server 2008 R2 is unable to authenticate the credentials. To avoid this issue, do not use international characters in a username for PAP, CHAP, or MS-CHAPv2. (Authentication works if you are using NPS for Windows Server 2008 R2). To correct this, see the Routing and Remote Access blog (http://go.microsoft.com/fwlink/?LinkId=150341).
Windows Search indexing
If you use a computer that has Windows Search enabled (Windows 7, Windows Vista, or Windows XP with Windows Search installed) and have chosen a custom index location that has a path name longer than 128 characters, the indexer will not start after you have upgraded the computer to this release. Search functionality and some library views are affected.
To avoid this, move the index to a different location that has a path name of less than 128 characters before you install this release as an upgrade.
If this has already occurred, use the Restore Defaults button on the Advanced Options pane of the Indexing Options control panel to reset the indexer.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Aero, Hyper-V, Internet Explorer, Windows, Windows Media, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.