List of Available Hotfixes for Windows 7

NoN · 13 Nov 2013

Visual C++ Redistributable for Visual Studio 2012 Update 4 (November 13, 2013)

The Visual C++ Redistributable Packages install runtime components of Visual C++ libraries that are required to run applications developed using Visual Studio 2012 on a computer that does not have Visual Studio 2012 installed. These packages install runtime components of the C Runtime (CRT), Standard C++, ATL, MFC, C++ AMP, and OpenMP libraries.

Download

NoN · 10 Dec 2013

-Article ID: 2905247 - Last Review: December 10, 2013 - Revision: 1.0
Microsoft security advisory: Insecure ASP.NET site configuration could allow elevation of privilege

Introduction:
This security update resolves a vulnerability in the Microsoft .NET Framework that could allow elevation of privilege on a server system if a user views a specially crafted webpage by using a web browser that can run ASP.NET applications.

Applies to:

This article applies to the following:

Microsoft .NET Framework 4.5.1 when used with:
Windows 7 Service Pack 1
- Windows 8.1
- Windows RT 8.1
- Windows Server 2012 R2
- Windows 8.1 Preview
- Windows RT 8.1 Preview
- Windows Server 2012 R2 Preview
- Windows 8
- Windows RT
- Windows Server 2012
Microsoft .NET Framework 4.5.1 Release Candidate when used with:
- Windows 8
- Windows RT
- Windows Server 2012
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
- Windows Vista Service Pack 2
- Windows Server 2008 Service Pack 2
Microsoft .NET Framework 4.5 when used with:
- Windows 8
- Windows RT
- Windows Server 2012
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
- Windows Vista Service Pack 2
- Windows Server 2008 Service Pack 2
Microsoft .NET Framework 4 when used with:
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
- Windows Vista Service Pack 2
- Windows Server 2008 Service Pack 2
- Windows XP Service Pack 3
- Windows Server 2003 Service Pack 2
Microsoft .NET Framework 3.5.1 when used with:
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
Microsoft .NET Framework 3.5 when used with:
- Windows 8.1 Preview
- Windows Server 2012 R2 Preview
- Windows 8
- Windows Server 2012
Microsoft .NET Framework 2.0 Service Pack 2 when used with:
- Windows Vista Service Pack 2
- Windows Server 2008 Service Pack 2
- Microsoft Windows XP Service Pack 3
- Microsoft Windows Server 2003 Service Pack 2
Microsoft .NET Framework 1.1 Service Pack 1 when used with:
- Windows Server 2003 Service Pack 2 32-bit Edition

Download appropriate Microsoft .NET Framework security advisory for your system:

Microsoft security advisory: Insecure ASP.NET site configuration could allow elevation of privilege

NoN · 10 Dec 2013

-Article ID: 2905454 - Last Review: December 10, 2013 - Revision: 2.0
An update is available that changes the currency symbol of Latvia to the euro (€) in Windows

Introduction:
An update is available that changes the currency symbol of Latvia from the Latvian lats (Ls) to the euro (€) in Windows.

Note Latvia adopts the euro on January 1, 2014.

This update applies to the following operating systems:

Windows 8
Windows Server 2012
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2 SP1
Windows Server 2008 Service Pack 2 (SP2)

Update for Windows 7 for x64-based Systems (KB2905454):
Download Update for Windows 7 for x64-based Systems (KB2905454) from Official Microsoft Download Center

Update for Windows 7 for x86-based Systems (KB2905454):
Download Update for Windows 7 (KB2905454) from Official Microsoft Download Center

robinb9 · 10 Dec 2013

still waiting for the hotfix for Outlook 2010 after installing sp2. actually it was suppose to go into a cumulative outlooks update in this months patch Tuesday but it did not

NoN · 10 Dec 2013

robinb9 said:

still waiting for the hotfix for Outlook 2010 after installing sp2. actually it was suppose to go into a cumulative outlooks update in this months patch Tuesday but it did not

Hi there,
Im not aware about Outlook 2010 as i'm not using Microsoft Office at all, but you could have a look at download center HERE if something appears to suit your needs.:)

NoN · 30 Dec 2013

Those are Windows 7 SP1 Hot-fixes that did escaped to our attention...[PART ONE]

-Article ID: 2618535 - Last Review: October 12, 2011 - Revision: 1.0
USB HID keyboard incorrectly reports the previous auto-repeat scan code in Windows 7 or in Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

You install Windows 7 or Windows Server 2008 R2 on a computer that has multiple processors installed.
You use a USB Human Interface Device (HID) keyboard on the computer.
You press different keys on the keyboard.

In this scenario, the USB HID keyboard may incorrectly report the previous auto-repeat scan code.

Cause:
The issue occurs because of a race condition between the new auto-repeat scan code and the previous auto-repeat scan code. Sometimes, the HID keyboard filter driver (Kbdhid.sys) overwrites the data of the previous auto-repeat scan code with the data of new auto-repeat scan code.

When the race condition occurs, the driver does not stop the previous auto-repeat routine timer if the keyboard reports a new scan code. Therefore, you encounter the issue that is described in the "Symptoms" section.

Review & request hotfix:
http://support.microsoft.com/kb/2618535/en-us

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

-Article ID: 2614451 - Last Review: December 14, 2011 - Revision: 1.0
"STOP: 0x0000007E" error occurs when you write some data onto a CD or DVD in Windows Server 2008 R2 or in Windows 7.

Symptoms:
When you try to write some data onto a CD or DVD on a computer that is running Windows Server 2008 R2 or Windows 7, the computer may stop responding. Additionally, you receive the following Stop error message:

Code:

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

Notes: This Stop error describes a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED issue.

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

Cause:
This issue occurs because of an error in the Udfs.sys driver. Under certain conditions, the Udfs.sys driver tries to access a variable without checking whether its value is NULL. If its value is NULL, the issue described in the "Symptoms" section occurs.

Review & request hotfix:
http://support.microsoft.com/kb/2614...rss&spid=14019

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

-Article ID: 2635732 - Last Review: December 14, 2011 - Revision: 1.0
The same WHEA error is logged again even though no uncorrectable error has occurred on a WHEA-enabled computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

You have a computer that is based on a Windows Hardware Error Architecture (WHEA)-enabled platform.
The platform has a CPU that supports Machine Check Architecture (MCA).
The computer is running Windows 7 or Windows Server 2008 R2.
An uncorrectable error occurs which causes a machine-check exception, and then causes a Stop error.
The computer is restarted automatically.
The uncorrectable error is collected by WHEA and logged in the System log.
You perform a soft restart on the computer.

In this scenario, the same WHEA error is logged again in the System log even though no uncorrectable error has occurred.

Cause:
The issue occurs because the IA32_MCi_STATUS machine check error status registers (MSRs) are not cleared during the soft restart.

Workaround:
To work around this issue, you have to turn off the computer and then turn it on again.

Review & request hotfix:
http://support.microsoft.com/kb/2635...rss&spid=14019

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

-Article ID: 2653030 - Last Review: February 16, 2012 - Revision: 1.0
Windows Media Player 12 does not play some AVI files that were created by a third-party and that include an AVI super index chunk correctly in Windows 7.

Symptoms:
Consider the following scenario. You use Windows Media Player 12 on a computer that is running Windows 7 to play some AVI files that were created by a third-party application or by third-party hardware. The AVI files include an AVI super index chunk. In this scenario, Windows Media Player 12 does not play the files correctly. Additionally, you receive an error message that resembles the following:

An internal error has occurred.

Cause:
This issue occurs because Microsoft Media Foundation does not parse an index chunk in the AVI files correctly.

Workaround:
To work around the issue, regenerate the AVI files so that every AVI standard index chunk contains more than one entry.

Review & request hotfix:
http://support.microsoft.com/kb/2653030/en-us

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

-Article ID: 2582203 - Last Review: February 16, 2012 - Revision: 3.0
A process that is being terminated stops responding in Windows 7 or in Windows Server 2008 R2.

Symptoms:
On a computer that is running Windows 7 or Windows Server 2008 R2, a process that is being terminated stops responding. When this issue occurs, the main thread of the process becomes blocked, and the process does not terminate.

If you analyze the call stack of the process when this issue occurs, you notice that a thread is blocked in the ntdll!NtReleaseKeyedEvent() function.

Cause:
This issue occurs because the main thread that terminates the process tries to reactivate another thread that was terminated when the thread released an SRW lock. This race condition causes the process to stop responding.

Review & request hotfix:
A process that is being terminated stops responding in Windows 7 or in Windows Server 2008 R2

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

-Article ID: 2461249 - Last Review: February 16, 2012 - Revision: 4.0
The Task Scheduler service runs the same job two times in Windows Server 2008, in Windows Vista, in Windows 7 or in Windows Server 2008 R2.

-Article ID: 2698800 - Last Review: May 9, 2012 - Revision: 1.0
Task Scheduler runs a missed task unexpectedly on a computer that is running Windows 7 or Windows Server 2008 R2.
are complementary fixes to each other:
-Article ID: 2787046 - Last Review: January 24, 2013 - Revision: 5.0
Task that is created by using the "AT" command is not deleted after it is executed in Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Symptoms:
When you use the AT command to schedule tasks on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, you experience one of the following issues.

Issue 1:
When you schedule a single execution task by using the ATcommand, the task is not deleted after the task is executed. Specifically, you cannot find the task by using the AT command, but the task is listed in the Task Scheduler snap-in.at

Issue 2:
Assume that you schedule a single execution task that runs at a scheduled time or date by using the ATcommand. In this situation, the task is not deleted after the task is executed, and the task runs weekly.

Note:
On a computer that is running a version of Windows that is earlier than Windows Vista and Windows Server 2008, task information is stored in a .job file.
On a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, task information is stored in an .xml file. Additionally, when you schedule a task by using the ATcommand, a .job file is created for compatibility.

Cause:
These issues occur because the schema in the .job file does not have the "End boundary" and "Delete task as soon as its finished" nodes. When Schedsvc.dll registers a task by using the ATcommand, the Task Scheduler Compatibility plugin creates the .xml file that stores the task definition. However, the Task Scheduler schema v1.0 that Task Scheduler uses to create the .job file does not have the "End boundary" and "Delete task as soon as its finished" nodes. Therefore, the issues that are described in the "Symptoms" section occur.
Review & request hotfix:
http://support.microsoft.com/kb/2787046/en-us

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

-Article ID: 2627489 - Last Review: February 16, 2012 - Revision: 1.0
Event 1073 is logged after you cancel the logoff process in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You try to log off a computer that is running Windows 7 or Windows Server 2008 R2 without saving changes to an item.
You are prompted to save the item, and you click Cancel in the dialog box.
You are prompted to close some programs before you can log off the computer, and you click Cancel in the dialog box.

Note This issue also occurs if you close a Remote Desktop or a Citrix application before you log off the computer.

Cause:
This issue occurs because the ExitWindowsEx function does not handle the EWX_LOGOFF flag correctly.

Resolution:
After you install this hotfix, the following event is added to Windows. This event handles situations in which the logoff process is canceled.
Type: WARNING

Event ID: 1077

Description: The attempt by user username to logoff computer computername failed.

Review & request hotfix:
http://support.microsoft.com/kb/2627489/en-us

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

-Article ID: 2697645 - Last Review: May 9, 2012 - Revision: 1.0
The files in the previous session are missing from a CD-RW disc when you add some new files to the disc on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You burn a CD-rewritable (CD-RW) disc by using the Mastered format on a computer that is running Windows 7 or Windows Server 2008 R2.
You burn a folder that contains many files to the CD-RW disc.
You burn another folder that contains some files to the CD-RW disc by using a new session.

In this scenario, all the files in the first folder are missing from the CD-RW disc.

Cause:
This issue occurs because of an error in the Image Mastering API (IMAPI) module.

Review & request hotfix:
http://support.microsoft.com/kb/2697...rss&spid=14019

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

-Article ID: 2697865 - Last Review: May 9, 2012 - Revision: 1.0
The Spoolsv.exe process stops responding when you connect to more than 200 network printers from a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
When you connect to more than 200 network printers that are hosted on a print server from a client computer that is running Windows 7 or Windows Server 2008 R2, the Print Spooler (Spoolsv.exe) process stops responding.

Cause:
This issue occurs because the threads that the system uses to enumerate the printers on the client computer are exhausted.

Review & request hotfix:
The Spoolsv.exe process stops responding when you connect to more than 200 network printers from a computer that is running Windows 7 or Windows Server 2008 R2

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

-Article ID: 2769618 - Last Review: December 24, 2012 - Revision: 2.0
Cannot play an audio file when an audio file is already playing in Windows Media Player on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you play an audio file in Windows Media Player on a computer that is running Windows 7 or Windows Server 2008 R2. However, when you try to use another application to play another audio file at the same time, the application does not play the second file. Additionally, you receive an error message that resembles the following from the second application:

0x887C0033 AEERR_TIMED_OUT

Note The application tries to play the audio file in shared mode.

Cause:
This issue occurs because of a timing problem that occurs in the audio engine. This behavior occurs when the kernel system timer is set to 10 milliseconds by the Multimedia Class Scheduler service (MMCSS). Therefore, a second audio stream occasionally encounters this time-out error.

Review & request hotfix:
http://support.microsoft.com/kb/2769618/en-us

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

-Article ID: 2512352 - Last Review: December 27, 2012 - Revision: 2.0
Windows Server Backup utility does not back up some newly created files in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You use the Windows Server Backup utility to back up files on a volume regularly.
Files are created or renamed in a certain short period of time in snapshot creation.

In this scenario, the file is not backed up, and the backup operation finishes in the incomplete backup status.

If you use the Windows Server Backup utility for incremental backups, the next backup operation is a full backup instead of an incremental backup. Therefore, the chain of incremental backup sets is broken.

Cause:
This issue occurs because the Wbengine.exe service does not appropriately handle files that are created or renamed in a certain period of time.

Review & request hotfix:
http://support.microsoft.com/kb/2512...rss&spid=14019

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

-Article ID: 2707589 - Last Review: June 13, 2012 - Revision: 1.0
You may not receive correct rich error information when a COM application encounters an error in Windows 7 SP1 or in Windows Server 2008 R2 SP1.

Symptoms:
Consider the following scenario:

You run a COM application on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
The application uses Neutral Apartment as the threading model for the COM objects.
The application encounters an error.

In this scenario, you may not receive correct rich error information. However, the rich error information that you receive helps you take necessary actions that are based on the error.

Note: If the COM application uses the Free threading model for the COM objects, this issue does not occur.

Cause:
This issue occurs because the errorInfo object is cleared and marked as NULL in the Neutral component that receives an interface pointer as an argument.

Review & request hotfix:
http://support.microsoft.com/kb/2707...rss&spid=14019

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

-Article ID: 2531912 - Last Review: February 13, 2013 - Revision: 2.0
A computer that has smart card logon enabled stops responding after you remove and then reinsert a smart card in Windows 7, Windows Vista, Windows Server 2008 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running one of the following operating systems:
- Windows Vista
- Windows Server 2008
- Windows 7
- Windows Server 2008 R2
You enable smart card logon on the computer.
You remove and then reinsert the smart card.

In this scenario, the computer stops responding and displays the following message:

Reading Smart Card

Notes:

You must restart the computer to resolve this issue.
This issue is more likely to occur if you attach multiple smart card readers to the computer and use multiple smart cards.
This issue typically occurs after you remove and reinsert the smart card about 20 times.

Cause:
This issue occurs because too many removals and insertions of multiple smart cards may cause the Base Smartcard Cryptographic Service Provider (Base CSP) to stop responding.

Review & request hotfix:
http://support.microsoft.com/kb/2531...rss&spid=14019

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

-Article ID: 2718841 - Last Review: August 23, 2013 - Revision: 2.0
"0xc0000005" error message and Windows Explorer stops responding on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
On a computer that is running Windows 7 or Windows Server 2008 R2, the Windows Explorer process stops responding. Additionally, you receive the following error message:

0xc0000005

If you examine the call stack when this issue occurs, you notice that the issue is related to the NetworkItemFactory.dll component.

Cause:
This issue occurs because of a race condition. When a thread tries to close the handle to an object that is being destroyed, the operation fails.

Review & request hotfix:
"0xc0000005" error message and Windows Explorer stops responding on a computer that is running Windows 7 or Windows Server 2008 R2

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

NoN · 31 Dec 2013

Those are Windows 7 SP1 Hot-fixes that did escaped to our attention...[PART TWO]

-Article ID: 2642357 - Last Review: February 29, 2012 - Revision: 2.0
Broken shortcuts are deleted from the desktop in Windows 7.

Symptoms:
Issue 1

Considering the following scenario:

You create five or more shortcuts on the desktop of a computer that is running Windows 7.
These shortcuts are pointed to an external location. For example, the shortcuts are pointed to network resources or to removable storage devices.
The computer is disconnected from the network where the network resources reside. Or, the removable devices are disconnected from the computer.
You run the System Maintenance troubleshooter on the computer.

In this scenario, these shortcuts are deleted from the desktop.

Note These shortcuts are treated as broken shortcuts.

Issue 2

Considering the following scenario:

You create ten or more shortcuts on the desktop of a computer that is running Windows 7.
These shortcuts are pointed to executable files that were executed at least one time on the computer.
The executable files were not executed in the past three months.
You run the System Maintenance troubleshooter on the computer.

In this scenario, the System Maintenance troubleshooter offers to delete these shortcuts.

Note These shortcuts are treated as unused desktop icons.

After you install this hotfix, you can disable the "Broken Shortcut" task or the "Unused Desktop Icon" task in the System Maintenance troubleshooter by configuring the registry.

Or
Use Microsoft Fix-it Provided.

Review & request hotfix:
http://support.microsoft.com/kb/2642...rss&spid=14019

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

-Article ID: 2685889 - Last Review: April 11, 2012 - Revision: 1.0
OpenGL rendered content is still displayed after you minimize a modeless dialog box in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You enable the Aero feature on a computer that is running Windows 7 or Windows Server 2008 R2.
You run an application that uses OpenGL rendering in modeless dialog boxes.
When a modeless dialog box appears, you start the OpenGL rendered content.
You minimize the modeless dialog box.

In this situation, the OpenGL rendered content is still displayed.

Review & request hotfix:
http://support.microsoft.com/kb/2685889/en-us

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

-Article ID: 2635500 - Last Review: April 11, 2012 - Revision: 2.0
Issues when you try to display a large TIFF file that contains multiple pages by using Windows Photo Viewer in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2.

Symptoms:
Assume that you try to open a large TIFF file that contains multiple pages by using Windows Photo Viewer on a computer that is running one of the following operating systems:

Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2

In this situation, you may experience one of the following issues.

Issue 1
When you scroll through the pages in the TIFF file, the computer stops responding. Additionally, the available memory is exhausted. To recover from this issue, manually close Windows Photo Viewer by using Task Manager.

Issue 2
Window Photo Viewer does not open the TIFF file. Additionally, you receive the following error message:
Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted or is too large.

Cause:
These issues occur because of the way of that memory is allocated when Windows displays a TIFF file.

Review & request hotfix:
Issues when you try to display a large TIFF file that contains multiple pages by using Windows Photo Viewer in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2

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

-Article ID: 2684681 - Last Review: April 11, 2012 - Revision: 1.0
Iscsicpl.exe process stops responding when you try to reconnect a storage device to a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running one of the following operating systems:
- Windows Vista
- Windows Server 2008
- Windows 7
- Windows Server 2008 R2
You set up an iSCSI storage device on the computer. Then, you configure the persistent logon setting and Challenge Handshake Authentication Protocol (CHAP) authentication setting for the device.
You disconnect the network connection on the computer, and then you restart the computer.
You wait at least 30 seconds, and then you reestablish the network connection.
The iSCSI initiator user interface displays the connection state as Reconnecting.

In this scenario, the iscsicpl.exe process stops responding. Additionally, you cannot disconnect the storage device from the computer. To reestablish the connection between the storage device and the computer, you must restart the computer.

Cause:
This issue occurs because the session between the storage device and the computer is locked when the iSCSI initiator tries to log on. However, the iSCSI initiator does not try to log on after 10 failed log on attempts. Therefore, the session is not released.

Review & request hotfix:
http://support.microsoft.com/kb/2684...rss&spid=14019

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

-Article ID: 2719248 - Last Review: September 6, 2012 - Revision: 4.0
Number of UI and GDI objects increases when an application displays new animated controls in an Aero theme in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Assume that you are using an Aero theme on a computer that is running Windows 7 or Windows Server 2008 R2. When you run an application that continuously displays new animated controls, the number of UI objects and Graphics Device Interface (GDI) objects increases continuously. Additionally, the application does not run as expected. For example, the application crashes.

Notes

The maximum number of user objects for each application is 10000, and the maximum number of GDI objects for each application is 10000. When the number of objects exceeds these limits, the application does not run correctly.
The objects are released 35 seconds or more after the application stops displaying new animated controls.

Cause:
This issue occurs because new buffers are created when animated controls are displayed on a computer that uses an Aero theme. The buffers are released by a cleanup routine every 35 seconds. However, if an application continuously displays new animated controls, the issue that is described in the "Symptoms" section occurs.

Review & request hotfix:
http://support.microsoft.com/kb/2719248/en-us

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

-Article ID: 2758949 - Last Review: November 14, 2012 - Revision: 1.0
You cannot build an IP-HTTPS protocol-based connection on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

Multiple certificates are installed in the certificate store on a client computer that is running Windows 7 or Windows Server 2008 R2.
One of the certificates does not have a private key.
You try to build a connection that is based on the IP-HTTPS protocol. For example, you try to build a connection by using the DirectAccess feature.
The IP-HTTPS protocol selects the certificate that does not have a private key to build the connection.

In this scenario, the connection is not established.

Review & request hotfix:
http://support.microsoft.com/kb/2758949/en-us

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

-Article ID: 2619260 - Last Review: December 28, 2012 - Revision: 3.0
"Play To" feature does not work when two network adapters are on different subnets or when you enable Wi-Fi Direct concurrent mode in Windows 7.

Symptoms:
When you use Windows Media Player 12 on a computer that is running Windows 7, the Play To feature does not work in the following scenarios.

Scenario 1

The computer has two or more network adapters. Additionally, at least two of the network adapters are on different subnets. For example, you have an Ethernet network adapter that connects to the Internet, and you have another Wi-Fi network adapter that connects to a local area network.
You try to use the Play To feature to play media on a digital media receiver (DMR) device through the Wi-Fi connection.

In this scenario, the DMR device receives an invalid URL that contains an incorrect IP address.

Scenario 2

You enable Wi-Fi Direct concurrent mode on the computer. This mode lets Wi-Fi client mode and Wi-Fi Direct mode coexist.
You try to use the Play To feature to play media on a DMR device through the Wi-Fi Direct connection.

In this scenario, the DMR device does not play the media successfully. The device plays the media if you enable only Wi-Fi Direct mode.

Review & request hotfix:
http://support.microsoft.com/kb/2619260/en-us

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

-Article ID: 2619914 - Last Review: December 28, 2012 - Revision: 4.0
A signed driver is displayed as unsigned in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You install a driver that has a Windows Hardware Quality Labs (WHQL) or Authenticode signature on the computer.
In Device Manager, you expand the corresponding device, right-click the driver, and then click Properties.
You click the Driver Details button on the Driver tab.

In this scenario, the driver file is displayed as unsigned.

Note For example, you may encounter the issue for a network adaptor driver or a storage controller.

Cause:
This issue occurs because of incorrect logic when the Authenticode flag in the catalog file of the driver is checked.

Review & request hotfix:
http://support.microsoft.com/kb/2619914/en-us

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

-Article ID: 2614892 - Last Review: December 28, 2012 - Revision: 3.0
A computer stops responding because of a deadlock situation in the Mountmgr.sys driver in running Windows 7 or in Windows Server 2008 R2.

Symptoms:
On a computer that is running Windows 7 or Windows Server 2008 R2, the whole computer may stop responding. When this issue occurs, you have to forcibly restart the computer to recover from this issue.

Here is a sample scenario:

You install a Symantec antivirus application on a computer that is running Windows Server 2008 R2.
You run a backup application on the computer.

In this scenario, the computer stops responding.

Cause:
This issue occurs because the Mountmgr.sys driver incorrectly maintains a global mutex. This behavior causes a deadlock situation in the Mountmgr.sys driver.

Review & request hotfix:
http://support.microsoft.com/kb/2614892/en-us

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

-Article ID: 2799035 - Last Review: February 13, 2013 - Revision: 1.0
Certificate Propagation service crashes when you disconnect an RDS client from a Windows 7 or Windows Server 2008 R2-based RDS server.
Is superseded by:
-Article ID: 2797822 - Last Review: March 13, 2013 - Revision: 1.0
Hotfix is available that adds support for NIST SP 800-73-3 specification in Windows 7.

Introduction:
This article describes an available hotfix that adds support for the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-73-3 specification in Windows 7. This hotfix improves features for smart card–related Plug and Play and Personal Identity Verification (PIV) standards from the NIST. This hotfix supports the Key History object that is described in section 3.2.7 of the NIST SP 800-73-3 Part1 specification. The Key History object does not support the following in this hotfix:

Discontinued keys that have off-card certificates.
Key archival by using the smart card. Therefore, the following operations are not available:
- Imports of key material to a discontinued key container.
- Imports of certificates for a key in a discontinued key container.
- Requests for the card to generate a key pair for a discontinued key container.
- Changes to the Key History object

Notes

Currently, Windows 7 only supports the capabilities of NIST SP 800-73-2 for PIV smart cards.
According to NIST SP 800-73-3 Part1, the container name changes of a Key Management key is archived to a discontinued container. If a smart card was previously used on a computer, the smart card must be inserted into the computer before the smart card tries to use the key. This allows for the computer to recognize the new container name and find the certificate. If you do not insert the smart card, you will be unable to successfully select the certificate from a selection dialog box.

Review & request hotfix:
http://support.microsoft.com/kb/2797822/en-us
-----------------------------------------------------------------------------------------------------------

NoN · 01 Jan 2014

Those are Windows 7 SP1 Hot-fixes that did escaped to our attention...[PART THREE]

-Article ID: 2716542 - Last Review: September 3, 2012 - Revision: 2.0
A hotfix is available that enables a Windows 7-based or Windows Server 2008 R2-based computer to create a memory dump file without a page file.

Introduction:
This article describes a hotfix that enables a Windows 7-based or Windows Server 2008 R2-based computer to create a memory dump file even when there is no page file on the computer.

Currently, the computer must have at least one page file to create a dump file even though the system uses the dedicated dump file feature. Therefore, if there is no page file on the computer, the computer cannot create the memory dump file when the system crashes.

Review & request hotfix:
A hotfix is available that enables a Windows 7-based or Windows Server 2008 R2-based computer to create a memory dump file without a page file

And as a complementary Fix to above article ID 2716542:

-Article ID: 2826910 - Last Review: April 9, 2013 - Revision: 1.0
Secondary dump data is limited to 256 MB in Windows 7 and Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a Windows 7-based or Windows Server 2008 R2-based computer that crashes.
A third-party driver uses a Bug Check Callback Routine to include inaccessible memory in the secondary stream.
The secondary dump data is very large. For example, the total size is larger than 256 megabytes (MB).

In this scenario, the Bug Check Callback Routines are no longer called as soon as the 256 MB limit is reached.

Cause:
This issue occurs because the secondary dump data only allows for 32 MB per chunk and 256 MB overall.

After you apply this hotfix, you can use the following DWORD registry value to increase the maximum size to 4 gigabytes (GB) (0xFFFFFFFF):

HKLM\System\CurrentControlSet\Control\CrashControl\MaxSecondaryDataDumpSize

Note Each Bug Check Callback Routine is limited to one-eighth of this value for one or more chunks. To store more than the set limit, register the Bug Check Callback Routine multiple times. The callback order is not defined.

Review & request hotfix:
http://support.microsoft.com/kb/2826910/en-us

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

-Article ID: 2725604 - Last Review: October 10, 2012 - Revision: 2.0
SynchronizeTime task does not start at the time that you scheduled on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you change the time zone settings on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the SynchronizeTime task on the computer does not start at the time that Windows scheduled.

For example, assume that you set the time zone to (UTC+09:00) Osaka, Sapporo, Tokyo on the computer, and then you schedule a SynchronizeTime task to run every Sunday at 01:00. In this situation, the history of the SynchronizeTime task displays the run time of the task as every Monday at 01:00.

Note: To access the SynchronizeTime task, click Microsoft in the Task Scheduler, click Windows, and then click Time Synchronization.

Cause:
This issue occurs because Windows uses Coordinated Universal Time (UTC) instead of local time to calculate the necessary wait time between each instance of the task. Therefore, the wait time that is used between each instance of the task is incorrect.

Review & request hotfix:
http://support.microsoft.com/kb/2725...rss&spid=14019

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

-Article ID: 2641222 - Last Review: January 4, 2013 - Revision: 2.0
An update is available that enables the Chkdsk.exe utility to repair a corruption error on the system volume in Windows 7 or in Windows Server 2008 R2

Symptoms:
This article introduces a hotfix that updates the Chkdsk.exe utility in Windows 7 and in Windows Server 2008 R2. Currently, the Chkdsk.exe utility cannot repair certain corruption errors on the system volume. These errors occur when the boot file is allocated to the first cluster instead of the first two clusters on the system volume. After you install this hotfix, the Chkdsk.exe utility can repair this kind of corruption error.

Review & request hotfix:
http://support.microsoft.com/?kbid=2641222

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

-Article ID: 2633667 - Last Review: January 4, 2013 - Revision: 2.0
32-bit NetBIOS applications cannot receive connection close notifications in a 64-bit version of Windows 7 or in Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You run a 32-bit application on a computer that is running a 64-bit version of Windows 7 or Windows Server 2008 R2.
The application uses the network basic input/output system (NetBIOS) API to communicate with a remote computer.
The NetBIOS session is ended or closed while the application is receiving data.

In this scenario, the application does not receive notifications that the session has ended or closed and does not try to reestablish the session. You have to restart the application to recover from this issue.

Notes

You do not experience this issue when you run the 32-bit application on a computer that is running a 32-bit version of Windows 7.
You do not experience this issue if you recompile the application as a 64-bit application and then run it on a computer that is running a 64-bit version of Windows 7 or Windows Server 2008 R2.

Cause:
This issue occurs because of an error in the NetBIOS interface (Netbios.sys) driver. When the Netbios.sys driver is receiving data, the driver does not convert the network connection block (NCB) structure from 64-bit to 32-bit when the session is abandoned. Because the 32-bit application cannot understand the 64-bit NCB structure, the issue described in the Symptoms section occurs.

Review & request hotfix:
http://support.microsoft.com/kb/2633667/en-us

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

-Article ID: 2635972 - Last Review: January 4, 2013 - Revision: 2.0
You cannot open an image in a compressed (.zip) file that is protected by using a password in Windows 7.

Symptoms:
Consider the following scenario:

You set Windows Photo Viewer or Windows Live Photo Gallery as the default program to open images on a computer that is running Windows 7.
You compress an image and apply password protection to the resulting compressed (.zip) file.
You try to open the image in the compressed (.zip) file.

In this scenario, you cannot open the image in the compressed (.zip) file and you receive the following error message:

Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large.

Review & request hotfix:
http://support.microsoft.com/kb/2635...rss&spid=14019

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

-Article ID: 2800170 - Last Review: February 13, 2013 - Revision: 1.0
Mouse class installer crashes when you try to update drivers for USB HID devices in Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you attach multiple USB human interface devices (HID) to a computer that is running Windows 7 or Windows Server 2008 R2. You try to update the devices from the inbox drivers to third-party drivers. In this situation, the mouse class installer crashes.

Review & request hotfix:
http://support.microsoft.com/kb/2800...rss&spid=14019

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

-Article ID: 2797749 - Last Review: March 13, 2013 - Revision: 1.0
Explorer.exe process may crash after you add custom properties to a .doc file in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have several .doc files on a computer that is running Windows 7 or Windows Server 2008 R2.
You right-click a .doc file, you click Properties, and then you click the Custom tab.
You manually add several entries on the Custom tab.

In this scenario, the Explorer.exe process may crash.

Cause:
This issue is caused by an access violation that occurs in the Docprop.dll file.

Review & request hotfix:
http://support.microsoft.com/kb/2797...rss&spid=14019

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

-Article ID: 2799360 - Last Review: May 24, 2013 - Revision: 2.0
Svchost.exe process that hosts the network location awareness service crashes in Windows 7 or in Windows Server 2008 R2.

Symptoms:
When you are using a computer that is running Windows 7 or Windows Server 2008 R2, the Svchost.exe process that hosts the network location awareness service crashes intermittently.

Cause:
This issue occurs because a handle leak occurs in the Wldap32.dll file.

Review & request hotfix:
http://support.microsoft.com/kb/2799...rss&spid=14019

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

-Article ID: 2833001 - Last Review: May 14, 2013 - Revision: 1.0
Wmiprvse.exe process crashes when you run a WMI script on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you have a Network File System (NFS) shared folder mounted on a computer that is running Windows 7 or Windows Server 2008 R2. You run a Windows Management Instrumentation (WMI) script to obtain the disk usage information on the computer. For example, you run the following command:

select * from Win32_LogicalDisk where FileSystem <> NULL

In this situation, the Wmiprvse.exe process crashes.

Review & request hotfix:
http://support.microsoft.com/kb/2833001/en-us

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

-Article ID: 2732840 - Last Review: April 10, 2013 - Revision: 4.0
Tasklist.exe tool displays no process information on a computer that is running Windows.

Symptoms:
Assume that you use the Tasklist.exe tool on a computer that is running one of the following operating systems:

Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2
Windows 8
Windows Server 2012

When the operating system is under a heavy load, the Tasklist.exe tool displays no process information.

For example, assume that you run the following command:

tasklist.exe /FI “IMAGENAME eq lsass.exe”

In this situation, the Tasklist.exe tool displays the following message even when the Lsass.exe process is running:

INFO: No tasks are running which match the specified criteria.\n

Review & request hotfix:
http://support.microsoft.com/kb/2732...rss&spid=14019

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

-Article ID: 2847521 - Last Review: June 13, 2013 - Revision: 1.0
"0x0000010c" Stop error on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
computer that is running Windows 7 or Windows Server 2008 R2 crashes randomly. Additionally, you receive a Stop error message that resembles the following when the computer crashes:

Code:

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

Notes

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

Cause:
This issue occurs because NTFS incorrectly removes an additional create parameter (ECP) entry from an ECP list before NTFS returns the STATUS_REPARSE status. NTFS removes the ECP entry when the computer has a shared folder or file that contains NTFS reparse points, such as symbolic links. Then, when the Srv2.sys file reuses the ECP list in a new call, the issue occurs.

Review & request hotfix:
http://support.microsoft.com/kb/2847521/en-us

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

-Article ID: 2836405 - Last Review: July 10, 2013 - Revision: 1.0
Access violation occurs on an Internet Explorer process when you try to open an .xml document 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 try to open an .xml document by using Windows Internet Explorer, an access violation occurs on an Internet Explorer process, and a dialog box that contains no content appears. Additionally, the access violation and Event ID 1000 are reported as an application error in the application event log.

Review & request hotfix:
http://support.microsoft.com/kb/2836...rss&spid=14019

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

-Article ID: 2851323 - Last Review: July 10, 2013 - Revision: 1.0
Windows Explorer does not display all network computers 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 in a network environment.
You use Windows Explorer to view all the computers that are connected in the network.
Windows uses the Computer Browser service to map the computers that are connected in the network.

Note: The Active Directory directory service is the default service for mapping computers that are connected in a network. However, Windows uses the Computer Browser service when the Active Directory directory service is not available.

Cause:
This issue occurs because the call to the initialization function has a wrong priority.

Workaround:
To work around this issue, use a Universal Naming Convention (UNC) path to find the computers in the network.

Review & request hotfix:
http://support.microsoft.com/kb/2851...rss&spid=14019

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

-Article ID: 2832829 - Last Review: August 13, 2013 - Revision: 2.0
"0x00000019" Stop error when you try to shut down a Windows-based computer.

Symptoms:
Assume that you have a computer that is running Windows 7, Windows Server 2008 R2, Windows 8, or Windows Server 2012. The computer is installed with a video card that is compliant with Intel High Definition Audio Specification for HDMI. When you try to shut down the computer, you may receive a Stop error message that resembles the following:

Code:

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

Notes

This Stop error describes a BAD_POOL_HEADER issue.
The parameters in this Stop error message vary, depending on the configuration of the computer.
Not all "Stop 0x00000019" errors are caused by this issue.
This issue occurs when system tries to stop the process of the High Definition Audio Controller driver on the video card. The error occurs in the Hdaudio.sys driver.

Cause:
The issue occurs because the Hdaudio.sys driver tries to process the audio information when the uninitialized internal firmware memory within the video card is set in a certain manner. The result is internal pool corruption. You receive the stop error when the Hdaudio.sys driver is unloaded, a process that typically occurs when you try to shut down the computer.

Review & request hotfix:
http://support.microsoft.com/kb/2832829/en-us

NoN · 01 Jan 2014

Those are Windows 7 SP1 Hot-fixes that did escaped to our attention...[PART FOUR]

-Article ID: 2835595 - Last Review: May 14, 2013 - Revision: 1.0
The logon pop-up dialog box does not appear when you connect a Windows 7 SP1-based or Windows Server 2008 R2-based computer to a network.

Symptoms:
Assume that you enable 802.1X authentication for network access control in a workgroup environment. When you connect a computer that has Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 installed to a network, the logon pop-up balloon that you use to enter your credentials in order to log on to the 802.1X secured network does not appear.

Cause:
This issue occurs because there is a race condition between the two threads.

Workaround:
To work around the issue, use one of the following methods:

Disable and enable the network adapter.
Restart the Wired AutoConfig service (dot3svc).

Review & request hotfix:
The logon pop-up dialog box does not appear when you connect a Windows 7 SP1-based or Windows Server 2008 R2-based computer to a network

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

-Article ID: 2815853 - Last Review: April 9, 2013 - Revision: 1.0
RPC service crashes on a Windows 7-based or Windows Server 2008 R2-based COM client.

Symptoms:
Consider the following scenario:

You have a Windows 7-based or Windows Server 2008 R2-based computer that runs as a COM client.
You have a COM server that supports remote procedure calls (RPCs) from the COM client.
The COM client uses the RemoteServerName registry entry to obtain the remote COM server name dynamically.

In this scenario, the RPC service crashes on the COM client. Additionally, the COM client restarts after the RPC service crashes.

Note: The RemoteServerName registry entry is located under the following registry subkey:
\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{GUID}

Cause:
This issue occurs because the GetRegistryStringValue function assumes that the value type of the RemoteServerName registry entry is REG_MULTI_SZ. Therefore, a heap overflow occurs in the rpcss!GetRegistryStringValue method.

Review & request hotfix:
http://support.microsoft.com/kb/2815...rss&spid=14019

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

-Article ID: 2824546 - Last Review: May 21, 2013 - Revision: 2.0
Incorrect DHCP packet is sent when DHCP client receives a DHCP offer on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer.

Symptoms:
Assume that you have a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based Dynamic Host Configuration Protocol (DHCP) client computer. The client computer has the hotfix from KB 2393659 installed. When the DHCP client receives a DHCP offer, the client sends out a DHCP offer instead of a DHCP request.

Notes

The expected behavior is that the DHCP client should send out a DHCP request when the DHCP client receives a DHCP offer.
DHCP offer should only be sent by the DHCP server.
When you connect the client to a third-party network device that can detect the legality of DHCP servers, the client is perceived as an unauthorized DHCP server. Therefore, the port connection to the client is blocked.

Here is a network trace sample:

Code:

58476    12:56:58 16/11/2012        DHCPSrv-1  Client             DHCP:Reply, MsgType = OFFER, TransactionID = 0xE5F0E526
58494    12:56:58 16/11/2012        0.0.0.0   255.255.255.255                DHCP:Reply, MsgType = OFFER, TransactionID = 0xE5F0E526

When the Window 7 client sends the reply offer together with source IP 0.0.0.0, the client will be blocked because it looks like an unauthorized DHCP server.

Cause:
This issue occurs because DHCP clients use the same buffer for sending and receiving packets.

Typically, when an active listener receives a duplicate offer intended for an interface that has already received its offer, the buffer that corresponds to the destination interface will be overwritten. However, the thread for that interface uses the buffer and prepares to send a request. Therefore, the sender sends an offer instead of a request.

Review & request hotfix:
http://support.microsoft.com/kb/2824...rss&spid=14019

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

-Article ID: 2799464 - Last Review: March 13, 2013 - Revision: 1.0
Memory size of video card is displayed incorrectly in x64-based versions of Windows 7 and Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a video card that has more than 4 gigabytes (GB) of memory.
You use the video card on a computer that is running an x64-based version of Windows 7 or Windows Server 2008 R2.
You view the memory size of the video card in the Adapter Properties dialog box.

In this scenario, the memory size of the video card is displayed incorrectly. For example, if the actual memory size of video card is 6 GB, the memory size is displayed as 2 GB.

Cause:
This issue is caused by a 64-bit and 32-bit number conversion problem that occurs when available video card memory is retrieved.

Review & request hotfix:
http://support.microsoft.com/kb/2799...rss&spid=14019

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

-Article ID: 2798670 - Last Review: March 18, 2013 - Revision: 2.0
USB audio stream stalls on a computer that is running Windows 7 or Windows Server 2008 R2.
Is Superseded by January 14, 2014 Windows Update Security bulletin: MS13-081

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

-Article ID: 2767671 - Last Review: May 15, 2013 - Revision: 3.0
MPEG-2 Demultiplexer filter or MPEG-2 Splitter filter does not correctly play an MPEG-2 TS-encoded file in Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012.

Symptoms:
Assume that you play an MPEG-2 transport stream (TS)-encoded file by using the MPEG-2 Demultiplexer filter or the MPEG-2 Splitter filter on a computer that is running one of the following operating systems:

Windows 7
Windows Server 2008 R2
Windows 8
Windows Server 2012

However, the beginning of the file does not play.

Review & request hotfix:
http://support.microsoft.com/kb/2767...rss&spid=14019

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

-Article ID: 2755625 - Last Review: May 24, 2013 - Revision: 2.0
Event ID 4097 is not logged as expected when you cannot install an ActiveX control from a website to a computer that is running 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 enable the following Group Policy setting to enable ActiveX controls to be installed on the computer. Computer Configuration\Administrative Templates\Windows Components\ActiveX Installer Service\Approved Installation Sites for ActiveX Controls
You define one or several host URLs in the policy setting to limit from where you can install ActiveX controls.
You try to install an ActiveX control from a website that is not listed in the host URLs by using a standard user account on the computer. As expected, the installation is not successful.

In this scenario, the following event is not logged in the Application log as expected:
Log Name: Application
Source: AxInstallService
Event ID: 4097
Task Category: None
Level: Error
Description: Attempt to install control link to the ActiveX control failed. The host URL link to the website is not in policy.

Review & request hotfix:
http://support.microsoft.com/kb/2755...rss&spid=14019

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

-Article ID: 2685088 - Last Review: June 13, 2012 - Revision: 4.0
The screen saver grace period does not work as expected if the period exceeds 60 seconds on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you use a screen saver that requires you to enter a password when you resume a Windows 7-based or Windows Server 2008 R2-based computer. When you change the screen saver grace period to a period that is more than 60 seconds, the actual grace period never exceeds 60 seconds.

Note You can adjust the screen saver grace period by changing the value of the ScreenSaverGracePeriod registry entry. This value specifies the delay between the appearance of a screen saver that requires a password on resume, and the enforcement of the password requirement.

Cause:
This issue occurs because of a 60-second limitation for the ScreenSaverGracePeriod registry entry.

Review & request hotfix:
http://support.microsoft.com/kb/2685088/en-us

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

-Article ID: 2876213 - Last Review: September 11, 2013 - Revision: 2.0
Error message when you click New Scan in Windows Fax and Scan on a Windows-based computer .

Symptoms:
Assume that you have a Web Services for Devices (WSD)-based scanner installed on a computer that is running one of the following operating systems:

Windows 8
Windows Server 2012
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2 SP1

When you click New Scan in Windows Fax and Scan, the scan operation fails. Additionally, you receive an error message that resembles the following:
An error occurred while setting scanner properties. If another program is scanning, please wait for it to complete and try again.

Cause:
This issue occurs because it takes longer than expected for the scan data to be transferred from the WSD scanner to the computer. Therefore, the read request returns empty data to the driver of the WSD scanner. Then, the driver for the WSD scanner assumes that an issue occurred and interrupts the scan operation.

Review & request hotfix:
http://support.microsoft.com/kb/2876213/en-us

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

-Article ID: 2891362 - Last Review: December 12, 2013 - Revision: 1.0
A file copy operation fails when files or folders have long paths in Windows Explorer.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).
You use Windows Explorer to try to copy files or folders in order to paste them into some other folder.
The files or folders that you copy have have paths that exceed the maximum allowable path length.

In this scenario, the behavior of the copy operation is unreliable and fails because of the length of the file or folder path. Additionally, you may experience one of the following symptoms:

The copy operation fails and generates a message that states that the path (file name) is too long. The message also suggests that you shorten the file name and try to copy again.
The copy operation does not start. In this case, no message is generated.
The copy operation starts, copies a few files or folders, and then fails without generating a message.

This problem may prevent some files or folders from being copied. You may not realize the the problem occurred if you do not receive an error message. Different symptoms may occur, depending on how the files are selected for copying.

Note This problem can also occur when you try to copy files or folders from Volume Shadow Copy Service snapshots if the file or folder length in the snapshot exceeds the maximum path length.

Review & request hotfix:
http://support.microsoft.com/kb/2891...rss&spid=14019

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

-Article ID: 2905569 - Last Review: December 12, 2013 - Revision: 1.0
The scroll bar in a 32-bit application does not move on a computer that is running a 64-bit version of Windows.

Symptoms:
You run a 32-bit application on a 64-bit version of Windows 7 or Windows Server 2008 R2. After several weeks of running the 32-bit application, you may find that the scroll bar in the application does not move and that the application's user interface does not respond to mouse clicks.

Cause:
This problem occurs when the window handle number exceeds the handle limit for the 32-bit application.

Review & request hotfix:
http://support.microsoft.com/kb/2905...rss&spid=14019

NoN · 03 Jan 2014

Those two next Hotfixes (Kb article ID: 2732673 & Kb Article ID: 2728738) are for the ones that have installed at the time:

An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

It's revised versions!

-Article ID: 2732673 - Last Review: November 13, 2013 - Revision: 13.0
"Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2.

Symptoms:
Consider one of the following scenarios:

Scenario 1:

You enable Remote Desktop on a computer (computer A) that is running Windows 7 or Windows Server 2008 R2.
You configure an Outlook 2010 client that is installed on computer A to save Personal Folder (.pst) files on another computer (computer B). Computer B is a file server that is running Windows Server 2008 R2.
You establish a remote connection to computer A from a client computer, and then start Outlook 2010 in the Remote Desktop session.

In this scenario, you receive the following error message that states that the .pst file is corrupted:
Delayed Write Failed
Windows was unable to save all the data for the file file path. The data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere.

Additionally, the following event is logged in the System log on computer A:
MUP Event ID 140

Binary data:
In Words

0000: 00040004 00300002 00000000 8004008C
0008: 00000000 C0000022 00000000 00000000
0010: 00000000 00000000 C0000022

Note: status code C0000022 = STATUS_ACCESS_DENIED, Access Denied

Note: This issue does not occur if you disable the Server Message Block version 2 (SMBv2) file sharing protocol on the file server.

Scenario 2:

You have mapped a network drive to a server share and you use offline files to make the data on this share available offline.
You have a MUP filter driver installed (e.g. disc encryption Software).
You try to open a file (e.g. a text file) of a given size from this share while you're connected to the Network, although the actual SMB Connection to the server is not yet established.

In this Scenario, you might get the this error message: Cannot open the %% file. Make sure a disk is in the drive you specified
If you click on OK the text file will be empty. If you now close and open the file again it might work.

Cause:
Scenario 1:
This issue occurs because the Outlook 2010 client tries to write data to an open SMBv2 file ID that has read-only access.

Scenario 2:
This issue occurs because the offline files client tries to read the file from the server before the actual SMB connection is established.

Download Hotfix:
http://support.microsoft.com/kb/2732673/en-us

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

-Article ID: 2728738 - Last Review: November 13, 2013 - Revision: 7.0
You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles.

Symptoms:

Consider the following scenario:

You have a client computer that is running Windows 7 or Windows Server 2008 R2 in a network environment.
User accounts are configured to use roaming profiles when users log on to the computer from a remote site.
You enable the following Group Policy setting to enable slow link detection for roaming profiles:Computer Configuration\Administrative Templates\System\User Profiles\Slow network connection timeout for user profiles
You configure the Connection speed option and the Time option in the Group Policy setting.
You log on to the client computer from a remote site by using a network connection. The network connection has a fast link speed to the profile server and has high network latency.

Note: The high network latency causes the download speed on the computer to be slow.

In this scenario, the time that is required for you to log on to the computer is longer than expected.

Note: This issue also occurs when you do not enable the Slow network connection timeout for user profiles Group Policy setting. When you do not enable the Group Policy setting, the computer uses the default settings for the Connection speed option and for the Time option.

Cause:
This issue occurs because the computer ignores the Time option and therefore does not consider network latency. When the client computer detects that the link speed is fast, the computer assumes that the network connection is fast. Then, the client computer starts to download the roaming profile, and you experience a slow logon process.

Download Hotfix:
You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles

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

-Article ID: 2820927 - Last Review: January 6, 2014 - Revision: 3.0
Currently available hotfixes for Folder Redirected Windows 7 SP1 clients

Summary:
This article lists the hotfixes that are currently available for Windows 7 clients that are used in a Active Directory environment that makes use of data centralization, including folder redirection, offline files and file server access.

In specific the components of relevance here are:
- CSC (Client Side Caching, Offline Files)
- DFSC (Distributed File System client)
- Shell
- Folder Redirection
- Group Policy Preferences

Introduction:
This article contains lists of Microsoft Knowledge Base articles that describe the currently available fixes. Each section is divided into subsections for different component drivers:
DFS Namespace, Offline Files, Shell, Folder Redirection and Group Policy Preferrences.

DFSN client component:
http://support.microsoft.com/kb/2820...rss&spid=14019