List of Available Hotfixes for Windows 7

NoN · 13 Feb 2015

This one might superseded the "Article ID: 3019224 - Last Review: February 11, 2015 - Revision: 1.0" (Which Article ID: 3019282 looks more appropriate for the end-users) freshly posted.

-Article ID: 3019282 - Last Review: February 11, 2015 - Revision: 1.0
Print Spooler service crashes when you print documents on a network shared printer in Windows.

Symptoms:
This issue occurs if the network shared printer uses an IPv4 address.

Cause:
This issue occurs because a buffer underrun occurs when you connect to the network shared printer.
Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
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:
Print Spooler service crashes when you print documents on a network shared printer in Windows

NoN · 13 Feb 2015

-Article ID: 3012660 - Last Review: February 11, 2015 - Revision: 1.0
"The update is not applicable to your computer" error when you install update 2853587 in Windows 7 SP1 with AD LDS.

Symptoms
This issue only occurs if you first install AD LDS OOB on a computer that is running Windows 7 RTM and then install service pack 1 for Windows 7. In this situation, when you try to install update 2853587 the update cannot be applied, and you receive the error message.

Cause:
This issue occurs because update 2853587 is parented on the RTM version of the Microsoft-Windows-DirectoryServices-ADAM-Package-Client package that only presents when AD LDS OOB is installed. However, after SP1 is applied, the version of the package is increased. Therefore, update 2853587 cannot be applied.
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

Review and request hotfix:
"The update is not applicable to your computer" error when you install update 2853587 in Windows 7 SP1 with AD LDS

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

This one is more for "Server & Enterprise" editions, posted as informative purposes.

-Article ID: 3023569 - Last Review: February 10, 2015 - Revision: 1.0
Windows Process Activation Service crashes with an access violation in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
When this issue occurs, you cannot access the Internet Information Services (IIS) Web server. Additionally, event ID 1001 that resembles the following is logged in the Application log in Event Viewer:

Log Name: Application
Source: Windows Error Reporting
Date: Date and Time
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Computer
Description: Fault bucket, type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0 Problem signature:
P1: svchost.exe_WAS
P2: 6.1.7600.16385
P3: 4a5bc3c1
P4: iisw3adm.dll
P5: 7.5.7601.17514
P6: 4ce7c6b2
P7: c0000005
P8: 000000000001e48f
P9:
P10:

Cause:
This issue occurs because Windows Process Activation Service (WAS) does not clear a shutdown timer when WAS service is stopping. Then, a callback object is executed before the timer expires. Therefore, the access violation occurs.

Review and request hotfix:
Windows Process Activation Service crashes with an access violation in Windows 7 SP1 or Windows Server 2008 R2 SP1

NoN · 11 Mar 2015

Windows 7 is not Dead!

-Article ID: 3039024 - Last Review: March 9, 2015 - Revision: 3.0
Daylight saving time changes for Chile and Mexico in Windows.

Chile
Chile announced a DST change on January 28, 2015. For 2015 and going forward, Chile will remain in DST. (No DST change will be observed.) Therefore, the UTC offset for Chile will be updated to UTC-3:00, and the display name of the "Pacific SA Standard Time" time zone will be updated to "(UTC-3:00) Santiago."

Mexico
The Mexican state of Quintana Roo is moving from UTC-6:00 to UTC-5:00. The "Eastern Standard Time (Mexico)" will be created, and this new time zone will have a display name of "(UTC-5:00) Chetumal". This time zone will observe the following DST rules:

Start date: The first Sunday of April at 02:00 (clocks move forward by one hour)
End date: The last Sunday of October at 02:00 (clocks move backward by one hour)

Review and request hotfix:
Daylight saving time changes for Chile and Mexico in Windows

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

-Article ID: 3030039 - Last Review: March 10, 2015 - Revision: 1.0
"0xC000021B" error when you insert an NBL that contains multiple net buffers for IPv6 in Windows.

Symptoms:
This issue occurs when you use a Windows Filtering Platform (WFP) API that names FwpsInjectNetworkSendAsync0 to insert IPv6 packets.

Cause:
The issue occurs because the IPv6 header parser function fails when the input buffer size equals the size of the next header.
Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
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 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:
"0xC000021B" error when you insert an NBL that contains multiple net buffers for IPv6 in Windows

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

-Article ID: 3014783 - Last Review: March 10, 2015 - Revision: 1.0
"RDS busy" or "The Group Policy Client failed logon" error when you log on to an application in Windows Server 2008 R2.

Symptoms:
When you log on to a Windows 2008 R2-based server and access an application by using Remote Desktop Protocol (RDP), you receive one of the following error messages:

The task you are trying to do can't be completed because Remote Desktop Service is currently busy.
The Group Policy Client failed the logon.

Cause:
This problem occurs because of a synchronization issue in the user profile service (profsvc) between the work thread and the main service routine. When the user profile service stops, the service might still be busy trying to clean up the profiles.
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:
"RDS busy" or "The Group Policy Client failed logon" error when you log on to an application in Windows Server 2008 R2

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

-Article ID: 3036965 - Last Review: March 10, 2015 - Revision: 1.0
Printing preferences window appears behind a RemoteApp window in Windows.

This article describes an issue that occurs when you select a printing preferences option of a redirected printer in RemoteApp in Windows 7 Service Pack 1 (SP1) with Remote Desktop Connection (RDC) 8.1, Windows Server 2008 R2 SP1 with RDC 8.1, Windows 8.1, or Windows Server 2012 R2. A hotfix is available to resolve this issue.

Symptoms:
Assume that you use a redirected printer to print in a RemoteApp window, and you select the local printing preferences option. In this situation, the printing preferences window appears behind the RemoteApp window.
Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
Windows RT 8.1
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

Review and request hotfix:
Printing preferences window appears behind a RemoteApp window in Windows

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

-Article ID: 3031311 - Last Review: March 10, 2015 - Revision: 1.0
Duplicate SPNs cannot be detected in Windows 7 SP1 or Windows Server 2008 R2 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 run the Setspn command together with the -X switch on the computer in an Active Directory domain, the result does not return all existing duplicate Service Principal Names (SPNs).
Applies to

Windows Server 2008 R2 Service Pack 1, when used with:
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 Enterprise
- 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:
Duplicate SPNs cannot be detected in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3031085 - Last Review: March 11, 2015 - Revision: 1.0
"0x000000D5" Stop error on a ConfigMgr server that is running Windows Server 2008 R2 SP1.

Symptoms:
This issue occurs after you install a certain update on a System Center Configuration Manager (ConfigMgr) server that is running Windows Server 2008 R2 Service Pack 1 (SP1). The Stop error message resembles the following:
[CODE]STOP: 0x000000D5 (parameter1, parameter2, parameter3, parameter4)[CODE/]

Notes

This Stop error indicates a DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL issue.
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.

Additionally, the Stop error remains after you uninstall the update, and the system cannot manage the inventory and the hotfixes or the updates.
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:
"0x000000D5" Stop error on a ConfigMgr server that is running Windows Server 2008 R2 SP1

NoN · 12 Mar 2015

-Article ID: 3012644 - Last Review: March 10, 2015 - Revision: 1.0
Items disappear or are duplicated on All Programs menu after moving icons 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 clear the Sort All Programs menu by name check box in the Customize Start Menu dialog box of the Taskbar and Start Menu Properties.
You change the position of an item on the All Programs menu from the Start menu so that it is between two folders.
You log off and log on the computer.
You change the position of the same item on the All Programs menu from the Start menu.

In this scenario, a duplicate of the item that you moved appears and one of the folders is removed from the All Programs menu.
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:
Items disappear or are duplicated on All Programs menu after moving icons in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3036150 - Last Review: March 10, 2015 - Revision: 1.0
Remote desktop users can see the printers of the other users in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Assume that a user logs on to Windows Server 2008 R2 with remote desktop connection from a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1, and then opens Devices and Printers. In this situation, the user can see the printers of all the other users even though the permissions are set correctly for only the owner to access the printer.

Cause:
This issue occurs because the printer cache does not update details of the spool directory changes that are made to every printer. This makes the printers continuously to be shown to all logged-on users even though the users might not have the access to the printer.
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:
Remote desktop users can see the printers of the other users in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3036149 - Last Review: March 12, 2015 - Revision: 1.0
BITS might ignore the throttling policy and consume the WAN circuits in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
This issue occurs when Microsoft Background Intelligent Transfer Service (BITS) sets a maximum bandwidth in the Group Policy in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
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:
BITS might ignore the throttling policy and consume the WAN circuits in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3048015 - Last Review: March 12, 2015 - Revision: 1.1
Incorrect DST start settings for Morocco in 2015.

Symptoms:
Daylight saving time (DST) for Morocco in 2015 starts at 02:00 on March 29. However, some customers may experience an incorrect DST start setting of 02:00 on August 2 instead.

Note: Use either manual fix or the provided Fix-It solution in the article.

Review and request hotfix:
Incorrect DST start settings for Morocco in 2015

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

-Article ID: 3037941 - Last Review: March 10, 2015 - Revision: 1.0
Files are replaced even though they are not changed when you run Robocopy command in Windows 7 or Windows Server 2008 R2.

Symptoms:
This issue occurs after you install Hotfix 2639043 When you run the Robocopy /mir command to replicate directories and folders, the Date modified value of the files are different between source location and destination location in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

Note This issue may cause more unnecessary copy events or network bandwidth in your environment.
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:
Files are replaced even though they are not changed when you run Robocopy command in Windows 7 or Windows Server 2008 R2

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

-Article ID: 981538 - Last Review: March 11, 2015 - Revision: 1.0
You receive broken messages in the Ftp command output logs on a computer that is running Windows.

Symptoms:
On a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista, or Windows Server 2008, the Ftp.exe utility creates broken messages in the output logs. When this issue occurs, applications that monitor the Ftp output messages may not work correctly.

This issue occurs under certain conditions. For example, this issue may occur when you apply some Ftp commands to a target location that does not exist. This issue may also occur if the language locale is not set correctly in the Ftp.exe utility.

For example, on a computer whose language locale is English, you use the lcd Ftp command to change the working directory to the C:\aaaaa directory:
ftp> lcd C:\aaaaa
If the C:\aaaaa directory does not exist, the expected output message is as follows:

Code:

\aaaaa: File not found

However, you receive an output message that resembles the following:

Code:

\aaaaa: F

Note The appearance of the broken message may vary, depending on the language locale in your computer.
Applies to

Windows Vista Service Pack 2
Windows Vista Service Pack 1
Windows Vista Business
Windows Vista Business 64-bit Edition
Windows Vista Enterprise
Windows Vista Enterprise 64-bit Edition
Windows Vista Home Basic
Windows Vista Home Basic 64-bit Edition
Windows Vista Home Premium
Windows Vista Home Premium 64-bit Edition
Windows Vista Ultimate
Windows Vista Ultimate 64-bit Edition
Windows Server 2008 Service Pack 2
Windows HPC Server 2008
Windows Server 2008 Foundation
Windows Server 2008 Datacenter
Windows Server 2008 R2 Datacenter without Hyper-V
Windows Server 2008 Enterprise
Windows Server 2008 R2 Enterprise without Hyper-V
Windows Server 2008 Standard
Windows Server 2008 R2 Standard without Hyper-V
Windows Web Server 2008
Windows Server 2008 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
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

Review and request hotfix:
You receive broken messages in the Ftp command output logs on a computer that is running Windows

NoN · 09 Apr 2015

Not much lately....

-Article ID: 3048015 - Last Review: March 12, 2015 - Revision: 1.1
Incorrect DST start settings for Morocco in 2015.

Symptoms:
Daylight saving time (DST) for Morocco in 2015 starts at 02:00 on March 29. However, some customers may experience an incorrect DST start setting of 02:00 on August 2 instead.

More Infos: https://support.microsoft.com/fr-fr/kb/3048015/en-us

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

-Article ID: 3049874 - Last Review: March 26, 2015 - Revision: 3.0
Daylight saving time changes for Mexico, Mongolia, and Iran in Windows.

Introduction:
This article describes a hotfix that updates daylight saving time (DST) settings for Mexico, Mongolia, and Iran. This update supersedes KB 3039024.

More Infos: https://support.microsoft.com/fr-fr/kb/3049874/en-us

NoN · 10 Apr 2015

-Article ID: 3036155 - Last Review: April 10, 2015 - Revision: 2.0
Scanning application crashes upon close after you perform a scan in Windows.

This article describes an issue that occurs when you try to close a scanning application in Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

Cause:
This issue occurs because, when the scanning application performs a scan, the callbacks that were registered are not released until the scanning application itself closes.

Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
Windows RT 8.1
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

Review and request hotfix:
https://support.microsoft.com/fr-fr/kb/3036155/en-us

NoN · 15 Apr 2015

-Article ID: 3042842 - Last Review: April 14, 2015 - Revision: 1.0
Files cannot be copied when drive redirection is enabled in Windows 7 or Windows Server 2008 R2-based RDP 8.1 client.

Symptoms:
Assume that you have Remote Desktop Protocol (RDP) 8.1 applied on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. You have a file that is ranging in sizes from 1,535 bytes to 1,540 bytes. In this situation, when you try to copy the file to the RDP 8.1 client, file copy freezes at 0% forever.
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

Review and request hotfix:
https://support.microsoft.com/fr-fr/kb/3042842/en-us

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

-Article ID: 3045882 - Last Review: April 14, 2015 - Revision: 1.0
Private key is not exported when you export a certificate in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Assume that a certificate is configured to use strong private key protection and to prompt users for a password when the private key is accessed. In this configuration, when users export the certificate that includes the private key, the export is completed. However, the private key is not exported.
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:
https://support.microsoft.com/fr-fr/kb/3045882/en-us

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

-Article ID: 3040017 - Last Review: April 14, 2015 - Revision: 1.0
XPS driver is slower than GDI driver to print files in Windows.

Summary:
This article describes an issue that occurs when XPS drivers print files together with lots of vector drawings in Windows RT 8.1, Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
Windows RT 8.1
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:
https://support.microsoft.com/fr-fr/kb/3040017/en-us

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

-Article ID: 3027578 - Last Review: April 15, 2015 - Revision: 2.0
I/O failure during MPIO path failover in Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You configure a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1) to use Microsoft Multipath I/O (MPIO).
You connect a storage device that is configured to use Asymmetric Logical Unit Access (ALUA) to the computer.
A failover occurs on the MPIO paths.

In this scenario, the operating system becomes unresponsive, and I/O failure occurs.
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:
https://support.microsoft.com/fr-fr/kb/3027578/en-us

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

-Article ID: 3030736 - Last Review: April 15, 2015 - Revision: 2.0
"550 The process cannot access the file" error when you try to download a file in Windows.

This article describes an issue that occurs in the FTP service on a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

Symptoms:
This issue occurs when you try to download a file while the file is still being written to, even if the application that is writing to the file has opened the file by specifying the FILE_SHARE_READ value for the sharing mode. When this issue occurs, you cannot download the file, and the FTP service returns an error message that resembles the following:

Code:

550 The process cannot access the file because it is being used by another process.

Applies to

Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
Windows 8.1
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:
https://support.microsoft.com/fr-fr/kb/3030736/en-us

NoN · 16 Apr 2015

-Article ID: 2780102 - Last Review: April 16, 2015 - Revision: 2.0
"0x0000003B" Stop error when a Remote Desktop Connection Broker and a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer are in an RDS farm.

Symptoms:
Assume that you have a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows 7 SP1 in a Remote Desktop Services (RDS) farm. When a Remote Desktop Connection Broker is also in the RDS farm, the computer crashes. Additionally, you receive a Stop error message that resembles the following:

Code:

STOP 0x0000003B (Parameter1 , Parameter2 , Parameter3 , Parameter4)

Notes

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

Cause:
This issue is caused by a race condition that occurs in the dynamic virtual channels. Therefore, the rdpdr! CTransportVC::CloseChannels function in the Rdpdr.sys file crashes.
Applies to

Windows 7 Service Pack 1
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
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:
https://support.microsoft.com/fr-fr/kb/2780102/en-us

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

-Article ID: 3035446 - Last Review: April 15, 2015 - Revision: 1.0
Offline files stop syncing after the location of home folder is changed in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

The Folder Redirection feature is enabled for a user to redirect his or her documents to a home folder in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
The home folder is supported by offline files.
You have the Music, Pictures, and Videos folders of the user follow the Documents folder.
You change the destination location of the home folder for the redirected documents to a new location.

In this scenario, the Folder Redirection feature does not update the location of the folder, and offline files do not recognize the new home folder.

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:
https://support.microsoft.com/fr-fr/kb/3035446/en-us

NoN · 18 Apr 2015

-Article ID: 3044428 - Last Review: April 18, 2015 - Revision: 1.0
"0x00000027" or "0x00000050" Stop error in the Rdbss.sys driver in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
The Stop error resembles one of the followings:

Code:

STOP: 0x00000027 (parameter1, parameter2, parameter3, parameter4)

Code:

STOP: 0x00000050 (parameter1, parameter2, parameter3, parameter4)

Notes

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

Cause:
This issue occurs because there is a race condition in the Redirected Drive Buffering Subsystem (Rdbss.sys) driver.
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:
https://support.microsoft.com/fr-fr/kb/3044428/en-us

NoN · 25 Apr 2015

This is rather a Fix-It solution than a hotfix provided by Microsoft using a .vbs script. Could be useful for those that have istalled from DVD/ISO media Windows 7 SP1.

I remember seeing those errors in the events viewer, not caring too much has it said "Events cannot be delivered through this filter until the problem is corrected" (thought there was no hurry).

It has fixed three errors in event IDs on my actual machine and i have used the Workaround.vbs script instead of the ready Fix-It solution, which the first have displayed the errors fixed.

-Article ID: 2545227 - Last Review: April 23, 2015 - Revision: 2.1
Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2.

Symptoms:
After you install Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1) using integrated media, you may see the following WMI error is logged in the application log after every reboot:

Log Name - Application

Source - WMI

EventID - 10

Level - Error

User - N/A

OpCode - Info

Task Cat - None

Keywords - Classic

Details - Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Cause:
This originated in the Windows 7 SP1 DVD/ISO creation process. There was an issue in the creation process that caused a WMI registration to remain in the DVD/ISO. Since the registration is designed to work only during the DVD/ISO creation process, it fails to run on a live system and causes these events. These events are not indicative of any issue in the system and can be safely ignored. If however you want to prevent these events from getting generated and want to remove this specific WMI registration manually, please follow the steps mentioned in this article for running the workaround script.

More Information:
This particular Event ID 10 error message listed above can be safely ignored, this is not indicative of a problem with the Service Pack or with the operating system.

Review the Fix-It solution or manual Workaround:
https://support.microsoft.com/fr-fr/kb/2545227/en-us