List of Available Hotfixes for Windows 7

-Article ID: 2995054 - Last Review: October 14, 2014 - Revision: 1.0
"400 Bad Request" error when you send a message that contains a lowercase "get" to the Gateway.

Symptoms:
You have an SMS Gateway web server deployed in an environment where you're also running a Windows Server 2003-based server. However, when you use an HTTP webpage to send a message that contains a lowercase "get" to the Gateway, you receive the following error message:

Code:

400 Bad Request (Invalid Header Name)

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 Foundation
• Windows Server 2008 R2 Standard

Review and request hotfix:
"400 Bad Request" error when you send a message that contains a lowercase "get" to the Gateway

-Article ID: 2996534 - Last Review: October 14, 2014 - Revision: 1.0
Rotated images in PowerPoint 2013 are printed incorrectly when you use XPS in Windows.

Symptoms:

Considering the following scenario:

• You have a PowerPoint slide that contains rotated images on a computer that is running Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 8, Windows RT, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
• You open the PowerPoint slide in Microsoft PowerPoint 2013, and then you try to print the file by using Microsoft XPS Document Writer or an XPS printer.

In this scenario, the PowerPoint slide may be printed incorrectly.

Review and request hotfix:
Rotated images in PowerPoint 2013 are printed incorrectly when you use XPS in Windows

Note: See also Post #238
-Article ID: 2979583 - Last Review: September 11, 2014 - Revision: 1.0
Additional thick line is printed on a page that has an Excel chart in Windows 7 or Windows Server 2008 R2.

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

-Article ID: 3000406 - Last Review: October 14, 2014 - Revision: 1.0
Windows Journal crashes when you import a Word document that contains pictures Windows 7 or Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

• You have update 2971850 installed on a computer that is running Windows 7 or Windows Server 2008 R2.
• You try to import a Microsoft Word document that contains pictures to Windows Journal on the computer.
• In this scenario, Windows Journal crashes.

Applies to

• Windows Server 2008 R2 Datacenter
• Windows Server 2008 R2 Enterprise
• Windows Server 2008 R2 Standard
• Windows Server 2008 R2 Foundation
• 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 Journal crashes when you import a Word document that contains pictures Windows 7 or Windows Server 2008 R2

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

-Article ID: 2908580 - Last Review: October 15, 2014 - Revision: 2.0
"0x0000000A" Stop error on a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer that has Norton Internet Security or Norton 360 installed.

Symptoms:
Assume that you have a Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1-based computer that has multi-core processors. The computer has Norton Internet Security or Norton 360 installed. In this situation, the computer may crash. Additionally, you receive a Stop error message that resembles the following:

Code:

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

Cause:
This issue occurs because two identical UDP packets are sent at the same time from two threads. Therefore, a crash occurs in the Netio.sys file.

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:
"0x0000000A" Stop error on a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer that has Norton Internet Security or Norton 360 installed

Note: Superseded see post #188
-Article ID: 2908580 - Last Review: January 15, 2014 - Revision: 1.0
"0x0000000A" Stop error on a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer that has Norton Internet Security or Norton 360 installed.

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

-Article ID: 2998097 - Last Review: October 16, 2014 - Revision: 1.0
"Specified account does not exist" error message when domain users try to change their password in UPN format in a different domain.

Symptoms:

Consider the following scenario:

• There are multiple domains that do not have trust relationships between the domains.
• Domain clients within each domain are running Windows 7 Service Pack 1.
• The DNS that each domain points to can resolve the other.
• A user on a Domain 1 computer tries to change a Domain 2 user's password by using the UPN credential format, UserName@DNSDomainName.com.

In this scenario, the user password is not changed and the user receives the following error message:

The specified account does not exist.

Cause:
This problem occurs because of changes that were made in hotfix 978277

Applies to

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

Review and request hotfix:
"Specified account does not exist" error message when domain users try to change their password in UPN format in a different domain

Note: Might superseded security update from October 14, 2014 "patch Tuesday" by changing few .dll (Credssp.dll; Tspkg.dll...). Patch intended to Domain User only.

-Article ID: 2996911 - Last Review: October 16, 2014 - Revision: 1.0
DFSR stops replication after a dirty shutdown in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

• On a domain server in a Windows 7 or Windows Server 2008 R2 environment, you have a Distributed File System Replication (DFSR) service folder.
• Many replication activities appear in the folder.
• The domain server performs a dirty (unexpected) shutdown.
• NTFS journal wrap occurs after the dirty shutdown.

In this scenario, the DFSR replication of folders stops working after the DFSR garbage collection task is performed.

Cause:
When there is a dirty shutdown, DFSR updates records by restamping and marking records as GC VersionVectorTombstone. Journal wrap also marks the record as not present. The garbage collection task goes into effect, and the database GUID is added as tombstoned GUID. DFSR then marks the database GUID as stale. When a new file is created, it is stamped with the stale database GUID. This causes the record to be filtered out from the version vector because it is a stale database. Therefore, replication does not occur.

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 Foundation
• Windows Server 2008 R2 Standard

Review and request hotfix:
DFSR stops replication after a dirty shutdown in Windows 7 or Windows Server 2008 R2

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

-Article ID: 2998965 - Last Review: October 16, 2014 - Revision: 1.0
You cannot resize divided windows inside a RemoteApp in Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you run a RemoteApp on a Remote Desktop Services (RDS) client computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. The RemoteApp has multiple areas of functionality. In this situation, you cannot click or drag the vertical divider to resize divided windows inside the RemoteApp.

Applies to

• 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:
You cannot resize divided windows inside a RemoteApp in Windows 7 or Windows Server 2008 R2

Note: Might superseded security update from October 14, 2014 "patch Tuesday" with the Mstscax.dll updated:
-Article ID: 2994023 - Last Review: October 14, 2014 - Revision: 2.0
RPD 8.1 client for Windows 7 or Windows Server 2008 R2 disconnects when it is connected through a RD gateway. Article ID: 2994023

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

-Article ID: 2997200 - Last Review: October 16, 2014 - Revision: 1.0
Contiguous memory allocation fails with a "STATUS_NO_MEMORY" error in Windows 7 or Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

• You have a computer that's running Windows 7 or Windows Server 2008 R2.
• You use third-party software to allocate contiguous memory by using the MmAllocateContiguousMemory or MmAllocateContiguousMemorySpecifyCache APIs.

In this scenario, your allocation attempt fails, and a "STATUS_NO_MEMORY" error is generated when the computer is started.

Cause:
This problem occurs because of a problem in the memory allocation algorithm inside the Windows NT kernel. This causes fragmentation in the physical memory, and therefore the contiguous memory allocation process may fail.

Applies to

• Windows Server 2008 R2 Datacenter
• Windows Server 2008 R2 Standard
• Windows 7 Professional

Review and request hotfix:
Contiguous memory allocation fails with a "STATUS_NO_MEMORY" error in Windows 7 or Windows Server 2008 R2

Note: Might superseded security update from October 14, 2014 "patch Tuesday" on few files:
-Article ID: 2949927 - Last Review: October 16, 2014 - Revision: 2.0
Microsoft Security Advisory: Availability of SHA-2 hashing algorithm for Windows 7 and Windows Server 2008 R2: October 14, 2014.
Article ID: 2949927

-Article ID: 2996207 - Last Review: October 14, 2014 - Revision: 1.0
Network printers that use TCP/IP port cannot print after first document has printed in Windows.

Symptoms:
Assume that you use a network printer through a TCP/IP port to print documents on a client computer that is running Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. In this scenario, when the first print job is finished, any other print jobs cannot be printed.

Cause:
The issue occurs because the client computer does not send a FIN packet to the print server after the first print job is finished. Therefore the print server cannot recognize whether the print job has finished. In this scenario, the print server waits for several minutes, sends a RST packet to the client server, and then cancels the printer job.
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 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 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

Review and request hotfix:
Network printers that use TCP/IP port cannot print after first document has printed in Windows

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

-Article ID: 2957486 - Last Review: October 17, 2014 - Revision: 3.0
Ls command takes a long time to list shared files in two windows on a Windows-based NFS server.

Symptoms:
Consider the following scenario:

• You have a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1).
• The computer works as a Network File System (NFS) server.
• You create and share files on the NFS server.
• You use a mount command on a NFS client to connect to the NFS server.
• You open more than one terminal window on the NFS client.
• You run the following ls command in each terminal window at the same time to list all shared files:
  cd <NFS share>
  ls –lR

In this scenario, it takes longer than expected to list all the shared files from the NFS server.

Cause:
This issue occurs when the NFS client sends a GETATTR call two times in a row. The NFS server has to wait for the ACK packet from the NFS client for the first GETATTR reply packet before it can send the queued second GETATTR reply packet.

Note In most cases, it takes about 0.04 sec to send the second GETATTR reply packet because of delayed ACKs from the NFS client. Therefore, when you execute an ls command, it takes more than two hours to list all files for the attribute information when the total number of files is more than 400,000.
(400,000 * 0.04 sec / 2 Nfs3GetAttr() calls / 3600 sec = 2.22 hours)

You can confirm how long it takes to send the GETATRR reply to the NFS client by monitoring network packets.

Resolution:
To resolve this issue, install hotfix 2957486 on the NFS server.

Note Even though this issue has only been observed in Windows Server 2008 R2, the hotfix also applies to Windows 7.
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 Standard
• 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:
Ls command takes a long time to list shared files in two windows on a Windows-based NFS server

-Article ID: 2997842 - Last Review: October 22, 2014 - Revision: 1.0
Transmission throughput is less when you use a Wi-Fi adapter to transfer files in Windows 7 or Windows Server 2008 R2.

Symptoms:
This issue occurs on a multiprocessor computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

When you try to transfer files through a wireless network connection, the file transmission throughput is less than expected.

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:
Transmission throughput is less when you use a Wi-Fi adapter to transfer files in Windows 7 or Windows Server 2008 R2

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

-Article ID: 2974617 - Last Review: October 22, 2014 - Revision: 1.0
Network connectivity is lost when many users run applications on a remote server 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.
• The computer works as a server where more than 50 users run applications by using Remote Desktop Protocol (RDP) at the same time.
• The server is running under unusual heavy processor (CPU) and network load.

In this scenario, the network interface of the server is reset, and all the connected users may lose network connectivity from this remote server unexpectedly.

Cause:
When users run applications on the server, the applications trigger many object identifier (also known as OID) requests to the network miniport driver.

In this case, the Microsoft Network Device Interface Specification (NDIS) driver detects that the network miniport driver does not respond to an object identifier request in two seconds, and then the request times out. In this situation, NDIS resets the network miniport driver. When there are a large number of OID requests issued from the same kernel thread, Windows may detect that the thread is taking up too much CPU time, causing Windows CPU quota enforcement to place the thread on the CPU idle queue. The NDIS driver does not protect the calling thread from being placed on the CPU idle queue, which can cause an OID request to time out.

In severe cases, all users lose TCP network connectivity, and access to their applications is disrupted.

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:
Network connectivity is lost when many users run applications on a remote server in Windows 7 or Windows Server 2008 R2

System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014].
Fix Windows corruption errors by using the DISM or System Update Readiness tool

Version 34 (October 27, 2014):
This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found.

x32bits: http://www.microsoft.com/en-us/downl...s.aspx?id=3132
File size: 220.3 MB

x64bits: http://www.microsoft.com/en-US/downl....aspx?id=20858
File size: 538.6 MB

-Article ID: 2939489 - Last Review: October 29, 2014 - Revision: 2.0
"HTTP 403" or "0x80040001" error when you connect to a DirectAccess server from a DCA tool in Windows 7 SP1

Symptoms:
Consider following scenario:

• You have a DirectAccess Connectivity Assistant 2.0 tool installed on a computer that is running Windows 7 Service Pack 1 (SP1).
• You use the tool to connect to the DirectAccess server by using One-Time Password Certificate Enrollment (OTPCE) protocol authentication through a HTTPS connection.

In this situation, you can encounter one of the following issues:

• You receive a HTTP 403 error from the DirectAccess server as a response to the certificate-signing request.
• You receive a 0x80040001 error after you enter the one-time password (OTP).

Cause:
This issue occurs because of an error in the validation of the SSL certificate on the client-side computer that occurs before it uses OTPCE protocol authentication. Then, the cached certificate expires and is not refreshed to a valid certificate.
Applies to

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

Review and request hotfix:
http://support2.microsoft.com/kb/2939489/en-us

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

TimeZone Update...

-Article ID: 3011843 - Last Review: October 30, 2014 - Revision: 2.0
DST change for Fiji time zone for 2014.

Introduction:
Fiji announced on October 20, 2014 that the country's new daylight saving time (DST) schedule will start on November 2, 2014 and end on January 18, 2015. Windows currently has a DST start date of October 26 for the Fiji time zone. A hotfix is now available to adjust the DST settings for the Fiji time zone to the correct values.

Review and request hotfix:
DST change for Fiji time zone for 2014

-Article ID: 2989007 - Last Review: October 17, 2014 - Revision: 1.0
Update to support Ultra HD resolution for RDP sessions in Windows 7 and Windows Server 2008 R2.

Summary:
This article describes an update that supports Ultra High Definition (HD) resolution (3840x2160 resolution) for Remote Desktop Protocol (RDP) sessions in Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1.

Applies to

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

More Infos:
Update to support Ultra HD resolution for RDP sessions in Windows 7 and Windows Server 2008 R2

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

-Article ID: 2473205 - Last Review: October 17, 2014 - Revision: 51.0
List of currently available hotfixes for the File Services technologies in Windows Server 2008 and in Windows Server 2008 R2.

Summary:
This article lists the hotfixes that are currently available for users who have installed the File Services technologies on a Windows Server 2008-based computer or on a Windows Server 2008 R2-based computer. File Services provides technologies that help you manage storage, enable file replication, manage shared folders, ensure fast file searching, and enable access for UNIX client computers. This article also lists the hotfixes that are currently available for users who utilize File Services from Windows Vista-based computers or from Windows 7-based computers.

More Infos:
List of currently available hotfixes for the File Services technologies in Windows Server 2008 and in Windows Server 2008 R2

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

-Article ID: 2885209 - Last Review: November 10, 2014 - Revision: 8.0
Event ID 55 is logged in Windows 7 or Windows Server 2008 R2 and Windows may crash.

Symptoms:

When both of the following conditions are met, event ID 55 may be logged.

• You have a file server that is running Windows 7 or Windows Server 2008 R2.
• The cluster size (also known as the allocation unit size) for an NTFS volume is larger than 4 kilobytes (KB).

Specifically, the following event is logged in the System log:
Log Name: System
Event Type: Error
Event Source: NTFS
Event ID: 55
Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"
Additionally, because of file system corruption, the server may crash.

Cause:
This issue occurs because the BITMAP attribute of the NTFS metafile cannot roll back when an exception is raised after you modify the metafile. When the system tries to extend the BITMAP attribute, there is no transaction in progress, and the attribute snapshots are purged before the system starts to process the exception. In this situation, file corruption may occur, and NTFS event ID 55 may be logged.

Resolution:
To resolve this issue, we have released hotfixes for Windows 7 or Windows Server 2008 R2.

Note: This hotfix does not fix the existing file system corruption. Therefore, you have to run the Chkdsk command together with the /f or /r parameter after you apply the hotfix.



Applies to

• 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
• Windows 7 Enterprise
• Windows 7 Home Basic
• Windows 7 Home Premium
• Windows 7 Professional
• Windows 7 Starter
• Windows 7 Ultimate

Review and request hotfix:
http://support2.microsoft.com/kb/2885209/en-us

Note: Might superseded the automated Windows Update:
Article ID: 2928562 - Last Review: April 8, 2014 - Revision: 2.0
Event 55 when you copy an encrypted folder to EFS shared folder in Windows.

-Article ID: 2833914 - Last Review: November 11, 2014 - Revision: 2.0
"Interactive Logon: Smart card removal behavior" Group Policy setting doesn't work as expected in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

• You log on to a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based computer by using a smart card.
• You configure the following Group Policy setting to lock the computer or force a user to log off when the smart card is removed: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Smart card removal behavior
• The Interactive Services Detection dialog box appears, and then you click View the message.
• In the console session, you click Return now to return to the regular user session.
• You remove the smart card from the computer.

In this scenario, you are not forced to log off from the computer or the computer is not locked as expected.
Cause:
This issue occurs because the monitoring thread is canceled and the corresponding node is deleted when a WTS_CONSOLE_DISCONNECT event is fired.
Applies to

• 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
• 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:
"Interactive Logon: Smart card removal behavior" Group Policy setting doesn't work as expected in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 3002301 - Last Review: November 12, 2014 - Revision: 1.0
A memory leak in nonpaged pool memory occurs when a domain controller is running Windows Server 2008 R2.

Symptoms:
When a domain controller is running Windows Server 2008 R2, a memory leak in nonpaged pool memory may occur. This problem occurs when the domain controller is under heavy load and continues to occur until the domain controller stops responding and pool memory is exhausted.

Cause:
This problem occurs because of a race condition in the SMB redirector.

Workaround:
To work around this problem, restart the domain controller.
Applies to

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

Review and request hotfix:
A memory leak in nonpaged pool memory occurs when a domain controller is running Windows Server 2008 R2

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

-Article ID: 2969351 - Last Review: November 12, 2014 - Revision: 2.0
The .NET Framework 4.6 Preview (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2.

About the Microsoft .NET Framework 4.6 Preview (Offline Installer):
The Microsoft .NET Framework 4.6 Preview is a highly compatible, in-place update to the Microsoft .NET Framework 4, the Microsoft .NET Framework 4.5, the Microsoft .NET Framework 4.5.1, and the Microsoft .NET Framework 4.5.2.

The offline package can be used in situations in which the web installer cannot be used because of lack of Internet connectivity. When it is possible, we recommend that you use the web installer instead of the offline package for optimal efficiency and bandwidth requirements.
Applies to

• Windows Vista Service Pack 2
• Windows Server 2008 Service Pack 2
• Windows 7 Service Pack 1
• Windows Server 2008 R2 Service Pack 1
• Windows 8
• Windows Server 2012 Standard
• Windows Server 2012 Datacenter
• Windows 8.1
• Windows Server 2012 R2 Standard
• Windows Server 2012 R2 Datacenter

Download information:
The .NET Framework 4.6 Preview (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2

----------Article ID: 2969350 - Last Review: November 12, 2014 - Revision: 3.0-----------

Microsoft .NET Framework 4.6 Preview Language Pack (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and, Windows Server 2012 R2

-Article ID: 2998530 - Last Review: November 12, 2014 - Revision: 1.0
Disc is ejected unexpectedly when an application is writing to a CD or DVD drive in Windows 7 or Windows Server 2008 R2.

Symptoms:
An application is writing to the disc in a CD or DVD drive on a computer that's running Windows 7 or Windows Server 2008 R2. If you press the Eject button on the drive in this situation, the drive should be locked and nothing should happen. Unexpectedly, however, the disk is ejected. This causes data loss on the disc.

Cause:
This problem occurs because of a bug in the IOCTL_STORAGE_MEDIA_REMOVAL control code.
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 Foundation
• Windows Server 2008 R2 Standard

Review and request hotfix:
Disc is ejected unexpectedly when an application is writing to a CD or DVD drive in Windows 7 or Windows Server 2008 R2

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

-Article ID: 3001264 - Last Review: November 12, 2014 - Revision: 1.0
"0x80073B92" error when you perform a Bare Metal Recovery on a Windows 7 or Windows Server 2008 R2-based UEFI computer.

Symptoms:
Consider the following scenario:

• You have two hard disks installed on a Unified Extensible Firmware Interface (UEFI) computer that's running Windows 7 or Windows Server 2008 R2.
• You have Windows installed on one of the hard disks.
• In Disk Management, you configure a redundant array of independent disks (RAID Levels and SQL Server)
  (RAID) level 1, and you mirror the system drive to the hard disk that does not have Windows installed.
• You install the Windows Server Backup feature.
• You perform a full backup of Windows.
• You restart the computer to Windows Recovery Environment (WinRE), and then you perform a Bare Metal Recovery (BMR) operation.

In this scenario, the recovery fails, and you receive the following error message:

Code:

The system image restore failed. 
Error Detail: The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. (0x80073B92)

Cause:
This problem occurs because there are two Extensible Firmware Interface (EFI) system partitions after software mirroring is enabled. During the BMR process, the restore engine tries to create a list of files to be excluded from recovery. To create this list, the restore engine tries to retrieve the system volume name. This function fails because there is more than one EFI system partition. Therefore, the BMR restore engine cannot create the list of files to be excluded, and the recovery operation fails.
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 Foundation
• Windows Server 2008 R2 Standard

Review and request hotfix:
"0x80073B92" error when you perform a Bare Metal Recovery on a Windows 7 or Windows Server 2008 R2-based UEFI computer

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

-Article ID: 3001265 - Last Review: November 12, 2014 - Revision: 1.0
"Access Denied" error and all objects and child OUs under OU are deleted in GPMC 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 use Group Policy Management Console (GPMC) to unlink a Group Policy Object (GPO) from an organizational unit (OU).
• You link another GPO to the OU, or you try to delete this OU.

In this scenario, you receive an "Access Denied" error message, and all the objects and child OUs under this OU are deleted.
Note The OU is not deleted because it is under protection.

Cause:
This issue occurs because of the inconsistent permission in GPMC.
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:
http://support2.microsoft.com/kb/3001265/en-us

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

-Article ID: 3003385 - Last Review: November 12, 2014 - Revision: 1.0
"Access Violation" error when AzMan processes business rules in Windows 7 SP1 or Windows Server 2008 R2 SP1.

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 open a .NET Framework application that is running under Internet Information Services (IIS) on the computer.
• The application uses Windows Authorization Manager (AzMan).
• You run the application to call the AccessCheck method.
• Some business rules are processed during the call.

In this scenario, the application returns an "Access Violation" error randomly.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:
"Access Violation" error when AzMan processes business rules in Windows 7 SP1 or Windows Server 2008 R2 SP1