List of Available Hotfixes for Windows 7

NoN · 15 May 2014

-Article ID: 2950358 - Last Review: May 14, 2014 - Revision: 1.0
A memory leak in Network Store Interface Service (NSI) occurs unexpectedly.

Symptoms:
A memory leak in Network Store Interface Service (NSI) may cause unexpected problems on your computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1.

Applies to

Windows 7 Service Pack 1
Windows Server 2008 R2 Service Pack 1

Review and request hotfix:
A memory leak in Network Store Interface Service (NSI) occurs unexpectedly

------------------------------------------------------------------------------------------------------------

-Article ID: 2831013 - Last Review: May 14, 2014 - Revision: 5.0
User receives SMB change notifications from a subfolder that the user does not have permission to access in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Consider the following scenario:

You have a shared folder on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
A user (user A) maps a network drive to the shared folder. Therefore, user A can receive change notifications from the shared folder.
Another user (user B) changes a file in a subfolder or adds a file to a subfolder that user A does not have permission to access. The subfolder is in the shared folder.

In this scenario, user A receives Server Message Block (SMB) change notifications from the subfolder.

Notes

The expected behavior is that user A does not receive change notifications from the subfolder.
Change notifications are sent when any of the following activities occur:
- A user creates files or folders.
- A user changes existing files or folders.
- A user reads the documents that are temporarily written to the shared folder or automatically saved or locked in the shared folder.

Cause:
This issue occurs because the SMB protocol cannot modify change notification requests for each user.

Review and request hotfix:
User receives SMB change notifications from a subfolder that the user does not have permission to access in Windows 7 SP1 or Windows Server 2008 R2 SP1

------------------------------------------------------------------------------------------------------------

NoN · 15 May 2014

-Article ID: 2957775 - Last Review: May 14, 2014 - Revision: 2.0
System crashes during I/O traffic after you install a Host Bus Adapter on a computer that's running Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

You have a computer that's running Windows Server 2008 R2.
You install a Host Bus Adapter (HBA) that supports concurrent channels on the computer.
You start I/O traffic on the HBA.

In this scenario, the system crashes during I/O traffic.

Cause:
This problem occurs for miniports that opt into support for concurrent channels in Storport. In this situation, there's a race condition in which Storport tries to access memory that has already been freed, and this causes the system to crash.

Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
System crashes during I/O traffic after you install a Host Bus Adapter on a computer that's running Windows Server 2008 R2

NOTE: Might superseded the Update for Windows 7 for x64-based Systems (KB2908783) which was available through Windows Update last April 08, 2014.
INFO: Data corruption occurs on iSCSI LUNs in Windows

-------------------------------------------------------------------------------------------------------------

NoN · 20 May 2014

-Article ID: 2956703 - Last Review: May 15, 2014 - Revision: 1.0
You cannot renew the IP address after the system time synchronizes in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have computers in an environment to which the IP addresses are assigned by a Dynamic Host Configuration Protocol (DHCP) server.
You set a lease expiry time on the DHCP server.
You deploy Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 to one of the computers.
After the computer restarts, the system time of the computer is adjusted to an earlier time because of time synchronization.

In this scenario, the computer cannot request a new IP address from the DHCP server after the lease expires. Additionally, the computer reverts to using an Automatic Private IP Addressing (APIPA) (169.254.x .x) IP address.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2

Review and request hotfix:
You cannot renew the IP address after the system time synchronizes in Windows 7 or Windows Server 2008 R2

------------------------------------------------------------------------------------------------------------

-Article ID: 2953722 - Last Review: May 15, 2014 - Revision: 1.0
Drive Maps preferences are still displayed in Group Policy RSoP after they are removed or disabled.

Symptoms:
After a Drive Maps preference (Group Policy Preferences) is removed or disabled, and the client then applies those Group Policy Object (GPO) changes, the Drive Maps settings are still shown in Resultant Set of Policy (RSoP) reporting.

Cause:
This problem occurs because RSoP data is considered unchanged until there are new Drive Maps preferences to apply to the clients. Therefore, the previous preferences data is not discarded even if the particular Drive Maps setting was changed.

Resolution:

After you apply this update, follow these steps:

Go to the Group Policy Management Console (GPMC) window.
Open the Group Policy Object (GPO) in which your Drive Map setting is located.
Click User Configuration, click Policies, click Administrative Templates, and then click All Settings.
Select and then open Configure Purge RSOP behavior.
Select Enabled, and then set the value to 0x00000001.

Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
Drive Maps preferences are still displayed in Group Policy RSoP after they are removed or disabled

NoN · 10 Jun 2014

-Article ID: 2957560 - Last Review: June 3, 2014 - Revision: 6.0
Windows freezes during a stress test in iSCSI initiator.

Resolution:
This article describes an issue when you make a stress test in iSCSI initiator in Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

Details of the stress test:
This problem occurs when the stress test has the following conditions:

The stress test involves multiple iSCSI targets on external storage.
Each iSCSI target contains a Logical Unit Number (LUN).
A header and data digest are enabled for a cyclic redundancy check (CRC) function or for a checksum function on an iSCSI Initiator.
The test load writes to and reads from each volume.

Applies to

Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 R2 Standard
Windows 8 Enterprise
Windows 8 Pro
Windows 8
Windows Server 2012 Datacenter
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows Server 2012 Standard
Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard

Review and request hotfix:
Windows freezes during a stress test in iSCSI initiator

--------------------------------------------------------------------------------------------------------------

-Article ID: 2966897 - Last Review: June 10, 2014 - Revision: 1.0
Infinite loop occurs when the MSDSM inquires serial numbers of an MPIO device in Windows 7 SP1 and Windows Server 2008 R2 SP1.

Symptoms:
Assume that you configure a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 to use Microsoft Multipath I/O (MPIO) and the Microsoft Device Specific Module. When the MSDSM inquires serial numbers of an MPIO device, the system goes into an infinite loop. Additionally, the infinite loop may result in a Stop error.
Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2

Review and request hotfix:
Infinite loop occurs when the MSDSM inquires serial numbers of an MPIO device in Windows 7 SP1 and Windows Server 2008 R2 SP1

---------------------------------------------------------------------------------------------------------------

-Article ID: 2966921 - Last Review: June 10, 2014 - Revision: 1.0
No event ID 100 is logged in the Diagnostics-Performance log when you start Windows 7 SP1.

Symptoms:
Assume that you have a computer that is running Windows 7 Service Pack 1 (SP1). When you start the computer, no event ID 100 is logged in the Diagnostics-Performance log, even though you expect it to be.

This issue occurs even if the BootMinorThreshold parameter is set to be one second.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate

Review and request hotfix:
No event ID 100 is logged in the Diagnostics-Performance log when you start Windows 7 SP1

------------------------------------------------------------------------------------------------------------

-Article ID: 2951611 - Last Review: June 10, 2014 - Revision: 2.0
DirectAccess is used for internal network connections in Windows 7 SP1.

Symptoms:
A Windows 7 Service Pack 1 (SP1)-based computer uses DirectAccess to connect to the IPHTTPS address of the DirectAccess Server even though the computer is connected to the internal (domain) network.

Cause:
This issue occurs if the FQDN connection to the DA server(s) can be resolved in the internal network and a route exists to the IP address it resolves to. Or, if the DA client uses a proxy server that has a route to the DA server(s).

Only the IPHTTPS tunnel is connected. The IPSec tunnels are not created inside the IPHTTPS tunnel because the firewall detects a domain profile and the Connection Security rules do not apply to the domain profile. it is not a "full" DA connection that the Windows 7 client completed, but the IPHTTPS tunnel connection still occurs on port 443. As a result, performance issues may occur on the Direct Access Server.

Applies to

Windows 7 Service Pack 1

Review and request hotfix:
DirectAccess is used for internal network connections in Windows 7 SP1

NoN · 11 Jun 2014

Malicious Software Removal Tool (V5.13)

This tool checks your computer for infection by specific, prevalent malicious software (including Blaster, Sasser, and Mydoom) and helps to remove the infection if it is found. Microsoft will release an updated version of this tool on the second Tuesday of each month.

Download Malicious Software Removal Tool from Official Microsoft Download Center

-------------------------------------------------------------------------------------------------------------

-Article ID: 2964048 - Last Review: June 11, 2014 - Revision: 1.0
Can't open a local XML document that contains a multibyte character resource path link in Internet Explorer 9 or later.

Symptoms:

Consider the following scenario:

On a Windows 7 or Windows Server 2008 R2-based computer, you're running Internet Explorer 9 or a later version.
You try to open a local XML document that contains a multibyte character resource path link.

In this scenario, the contents of the resource path link are not displayed as expected in Internet Explorer.

Cause:
This problem occurs because Internet Explorer does not correctly parse multibyte characters.

Applies to

Windows 7 Enterprise
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
Can't open a local XML document that contains a multibyte character resource path link in Internet Explorer 9 or later

-----------------------------------------------------------------------------------------------------------

-Article ID: 2964643 - Last Review: June 11, 2014 - Revision: 1.0
Third-party VPN client stops Internet connectivity in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You have a third-party VPN solution deployed.
You connect your computer to the VPN server.

In this scenario, the network state for the VPN adapter is "No Internet Access." Additionally, some applications may not work properly.

For example, when you press F1 to open Help in Microsoft Office 2013 on the computer, you receive an error message that states the computer is not connected to the Internet, and the Help window is not displayed.

Cause:
This issue occurs because of a code error in the Network Connectivity Status Indicator (NCSI). In this situation, an incorrect connection status is reported. This issue also affects applications that read the network connection status through NCSI.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2

Review and request hotfix:
Third-party VPN client stops Internet connectivity in Windows 7 SP1 or Windows Server 2008 R2 SP1

NoN · 12 Jun 2014

-Article ID: 2965768 - Last Review: June 10, 2014 - Revision: 1.0
Stop error 0x3B when an application changes the z-order of a window in Windows 7 SP1 and Windows Server 2008 R2 SP1.

Symptoms:
When an application try to change the z-order of windows on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1, a Stop error 0x3B occurs in win32k.sys.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2

Review and request hotfix:
Stop error 0x3B when an application changes the z-order of a window in Windows 7 SP1 and Windows Server 2008 R2 SP1

------------------------------------------------------------------------------------------------------------

-Article ID: 2781571 - Last Review: June 11, 2014 - Revision: 3.0
"0x000000D1" Stop error after you install TDI drivers in Windows.

Symptoms:
Assume that you have a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista, or Windows Server 2008. After you install Transport Driver Interface (TDI) drivers, the computer crashes. Additionally, you receive a Stop error message that resembles the following:

Code:

Stop 0x000000D1 (Parameter1, Parameter2, Parameter3, Parameter4)

Notes

This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.
The parameters in this Stop error message vary, depending on the configuration of the computer.
Not all "Stop 0x000000D1" errors are caused by this issue.
The Afd.sys file is listed as the source of this error.

Cause:
This issue occurs because a TDI endpoint structure is created and populated when a WinSock application tries to bind a socket. However, a network interrupt occurs before the TDI endpoint structure is initialized. Therefore, the Afd.sys file tries to access to uninitiated data structure, and the computer crashes.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Ultimate

Review and request hotfix:
"0x000000D1" Stop error after you install TDI drivers in Windows

-----------------------------------------------------------------------------------------------------------

-Article ID: 2964511 - Last Review: June 11, 2014 - Revision: 2.0
Stop Error DRIVER_POWER_STATE_FAILURE occurs when you put your computer into standby or hibernation mode.

Symptoms:
After you put your computer into standby or hibernatation mode while you are connected to a virtual private network (VPN) over PPPoE or another tunnelling protocol, the NDIS Power Watchdog crashes and you receive the following Stop error message:

Code:

DRIVER_POWER_STATE_FAILURE

Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
Stop Error DRIVER_POWER_STATE_FAILURE occurs when you put your computer into standby or hibernation mode

-----------------------------------------------------------------------------------------------------------

-Article ID: 2962059 - Last Review: June 11, 2014 - Revision: 1.0
"RPC Server Unavailable" error when you set up a password and then click Next in Bitlocker To Go in Windows 8.1 or Windows 7.

Summary:
This article describes an issue when you plug in an external device to a client computer that is running Windows RT 8.1, Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

This issue is resolved by the following update rollup: 2962409
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014
Or, install the hotfix that is described in this article to resolve this issue.

Symptoms:

Consider the following scenario:

You have client computers that are running Windows RT 8.1, Windows 8.1, Windows Server 2012 R2, Windows 7, or Windows Server 2008 R2 in a domain.
You enable the Require password for removable data drive policy setting in the following Group Policy Object (GPO) path:
Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Removable Data Drive\Configure use of passwords for removable data drives
You plug in an external device to the client computer.

In this scenario, when you type the password and then client the next button in the BitLocker To Go wizard,you receive an error message that resembles the following:

Code:

RPC Server Unavailable

Applies to

Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
Windows RT 8.1
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 R2 Standard
Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard

Review and request hotfix:
"RPC Server Unavailable" error when you set up a password and then click Next in Bitlocker To Go in Windows 8.1 or Windows 7

NoN · 13 Jun 2014

-Article ID: 2964073 - Last Review: June 11, 2014 - Revision: 1.0
Stop error 7E or Stop error D1 occurs during read operations on a Usbser device.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You have an application or driver that issues read operations to the Usbser.sys driver and that specifies read time-outs.

Cause:
This problem occurs because of a race condition in the Usbser.sys driver.
Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
Stop error 7E or Stop error D1 occurs during read operations on a Usbser device

------------------------------------------------------------------------------------------------------------

-Article ID: 2965351 - Last Review: June 10, 2014 - Revision: 1.0
"Error_FILE_NOT_FOUND" when you print to a shared network printer.

Symptoms:
When you try to print a document on a shared network printer, the print operation is unsuccessful. In this situation, you receive the following error message:

Error_FILE_NOT_FOUND

Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
"Error_FILE_NOT_FOUND" when you print to a shared network printer

-----------------------------------------------------------------------------------------------------------

-Article ID: 2965904 - Last Review: June 13, 2014 - Revision: 2.0
Task name is deleted after you link a storage report to a scheduled task in Windows 7 SP1 and Windows Server 2008 R2 SP1.

Symptoms:

Considering the follow scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You create a scheduled task through command line interface (CLI) commands.
You generate a storage report.
You link the storage report to the scheduled task.

In this scenario, the name of the scheduled task becomes blank incorrectly. Additionally, the scheduled task does not run.

Cause:
This issue occurs because the storage report passes an incorrect task name when you link the report to the existing scheduled task.
Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Web Server 2008 R2

Review and request hotfix:
Task name is deleted after you link a storage report to a scheduled task in Windows 7 SP1 and Windows Server 2008 R2 SP1

NoN · 17 Jun 2014

-Article ID: 2964487 - Last Review: June 16, 2014 - Revision: 1.0
Some application windows and taskbar previews are blank or transparent on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
When you start an application in Windows 7 or Windows Server 2008 R2, a blank or transparent window and a blank or transparent taskbar preview are displayed. This problem most frequently occurs in a Microsoft Office 2013 application or a third-party product.

Applies to

Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Standard

Review and request hotfix:
Some application windows and taskbar previews are blank or transparent on a computer that is running Windows 7 or Windows Server 2008 R2

-----------------------------------------------------------------------------------------------------------

-Article ID: 2958997 - Last Review: June 17, 2014 - Revision: 1.0
EUDC fonts cannot be printed correctly by using an XPS print driver in Windows.

Symptoms:
Assume that you have a document that has several end-user-defined characters (EUDCs), and the document has more than one EUDC font. You print the document by using an XPS print driver on a computer that is running Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, or Windows Server 2008 R2. In this situation, only the EUDCs that are associated with the first EUDC font in the document are printed. Other EUDCs either disappear or are replaced by the EUDCs that are associated with the first EUDC font in the document.

Applies to

Windows 8.1 Enterprise
Windows 8.1
Windows 8.1 Pro
Windows RT 8.1
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 R2 Standard
Windows 8 Enterprise
Windows 8
Windows 8 Pro
Windows Server 2012 Datacenter
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows Server 2012 Standard
Windows 7 Enterprise
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Professional
Windows 7 Starter
Windows 7 Ultimate
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Foundation
Windows Server 2008 R2 Standard
Windows Server 2008 R2 for Itanium-Based Systems

Review and request hotfix:
EUDC fonts cannot be printed correctly by using an XPS print driver in Windows

NoN · 23 Jun 2014

-Article ID: 2965705 - Last Review: June 23, 2014 - Revision: 1.0
Display problems when a supplementary character follows a mathematical operator.

Symptoms:
When a supplementary character such as "∈" follows a mathematical operator in Windows 7 or Windows 7 Service Pack 1, characters that follow the supplementary character are not displayed correctly.

Cause:
This problem occurs because of a logic error that occurs when the font does not include the character glyph.
Applies to

Windows 7 Service Pack 1
Windows 7 Enterprise
Windows 7 Professional
Windows 7 Ultimate

Review and request hotfix:
Display problems when a supplementary character follows a mathematical operator

-----------------------------------------------------------------------------------------------------------

-Article ID: 2930287 - Last Review: June 23, 2014 - Revision: 4.0
WSD scan fails when you scan many pages in Windows.

Symptoms:
Assume that you create a Web Service on Device (WSD) scan environment that has Windows 8.1-based, Windows 8-based, or Windows 7-based computers and a WSD scanner. Then, you try to scan multiple pages of paper through the WSD scanner in one tray. In this situation, the scan fails.

Cause:
This issue occurs because WSD does not process the scanned data correctly in some cases.

Resolution:
-To resolve this issue for Windows 8.1 and Windows Server 2012 R2, install the hotfix that is described in this article.
-To resolve this issue for Windows 8 or Windows Server 2012, install update rollup 2928678, or install the hotfix that is described in this article.
-To resolve this issue for Windows 7 or Windows Server 2008 R2, install the hotfix that is described in this article.
Applies to

Windows 8.1 Enterprise
Windows 8.1
Windows 8.1 Pro
Windows RT 8.1
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Foundation
Windows 8 Enterprise
Windows 8 Pro
Windows 8
Windows RT
Windows Server 2012 Datacenter
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows Server 2012 Standard
Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard

Review and request hotfix:
WSD scan fails when you scan many pages in Windows

NoN · 09 Jul 2014

-Article ID: 2965917 - Last Review: July 8, 2014 - Revision: 1.0
A computer freezes during startup after filter drivers are installed in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You install some third-party filter drivers. For example:
- Symantec Endpoint Protection
- McAfee Data Loss Prevention Endpoint
- McAfee Endpoint Encryption for Files and Folders
- McAfee Agent

In this scenario, the computer will freeze when it next tries to startup.

Cause:
This issue occurs because there is a deadlock between Windows NT kernel and the fltmgr.sys file

Workaround:
To work around this issue, start the computer in safe mode, and then uninstall the filter drivers.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 for Itanium-Based Systems

Review and request hotfix:
A computer freezes during startup after filter drivers are installed in Windows 7 or Windows Server 2008 R2

-------------------------------------------------------------------------------------------------------------

-Article ID: 2961980 - Last Review: July 8, 2014 - Revision: 1.0
Conhost.exe process may crash when you run console applications in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms & Cause:
This issue occurs because a certain API fails when the amount of shared memory that's requested is greater than the initial shared memory. The Conhost.exe process does not then know the actual size of the shared memory.

Applies to

Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Ultimate
Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Foundation
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 for Itanium-Based Systems

Review and request hotfix:
Conhost.exe process may crash when you run console applications in Windows 7 SP1 or Windows Server 2008 R2 SP1

Note: This next Article ID: 2516889 might superseded Article ID: 2961980 in few files from April 12, 2014 to May 16, 2014.
Choose the one that suit the best your needs.

-Article ID: 2516889 - Last Review: July 8, 2014 - Revision: 2.0
The high-contrast mode accessibility option does not persist with a mandatory profile on a Windows 7-based or Windows Server 2008 R2-based computer.

Symptoms:
On a computer that is running Windows 7 or Windows Server 2008 R2, the high-contrast mode accessibility option does not work correctly when you run an application that uses the SPI_SETHIGHCONTRAST flag together with the SystemParametersInfo function.

Applies to

Windows 7 Enterprise
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Professional
Windows 7 Starter
Windows 7 Ultimate
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 for Itanium-Based Systems
Windows Server 2008 R2 Foundation
Windows Server 2008 R2 Standard
Windows Web Server 2008 R2

Review and request hotfix:
The high-contrast mode accessibility option does not persist with a mandatory profile on a Windows 7-based or Windows Server 2008 R2-based computer

------------------------------------------------------------------------------------------------------------

-Article ID: 2964833 - Last Review: July 9, 2014 - Revision: 3.0
Windows 8.1 or Windows 7 cannot connect over DirectAccess to a Remote Desktop Session Host server farm.

Symptoms:
Consider the following scenario:

You have a Remote Desktop Services (RDS) deployment.
The deployment contains an RD Connection Broker server and one or more RD Session Host servers or RD Virtualization Host servers.
The deployment is running Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2.
You expose the RDS Endpoint servers to users outside your corporate network by using DirectAccess.

In this scenario, clients can use Windows 8.1 or Windows 7 Remote Desktop Connection to connect to the RD Connection Broker server but cannot connect to their target endpoint in the RD Session Host server farm.

Cause:
This problem occurs because the client does not try all the endpoint addresses that are passed in the redirection packet of the RD Connection Broker server.

Review and request hotfix:
Windows 8.1 or Windows 7 cannot connect over DirectAccess to a Remote Desktop Session Host server farm