List of Available Hotfixes for Windows 7

NoN · 13 Nov 2014

-Article ID: 3004182 - Last Review: November 12, 2014 - Revision: 1.0
Memory leak when transiting web pages that contain the Windows Media Player ActiveX control in Windows 7 SP1.

Symptoms:
Assume that you have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. When you repeat a video that is played by the Windows Media Player ActiveX control on a web page in Internet Explorer, a memory leak occurs on the computer.
Applies to

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 Web Server 2008 R2
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

Note: Might superseded October 14, 2014 "patch Tuesday".

Review and request hotfix:
Memory leak when transiting web pages that contain the Windows Media Player ActiveX control in Windows 7 SP1

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

-Article ID: 3005781 - Last Review: November 13, 2014 - Revision: 1.0
Error occurs when you print an A3 size document in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a redirected printer that is created by using the Terminal Service Easy Print feature.
You use the redirected printer to print a document in an editor application (such as Microsoft Word).

In this scenario, you cannot print the document because of incorrect page margins, and you receive an error message.
Applies to

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

Note: Might superseded October 14, 2014 "patch Tuesday".

Review and request hotfix:
Error occurs when you print an A3 size document in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3001232 - Last Review: November 13, 2014 - Revision: 2.0
Print jobs fail in Windows 7 and Windows Server 2008 R2.

Symptoms:
When you try to print on a system that's running Windows 7 or Windows Server 2008 R2, the print job fails.

Cause:
This problem occurs when the DependentFiles registry key for the driver that's used by the printer is overwritten by a NULL string.

The DependentFiles registry key is located under the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\<architecture>\Drivers\Versio n-3\<driver_name>

Note The <driver_name> placeholder represents the name of the driver in question.

Applies to

Windows 7 Service Pack 1
Windows 7 Enterprise
Windows 7 Home Premium
Windows 7 Professional
Windows Server 2008 R2 Service Pack 1
Windows Server 2008 R2 Standard
Windows Server 2008 R2 Enterprise

Review and request hotfix:
Print jobs fail in Windows 7 and Windows Server 2008 R2

NoN · 14 Nov 2014

Don't be surprised that all those Hotfixes are popping up...its because most of the files are dated from early October 2014, before the official support end lifecycle October 31.

-Article ID: 3004543 - Last Review: November 12, 2014 - Revision: 1.0
Windows 7 or Windows Server 2008 R2 cannot renew IP address from a Windows Server 2012 R2-based DHCP server.

Symptoms:
Consider the following scenario:

You have at least two computers that work as DHCP servers in Windows Server 2012 R2.
You enable the DHCP failover feature and the Network Access Protection (NAP) feature on these DHCP servers.
You have a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based client computer that obtains IP address from one of the DHCP servers.
When an IP address lease expires on the client computer, the client computer sends a DHCP request to another DHCP server to extend the IP address lease.

In this scenario, the client computer cannot renew the IP address.

Applies to

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

Review and request hotfix:

Windows 7 or Windows Server 2008 R2 cannot renew IP address from a Windows Server 2012 R2-based DHCP server

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

-Article ID: 3007006 - Last Review: November 12, 2014 - Revision: 2.0
Memory usage of the Msdtc.exe process increases on Windows 7 or Windows Server 2008 R2.

Symptoms:
A memory leak occurs in the Microsoft Distributed Transaction Coordinator service on a computer that is running Windows 7 or Windows Server 2008 R2. You can verify this increase in memory usage in Performance Monitor by monitoring the private bytes of the Msdtc.exe process.
Applies to

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

Review and request hotfix:
Memory usage of the Msdtc.exe process increases on Windows 7 or Windows Server 2008 R2

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

-Article ID: 3007196 - Last Review: November 12, 2014 - Revision: 1.0
DSCP value is missing in the SYN-ACK packet during a TCP connection 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 create a policy to mark specific traffic with the differentiated services code point (DSCP) value on the computer.
You configure the DSCP marking on the computer.
You open a transmission control protocol (TCP) connection to the computer.

In this scenario, the SYN-ACK packet from the computer does not have the DSCP value set.
Applies to

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
- Windows Web Server 2008 R2
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:
DSCP value is missing in the SYN-ACK packet during a TCP connection in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3002286 - Last Review: November 14, 2014 - Revision: 2.0
Delay in accessing a file server when a Windows 7-based computer connects to the file server.

Symptoms:
Consider the following scenario:

You have a client computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You connect the client computer to a file server that is running Windows Server 2012 or Windows Server 2012 R2.
You connect the client computer to the file server again by using a different universal naming convention (UNC) path.

In this scenario, when other client computers try to access the same file server, they may encounter delay.
Cause:
This issue occurs because the Windows 7-based client computer uses the same client ID for the connections that use different UNC paths. Then, the file server cannot identify the appropriate connection to send an oplock break request.

Applies to

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
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:

Delay in accessing a file server when a Windows 7-based computer connects to the file server

NoN · 15 Nov 2014

-Article ID: 3007207 - Last Review: November 14, 2014 - Revision: 1.0
Stop 0x7F error occurs when there are multiple concurrent sessions on a Windows Server 2008 R2-based terminal server.

Symptoms:
Assume that you have a terminal server that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 in a terminal server farm. When there are multiple concurrent sessions on the terminal server, you receive a Stop 0x7F error message.

Applies to

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
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

Note: Might superseded the November 11, 2014 "Patch Tuesday": MS14-079

Review and request hotfix:
Stop 0x7F error occurs when there are multiple concurrent sessions on a Windows Server 2008 R2-based terminal server

NoN · 18 Nov 2014

Looks an optional update...from the download center. No article ID available at this time of the day (check later).

Update for Windows 7 for x64-based Systems (KB3006499)

Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

Version: 3006499
Date Published: 11/17/2014
File Name: Windows6.1-KB3006499-x64.msu
File Size: 9.4 MB

KB Article ID: 3006499

Direct Download from Microsoft Download Center:

x64

X32

NoN · 22 Nov 2014

-Article ID: 3002297 - Last Review: November 18, 2014 - Revision: 1.0
The SMB Redirector may hang when the SMB protocol is used in Windows 7 SP1 or Windows 8.1.

Symptoms:
When the Server Message Block (SMB) protocol is used in Windows 7 Service Pack 1 (SP1) or in Windows 8.1 to access files that reside on a remote system, the SMB Redirector may hang, and the system seems to stop responding.

Cause:
This problem occurs because of a deadlock condition in the SMB Redirector that occurs when the queue is full.

More Infos:
The SMB Redirector component implements the client part of the file-and-print sharing functionality exposed by Windows through Microsoft Networking. The implementation is based on the Server Message Block (SMB) protocol. The SMB protocol lets the client computer to access files on another computer that implements the SMB Service part of the file-and-print sharing functionality, and access to a shared printer.

Applies to

Windows 8.1
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 7 Service Pack 1, when used with:
- Windows 7 Enterprise
- Windows 7 Professional
- Windows 7 Ultimate

Review and request hotfix:
The SMB Redirector may hang when the SMB protocol is used in Windows 7 SP1 or Windows 8.1

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

-Article ID: 2984640 - Last Review: November 19, 2014 - Revision: 1.0
Stop Error 0x0000000A when you try to resume a Windows 7-based computer from sleep or hibernation.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7.
You put the computer into sleep or hibernation.
You try to resume the computer from sleep or hibernation.

In this scenario, the computer freezes. Additionally, you receive a Stop error that resembles the following:

Code:

Stop: 0x0000000A ( parameter1 , parameter2 , parameter3 , parameter4 ) 
IRQL_NOT_LESS_OR_EQUAL

Cause:
This problem occurs because of a race condition between human interface device (HID) multiple physical device object (PDO) start requests that are created by using the same functional device object (FDO).

Applies to

Windows 7 Enterprise
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Professional
Windows 7 Ultimate

Review and request hotfix:
Stop Error 0x0000000A when you try to resume a Windows 7-based computer from sleep or hibernation

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

-Article ID: 2815716 - Last Review: November 21, 2014 - Revision: 3.0
Splwow64.exe process doesn't end after a print job finishes in the 64-bit version of Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running the 64-bit version of Windows 7 or Windows Server 2008 R2.
You print something by using a 32-bit application.
The print job is finished.

In this scenario, the Splwow64.exe process does not immediately end.

Note The Splwow64.exe process is used to translate the driver model of a 64-bit operating system and a 32-bit program.

Cause:
This issue occurs because the Splwow64.exe process stays in the memory for additional time to increase system performance after a print job is finished. Therefore, the Splwow64.exe process does not end as expected when a print job is finished.

Resolution:
After you apply this hotfix, the hotfix sets the default time-out value for the Splwow64.exe process to remain in memory to two minutes. Therefore, the Splwow64.exe process shuts down two minutes after the last print job is finished. Additionally, you can configure this time-out value by changing the registry value in the "Registry Information" section.

Note: After applying this Hotfix you'll have to configure the time-out value in the registry. Backup your registry before any action.

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:
Splwow64.exe process doesn't end after a print job finishes in the 64-bit version of Windows 7 or Windows Server 2008 R2

NoN · 28 Nov 2014

-Article ID: 3010024 - Last Review: November 27, 2014 - Revision: 1.0
Default saved form settings are lost when connecting to shared printers on a Windows Server 2008 R2-based print server.

This article describes an issue that occurs when you connect to a shared printer on a Windows Server 2008 R2 Service Pack 1 (SP1)-based print server from a Windows 7 SP1-based computer.

Symptoms:
This issue occurs after you log off and then log back on to the Windows 7 SP1-based computer

Cause:
This issue occurs because of a problem involving the forms synchronization mechanism between clients and print servers.

Applies to

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
Windows 7 Service Pack 1, when used with:
- Windows 7 Ultimate
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter

Review and request hotfix:
Default saved form settings are lost when connecting to shared printers on a Windows Server 2008 R2-based print server

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

-Article ID: 2996928 - Last Review: November 27, 2014 - Revision: 2.0
Backup task fails with a time-out error in Windows.

This article describes an issue that occurs when you perform a backup task in Windows 8, Windows RT, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

Symptoms:
Assume that you run a third-party backup requester application to perform a backup task on the computer.

In this scenario, the backup task fails with an "Event ID: 34113" error, and you receive the following error message:

Code:

FAILED_AT_FREEZE (0x800423f2 - VSS_E_WRITERERROR_TIMEOUT)

Cause:
The issue occurs because the Volume Shadow Copy Service (VSS) encounters a deadlock during the Thaw event if the Security Account Manager (SAM) has pending writes for the registry.

Applies to

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

Review and request hotfix:
Backup task fails with a time-out error in Windows

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

-Article ID: 3004145 - Last Review: November 27, 2014 - Revision: 1.0
SSRS freezes when you access SSRS reports in Windows 7 or Windows Server 2008 R2.

This article describes an issue that occurs when you access Microsoft SQL Server Reporting Services (SSRS) reports in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

Cause:
A race condition occurs in Open Database Connectivity (ODBC), and it causes a deadlock in SSRS.

More Information:
The race condition that causes this issue occurs between the ODBC Finalizer thread and the SQLFreeHandle function.

Applies to

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

Review and request hotfix:
SSRS freezes when you access SSRS reports in Windows 7 or Windows Server 2008 R2

NoN · 10 Dec 2014

-Article ID: 2535094 - Last Review: December 9, 2014 - Revision: 8.0
Server stops responding when you lock or unlock files on a network by using the SMB2 protocol in Windows.

Symptoms:
A computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008 stops responding when it uses the Server Message Block Version 2 (SMB2) protocol to lock or unlock files on a network.

If you enable the special pool feature on the computer, you receive a Stop error message that resembles the following:

Code:

STOP: 0x000000D5 ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) 
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

Notes

The parameters in this Stop error message vary, depending on the configuration of the computer.
Not all "0x000000D5" Stop errors are caused by this issue.

Cause:
This issue occurs because of a race condition between the NTFS file system driver (Ntfs.sys) and the SMB2 server driver (Srv2.sys).

When the race condition occurs, a structure in NTFS file system driver is released prematurely. Therefore, the issue that is described in the "Symptoms" section occurs when the Ntfs.sys driver accesses the released structure.

Review and request hotfix:
Server stops responding when you lock or unlock files on a network by using the SMB2 protocol in Windows

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

-Article ID: 2965917 - Last Review: December 9, 2014 - Revision: 2.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.

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

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

-Article ID: 3014300 - Last Review: December 9, 2014 - Revision: 1.0
CredUIPromptForWindowsCredentials API does not select the smart card logon certificate from the pvInAuthBuffer parameter.

Symptoms:
Assume that you use a smart card in which multiple smart card logon certificates are stored. Programmatically, you want to preselect one of the stored smart card certificates in the credential information dialog box when you call the CredUIPromptForWindowsCredentials API. To do this, you populate the pvInAuthBuffer input parameter of the CredUIPromptForWindowsCredentials API with the credential of the certificate that you want to preselect. This issue is that the CredUIPromptForWindowsCredentials API does not preselect the certificate that is supplied in the pvInAuthBuffer parameter. Instead, the default certificate that is stored in the registry is preselected.

Cause:
If the credential that is supplied in the pvInAuthBuffer parameter does not match the first certificate that is stored in the smart card, the default certificate that is stored in the registry is used instead. The default certificate is located in the following registry subkey:

Code:

HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{8bf9a910-a8ff-457f-999f-a5ca10b4a885}\SessionData\1\Certificate

Note The default certificate is stored in the registry subkey after a previous successful smart card logon.

Review and request hotfix:
CredUIPromptForWindowsCredentials API does not select the smart card logon certificate from the pvInAuthBuffer parameter

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

-Article ID: 3012696 - Last Review: December 9, 2014 - Revision: 1.0
An IPP printer stops responding after you cancel a print job from PowerPoint in Windows 7 or Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You have Microsoft Office 2010 or one of its individual products, such as Microsoft Word or Microsoft PowerPoint, installed.
You have an Internet Printing Protocol (IPP) printer installed that is using a PCL 6 Unidrv-based printer driver.
You print a large file to the IPP printer, and then you cancel the print job within the Microsoft Office application.

In this scenario, you notice that the print job seems to cancel successfully. However, the print job status display in the print queue properties of the IPP printer indicates an error. Although the status changes from Spooling to Printing as expected, the display does not change again for a long time. After this delay, a status of Error is shown. You may also notice that the print device stops responding and is inaccessible for any printing until it times out and returns to Ready status.

Review and request hotfix:
An IPP printer stops responding after you cancel a print job from PowerPoint in Windows 7 or Windows Server 2008 R2

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

NoN · 10 Dec 2014

-Article ID: 2974005 - Last Review: December 9, 2014 - Revision: 1.0
Stop error 0x0000007E in Windows 7 or Windows Server 2008 R2.

Symptoms:
On a computer that's running Windows 7 or Windows Server 2008 R2, you may receive the following Stop error message:

Code:

0x0000007E ( parameter1 , parameter2 , parameter3 , parameter4 ) 
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Notes

The parameters in this error message vary, depending on the configuration of the computer.
Not all "0x0000007E" Stop error messages are caused by this problem.

Cause:
This problem occurs because the Kernel WMI GUID pointer is null. This causes a double-free vulnerability in the pointer.

Review and request hotfix:
Stop error 0x0000007E in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3006112 - Last Review: December 9, 2014 - Revision: 1.0
Surrogate pair characters in fallback font are displayed as squares in Windows 7 or Windows Server 2008 R2.

Symptoms:
This issue occurs when you enter some surrogate pair characters in fallback font by using a Japanese input method editor (IME). The font is in Unicode plane 15 or 16.

Review and request hotfix:
Surrogate pair characters in fallback font are displayed as squares in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3004075 - Last Review: December 9, 2014 - Revision: 2.0
Windows-based MSDSM doesn't handle sense code 02/04/03 (LUN Not Ready – Manual Intervention Required).

Symptoms:
Consider the following scenario:

You have the Windows Server 2012 R2, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1 Failover Clustering feature attached to an EMC VPLEX appliance in a stretched configuration.
This configuration is running native Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MSDSM) functionality.
The WAN link between EMC VPLEX sites fails.

In this scenario, cluster disks and Cluster Shared Volumes (CSV) disks fail.

Note This hotfix enables MSDSM to handle the sense code 02/04/03 (LUN Not Ready – Manual Intervention Required). After the hotfix is applied, MSDSM retries I/O through an alternative path to the LUN.

Review and request hotfix:
Windows-based MSDSM doesn't handle sense code 02/04/03 (LUN Not Ready

NoN · 11 Dec 2014

-Article ID: 2999802 - Last Review: December 9, 2014 - Revision: 5.0
Solid lines instead of dotted lines are printed in Windows.

Symptoms:

Consider the following scenario:

You add a PostScript printer to a computer that is running Windows 8.1, Windows 8, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 SP1.
You print a page that includes dotted lines.

In this scenario, solid lines instead of dotted lines are printed on the second and remaining pages.

Review and request hotfix:
Solid lines instead of dotted lines are printed in Windows

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

-Article ID: 3009621 - Last Review: December 9, 2014 - Revision: 1.0
VMware virtual machines freeze when they shut down or restart in Windows 7 or Windows Server 2008 R2.

This article describes an issue that occurs when Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based VMware virtual machines are shutting down or restarting.

Symptoms:
This issue occurs on VMware vSphere 5.0-based virtual machines that is running on an AMD processor-based computer.

Cause:
A deadlock occurs when virtual machines are shutting down or restarting.

Review and request hotfix:
VMware virtual machines freeze when they shut down or restart in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3015999 - Last Review: December 9, 2014 - Revision: 1.0
Stop Error 0x27 occurs when you try to move a folder on a network share from one place to another on Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You try to work with files on a network share from a computer that is running Windows 7 or Windows Server 2008 R2.
Service Pack 1 (SP1) is installed on the computer.
You try to move a folder on the network share from one place to another.

In this scenario, the computer crashes, and you receive a Stop error 0x27 in csc!CscSetFileInformation.

Review and request hotfix:
Stop Error 0x27 occurs when you try to move a folder on a network share from one place to another on Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3008558 - Last Review: December 9, 2014 - Revision: 1.0
Servers restart unexpectedly when the Lsass.exe process crashes in Windows Server 2008 R2 or Windows 7.

This article describes an issue that occurs when the Lsass.exe process crashes in Windows Server 2008 R2 Service Pack 1 (SP1) or Windows 7 SP1. A hotfix is available to resolve this issue.

Cause:
The RPC return value for a method inside the Lsass.exe process is expected to be in the range of 0 to 4. But instead, it receives the value 4001. This makes Directory Services unstable and unpredictable, and it may have serious consequences to the whole organization.

Review and request hotfix:
Servers restart unexpectedly when the Lsass.exe process crashes in Windows Server 2008 R2 or Windows 7

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

-Article ID: 3016350 - Last Review: December 9, 2014 - Revision: 1.0
Windows Photo Viewer cannot print single pages or custom page ranges on Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Assume that you install Windows Photo Viewer application on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. In this situation, the photo printing wizard has no options to print single pages or custom page ranges of a multipage image files, such as the Tagged Image File Format files (.tif and .tiff files).

Review and request hotfix:
Windows Photo Viewer cannot print single pages or custom page ranges on Windows 7 SP1 or Windows Server 2008 R2 SP1

NoN · 11 Dec 2014

-Article ID: 3016375 - Last Review: December 9, 2014 - Revision: 1.0
You get a restricted IP address after the wireless interface is re-enabled in Windows 7 or Windows Server 2008 R2.

Symptoms:
This issue occurs if the computer has joined an environment that has the Network Access Protection (NAP) feature enabled on the DHCP server. When this issue occurs, the DHCP server recognizes the client as non-NAP capable.

Cause:
This issue occurs because the DHCP client builds a DHCP Request message that does not have the statement of health (SoH) defined when the wireless interface is disabled and then re-enabled.

Workaround:
To work around this issue, restart the Network Access Protection Agent (NAPAgent) service on the client computer.

Review and request hotfix:
You get a restricted IP address after the wireless interface is re-enabled in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3014793 - Last Review: December 9, 2014 - Revision: 1.0
Stop error 0xC2, 0x50, or 0xCC after you restart a computer that's running Windows 7 or Windows Server 2008 R2.

Symptoms:
When you restart a computer that's running Windows 7 or Windows Server 2008 R2, this triggers Stop error 0xC2, 0x50, or 0xCC, and the computer crashes.

Cause:
This problem occurs because of synchronization issues in the Network Driver Interface Specification (NDIS) driver.

Review and request hotfix:
Stop error 0xC2, 0x50, or 0xCC after you restart a computer that's running Windows 7 or Windows Server 2008 R2

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

-Article ID: 3013102 - Last Review: December 9, 2014 - Revision: 1.0
"Command not found" error when you run a command in the C shell for SUA in Windows 7 or Windows Server 2008 R2.

Symptoms:
In Windows 7 or Windows Server 2008 R2, when you use the C shell to run any command for the Subsystem for UNIX-based Applications (SUA), you receive the following error message:

Command not found.

Review and request hotfix:
"Command not found" error when you run a command in the C shell for SUA in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3015692 - Last Review: December 11, 2014 - Revision: 2.0
Gdiplus.dll does not decode a multiframe image frame correctly in Windows 7 or Windows Server 2008 R2.

Symptoms:
When the Gdiplus.dll file is used in Windows 7 or Windows Server 2008 R2 to decode a multiframe image, the image frame is not decoded correctly. This problem occurs when one or more frames in the multiframe image are encoded in different formats.

Review and request hotfix:
Gdiplus.dll does not decode a multiframe image frame correctly in Windows 7 or Windows Server 2008 R2