List of Available Hotfixes for Windows 7

NoN · Jan 3, 2014

See also post #161

-Article ID: 2524249 - Last Review: August 10, 2011 - Revision: 2.0
Video capture and playback stop, or most video frames are dropped, when you connect an IEEE 1394 digital video camera to a computer that is running Windows 7 or Windows Server 2008 R2 .
Is superseded by: Article ID: 2707135 - Last Review: June 14, 2012 - Revision: 3.0
An IEEE 1394 isochronous device does not function in Windows 7 SP1 or in Windows Server 2008 R2 SP1.

-Article ID: 2577550 - Last Review: August 10, 2011 - Revision: 1.0
You may wait for up to 30 seconds when you use a smart card to unlock a computer that is running Windows 7 or Windows Server 2008 R2

-Article ID: 2480641 - Last Review: August 31, 2011 - Revision: 3.0
XPS Viewer does not handle permissions for a group named "Anyone" correctly in Windows 7 or in Windows Server 2008 R2.

Added to [PART ONE] #176

-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

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

-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

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

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

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

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

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

-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

Added to [PART TWO] #177

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

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

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

-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

-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

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

-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

Added to [PART THREE] #178

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

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

-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

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

-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

-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

-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

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

Added to [PART FOUR] #179

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

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

-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

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

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

Added to [PART FIVE] #182

-Article ID: 2872543 - Last Review: September 10, 2013 - Revision: 1.0
FIX: A paged pool memory leak occurs on a touch screen device that is running Windows 7 Service Pack 1

-Article ID: 2886127 - Last Review: November 25, 2013 - Revision: 5.0
DLNA CTT test case 7.4.27.4 failure when you use the CTT to test a device in Windows.

-Article ID: 2877999 - Last Review: November 27, 2013 - Revision: 2.0
FIX: Stop Error 0x50 in Windows 7 or Windows Server 2008 R2.

-Article ID: 2899749 - Last Review: December 24, 2013 - Revision: 2.0
New parameter is added to Msra.exe in Windows 7 SP1 and Windows Server 2008 R2 SP1

-Article ID: 2877211 - Last Review: December 26, 2013 - Revision: 4.0
Performance Monitor uses incorrect calculation for certain types of counters in Windows 8, Windows Server 2012, Windows 7 SP1, or Windows Server 2008 R2 SP1

NoN · Jan 3, 2014

I do try to give the most apply-able hotfixes for end-users, here. There are some of those hotfixes you could find around that i had to skip as they do are for Enterprise/Server/IIS...some for Windows 7 Ultimate and some to special configurations.

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

-Article ID: 2653385 - Last Review: January 4, 2013 - Revision: 2.0
Selected subfolder is highlighted unexpectedly when you select the parent folder in Windows 7 or in Windows Server 2008 R2.
:warn: Is superseded by (no matter the date of the article ID, date of the file & version are newer, might be an edited date Kb article):
-Article ID: 2754035 - Last Review: October 11, 2012 - Revision: 2.0
You cannot disable drag-and-drop operations on the Start menu by configuring a registry key in Windows 7 SP1 or a Windows Server 2008 R2 SP1.

Symptoms:
Assume that you disable the drag-and-drop operation on the Start menu on a computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1. To do this, you use one of the following methods:

You set the NoChangeStartMenu DWORD registry key to 1 in the following path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\
You configure the "Remove drag-and-drop and context menus on the Start menu" policy.

However, after you restart the computer, you can still right-click to perform the drag-and-drop operation on the All Programs pane of the Start menu.

Review & request Hotfix:
http://support.microsoft.com/kb/2754035/en-us

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

-Article ID: 2858684 - Last Review: July 10, 2013 - Revision: 1.0
Not all results are returned by file content search from Windows Explorer in Windows 7 SP1 and Windows Server 2008 R2 SP1

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You have the Always search file names and contents (this might take several minutes) option selected under the Search tab in the Folder Options dialog box.
You search for file content in a nonindexed location by using the search box in Windows Explorer.

In this scenario, some files that contain the search content may not be displayed in the search result.

For example, the text "string" is present in some files named text1.txt and text2.txt. Both of the text files are present in the same nonindexed folder. When you search for "string" from the search box in Windows Explorer in the folder, only the text1.txt file is displayed in the search result.

Review & request Hotfix:
http://support.microsoft.com/kb/2858684/en-us?sd=rss&spid=14019

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

-Article ID: 2736469 - Last Review: August 16, 2013 - Revision: 3.0
Memory leak occurs when you run an application to read a file on a DVD-RAM disc that uses the FAT32 file system in Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012.

Symptoms:
Assume that a 4 gigabyte (GB) file is stored on a DVD-RAM disc that uses the FAT32 file system. When you run an application to read the file on a computer that is running Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012, a memory leak occurs, and the computer stops responding. In some cases, the computer crashes.

Note When you burn a DVD disc on a Windows XP-based computer, the disc is formatted to use the FAT32 file system.

Review & request Hotfix:
http://support.microsoft.com/kb/2736469/en-us

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

-Article ID: 2872543 - Last Review: September 10, 2013 - Revision: 1.0
FIX: A paged pool memory leak occurs on a touch screen device that is running Windows 7 Service Pack 1.

Symptoms:
Consider the following scenario:

You have a Windows 7 Service Pack 1-based device that uses a touch screen monitor.
You start Internet Explorer, and then you open any webpage.
You select a text string on the webpage by double-clicking or touching the text string.
You keep the text string in the selected state.

In this scenario, a page pool leak occurs. Additionally, page pool memory allocation errors occur and the device stops responding (hangs).

Cause:
This problem occurs because of a leak in the pool memory that is used by advanced local procedure call (ALPC) messages between the Tiptsf.dll and Tipskins.dll files.

Review & request Hotfix:
http://support.microsoft.com/kb/2872543/en-us

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

-Article ID: 2845626 - Last Review: October 9, 2013 - Revision: 2.0
Cached credentials are not updated when you change your password in Windows.

Symptoms:
Consider the following scenario:

In an Active Directory domain environment, you have a user account.
The user principal name (UPN) of the account differs from the Security Accounts Manager (SAM) name of the account. For example, the UPN of the account resembles "[email protected]," and the SAM name of the account resembles "domain\username2."
The credentials are cached on a client computer that is running Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
You always log on to the client computer by using the UPN method.
You change the password of the user account by using the client computer. For example, you press Ctrl+Alt+Del and then click Change Password.

In this scenario, your credentials that are cached in the Local Security Authentication Server (Lsass.exe) process are not updated.

Note You are prompted to enter credentials to continue accessing network resources because of this problem.

Cause:
This problem occurs because the Kerberos.dll file tries to compare the password change in the UPN user name format and in the SAM user name format in the Kerberos logon session. Because the UPN and the SAM name are different in this case, the credentials in the Lsass.exe process are not updated.

Review & request Hotfix:
http://support.microsoft.com/kb/2845626/en-us

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

-Article ID: 2878035 - Last Review: October 9, 2013 - Revision: 1.0
FIX: Original files that are burned to a DVD-RW by using IMAPIv2.0 cannot be changed in Windows 7

Symptoms:
When you burn data in multisession mode to a DVD-RW by using the Image Mastering API v2.0 (IMAPIv2.0) on a computer that is running Windows 7, the original files that are burned cannot be changed. This is true even though the writing process is complete and all IMAPIv2 objects are released.

Cause:
This problem occurs because of a handle leak in IMAPIv2 when a multisession writing session occurs for DVD-RW media.

Review & request Hotfix:
http://support.microsoft.com/kb/2878035/en-us?sd=rss&spid=14019

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

-Article ID: 2892678 - Last Review: October 31, 2013 - Revision: 1.0
Logon screen, shutdown screen, and lock screen are not displayed in full-screen mode after you change the screen resolution to 3200 × 1800 in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Assume that you change the screen resolution to 3200 × 1800 on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. After you restart the computer, the logon screen, shutdown screen, and lock screen are not displayed in full-screen mode.

Cause:
This issue occurs because 2560 × 1600 is the maximum screen resolution that you can use to view the logon screen, shutdown screen, and lock screen in full-screen mode.

Review & request Hotfix:
http://support.microsoft.com/kb/2892678/en-us?sd=rss&spid=14019

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

-Article ID: 2882780 - Last Review: November 13, 2013 - Revision: 3.0
Incorrect UI color rendering when an application uses the D3D11CreateDevice or D3D10CreateDevice function in Windows.

Symptoms:
Assume that you have a computer that is running Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. When you run an application that uses the D3D11CreateDevice function or the D3D10CreateDevice function, the user interface (UI) color of the application is rendered incorrectly.

Cause:
This issue occurs because D3D10.1 is incorrectly exposed on feature level 10.0.

Review & request Hotfix:
http://support.microsoft.com/kb/2882780/en-us?sd=rss&spid=14019

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

-Article ID: 2898202 - Last Review: November 13, 2013 - Revision: 1.0
FIX: Font smoothing and antialiasing for some fonts do not occur after hotfix 2670838 is installed in Windows 7 Service Pack 1 or Windows Server 2008 R2.

Symptoms:
You have a computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2. After you apply hotfix 2670838, font smoothing and antialiasing are not performed on some system fonts that are included in Windows.

Cause:
This problem occurs because of an issue in the XPS to GDI Converter (XpsGdiConverter.dll) when different types of font face names are compared.

Review & request Hotfix:
http://support.microsoft.com/kb/2898202/en-us

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

-Article ID: 2886127 - Last Review: November 25, 2013 - Revision: 5.0
DLNA CTT test case 7.4.27.4 failure when you use the CTT to test a device in Windows.

Symptoms:
Assume that you have a device that requires the Digital Living Network Alliance (DLNA) certification. When you use the DLNA Conformance Test Tool (CTT) to test the device on a computer that is running Windows 7 Service Pack 1 (SP1), Windows Storage Server 2008 R2 Essentials, or Windows Home Server 2011, the test fails for the DLNA CTT test case 7.4.27.4. Additionally, the failure prevents the device from achieving the DLNA certification.

Review & request Hotfix:
http://support.microsoft.com/kb/2886127/en-us

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

-Article ID: 2877999 - Last Review: November 27, 2013 - Revision: 2.0
FIX: Stop Error 0x50 in Windows 7 or Windows Server 2008 R2.

Symptoms:
A computer that is running Windows 7 or Windows Server 2008 R2 may not resume from sleep. Additionally, you receive Stop error 0x50.

Cause:
This problem occurs because of a race condition in which an access controller is freed in a thread by the HdAudBusRemoveDevice function although the access controller is still being used by the HdAudBusChildPowerUp function in another thread.

Review & request Hotfix:
http://support.microsoft.com/kb/2877999/en-us

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

:warn:-Article ID: 2908190 - Last Review: December 17, 2013 - Revision: 3.0
Stop error 0x50 in the Win32k.sys driver after you install a font update.
Is Superseded by January 14, 2014 Windows Update Security bulletin: MS14-003

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

-Article ID: 2899749 - Last Review: December 24, 2013 - Revision: 2.0
New parameter is added to Msra.exe in Windows 7 SP1 and Windows Server 2008 R2 SP1

Introduction:
After you install this update, a new parameter will be added to the Remote Assistance Command Line tool (Msra.exe) in Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1:

Code:

msra /offerra computernamesessioninformation

The format of the session information parameter should be "username:sessionid."

For example, you can use the parameter as follows:

Code:

msra /offerra computernamedomain\username:sessionid

With this new parameter, you can specify user session information alongside the computer name when you offer remote assistance. If the specified session information matches any of the user sessions on the computer, a Remote Assistance connection is sent to that session. If no matching user session is found, you are prompted to select the user session that you want to connect to.

Review & request Hotfix:
http://support.microsoft.com/kb/2899749/en-us

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

-Article ID: 2877211 - Last Review: December 26, 2013 - Revision: 4.0
Performance Monitor uses incorrect calculation for certain types of counters in Windows 8, Windows Server 2012, Windows 7 SP1, or Windows Server 2008 R2 SP1

Symptoms:
When you use Performance Monitor to view Windows binary performance log files (.blg) in Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1, the average value for certain counter types is computed and displayed incorrectly.

Note The following counters are the most frequently used counters that are affected by this issue. This issue also occurs with Network and Memory performance counters.

\LogicalDisk\Avg. Disk sec/Write
\LogicalDisk\Avg. Disk sec/Read
\LogicalDisk\Avg. Disk sec/Transfer
\PhysicalDisk\Avg. Disk sec/Write
\PhysicalDisk\Avg. Disk sec/Read
\PhysicalDisk\Avg. Disk sec/Transfer

Review & request Hotfix:
http://support.microsoft.com/kb/2877211/en-us

NoN · Jan 6, 2014

-Article ID: 2796764 - Last Review: March 13, 2013 - Revision: 1.0
The "New" option in the shortcut menu is missing for the root folder of a redirected drive in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

On a client computer, you open Remote Desktop Connection and enable drive redirection.
You create a Remote Desktop session to a computer that is running Windows 7 or Windows Server 2008 R2.
You browse to the root folder of the redirected drive in the Remote Desktop session.
You right-click an active region to display the shortcut menu.

In this scenario, the New option is missing on the shortcut menu.

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

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

I'm curious what the next patch Tuesday will bring along those hot-fix patches.

Does some might superseded some of them?

If no, here we still have a Windows 7 SP2 sliced!!! :what:

:roflmao:

PS:
Nearly all those Hotfixes don't superseded others Fixes that came along the automated Windows Update.
They do renew and fix Windows 7 & Windows 7 SP1 files in System32/SysWOW64 & Drivers folders, aswell update the registry according to their descriptions.

I have check & compare every files (date & versions) that was on my PC system OS before putting them here just to be sure they do not replace older files but patched ones already.

I'm end-user Windows 7 SP1 Pro install with retail version so i shouldn't be much different from your day-to-day versions. Unless you have Enterprise & some ServerIIS Editions and Ultimate (for those having AppLocker/Bitlocker, BranchCache) some files might be not be needed.

Check the "Applies To" section for your edition in each Article ID.

If some of the files have been replaced from WU, it is very very few of them by a newer version & a newer date and not by a newer version & older date.

I've been the guinea pig for a week, the time to install and test those Hotfixes.

Not to say to you it is safe install, but i didn't bump onto fatal errors or BSOD whatsoever. My Events Viewer shows the usual errors ID.

Cheers, NoN!

NoN · Jan 7, 2014

Those are quite common BSOD code in Windows 7, so might catch your attention.

-Article ID: 2719704 - Last Review: May 24, 2013 - Revision: 2.0
"0x0000003B" or "0x000000D5" Stop error in Windows 7 or in Windows Server 2008 R2

Symptoms:
A computer that is running Windows 7 or Windows Server 2008 R2 crashes intermittently. Additionally, the user receives a Stop error message that resembles one of the following:

Code:

STOP: 0x0000003B (0000000080000003, [I]parameter2[/I], [I]parameter3[/I], 0000000000000000)

Code:

STOP: 0x000000D5 ([I]parameter1[/I], [I]parameter2[/I], [I]parameter3[/I], [I]parameter4[/I])

Notes

The use receives the "0x0000003B" Stop error when the Driver Verifier utility is disabled by default on the computer.
The user receives the "0x000000D5" Stop error when the Driver Verifier utility is enabled on the computer.
The "0x0000003B" Stop error describes a SYSTEM_SERVICE_EXCEPTION issue.
The "0x000000D5" Stop error describes a DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL issue.
The parameters in these error messages vary, depending on the configuration of the computer.
Not all "0x0000003B" and "0x000000D5" Stop errors are caused by this issue.

Cause:
This issue occurs because Rdpdr.sys tries to reference memory that is no longer available.

Review & request Hotfix:
http://support.microsoft.com/kb/2719704/en-us

----------------------------------------------------------------------------------------------------------
:info::ar:-Article ID: 2901005 - Last Review: October 23, 2013 - Revision: 1.0
Windows may crash on boot if asynchronous boot is enabled on some hardware.

Symptoms:

Consider the following scenario:

You have a system running Windows 7 SP1.
Windows is installed onto an SSD drive.
The external display is attached via DVI-D.
A USB keyboard and mouse are attached to the system.
The system is running with asynchronous boot enabled.

In this scenario, the system may crash on boot with a 0x3b error.

Resolution:

Disable asynchronous boot through the registry by creating the following registry key:

Click Start, click Run, type regedit in the Open box, and then click OK.
Browse to this path HKEY_LOCAL_MACHINE\SYSTEM\System\CurrentControlSet\Control\Pnp (if not already there).
Create a registry key named BootOptions of REG_DWORD type and set its value to 0.

Review Article ID:
Windows may crash on boot if asynchronous boot is enabled on some hardware

Blog Technet:
Group Policy and Logon Impact

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

Note: This article ID 2870102 is related to DirectX Graphics Kernel & DirectX Graphics MMS.

-Article ID: 2870102 - Last Review: October 9, 2013 - Revision: 1.0
FIX: Stop Error 0x0000000A and automatic restart in Windows 7 or Windows Server 2008 R2.

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

Code:

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

After you receive this Stop error message, the computer restarts automatically.

Note: Not all 0x0000000A Stop errors are caused by this problem.

Cause:
This problem occurs because of a race condition that occurs in the Dxgmms1.sys module. When the race condition occurs, the module tries to access an object that is already freed. Therefore, the module accesses an invalid memory address.

Review & request Hotfix:
FIX: Stop Error 0x0000000A and automatic restart in Windows 7 or Windows Server 2008 R2

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

:warn: NOTE: I could tell that this article ID 2885978 is superseded by January 14, 2014 Windows Update security bulletin: Article ID: 2913431, Update fixes an issue that causes Windows to crash
But the Smb driver (mrxsmb.sys) still remains patched in article ID 2885978.

-Article ID: 2885978 - Last Review: October 16, 2013 - Revision: 1.0
0x0000007F Stop error on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer.

Symptoms:
A computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 crashes. Additionally, you receive a Stop error message that resembles the following:

Code:

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

Notes

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

Cause:
This issue is caused by stack exhaustion that occurs when the computer sends and receives Transmission Control Protocol (TCP) or Server Message Block (SMB) data. Stack exhaustion occurs because the thread on which the TCP and SMB data is received and sent does not have sufficient stack space to complete the call.

Review & request Hotfix:
0x0000007F Stop error on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer

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

I also dug this one out! My Core i5 3rd Gen is a Stepping of family 6, part of Intel Xeon!

:ar:-Article ID: 2493989 - Last Review: August 19, 2011 - Revision: 1.0
Microcode update for Intel processors in Windows 7 or in Windows Server 2008 R2.

Introduction:

This article describes a microcode update for Intel processors. This update improves the reliability of x64-based versions of Windows that uses certain Intel processors. This update fixes an issue in which the operating system might function incorrectly. These issues are not common. These issues might affect processors that meet all the following conditions:

Designated as a Intel Xeon or Intel Core family processor that is based on the "Penryn" or "Merom" codenamed processors.
Has the Family, Model, and Stepping of family designations of 6, or a Model designation of 15, of 22, of 23, or of 29.

HOTFIX:
http://support.microsoft.com/kb/2493989/en-us

NoN · Jan 9, 2014

The Article ID: 2703902 is coming as a complementary fix to the Article ID: 2653030:

-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. #176
----------------------------------------------

-Article ID: 2703902 - Last Review: July 12, 2012 - Revision: 2.0
FIX: Windows Media Player stops playing .wav files before the end in Windows 7

Symptoms:
When you play a .wav file in Windows Media Player on a computer that is running Windows 7, the playback stops several seconds before the end of the .wav file.

Note This issue does not occur in a previous Windows operating system, such as Windows XP and Windows Vista.

Cause:
This issue occurs is caused by a design change in Windows 7. The Media Foundation (MF) source is used for parsing the .wav files in Windows 7. However, some issue occurs during the data chunk length computation for specific .wav files in the MF source.

Review & request hotfix:
FIX: Windows Media Player stops playing .wav files before the end in Windows 7

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

This is an update rollup feature for compatibility between Windows 7 & Windows 8 and will update only the necessary files on your based system.

:info::ar:-Article ID: 2760730 - Last Review: December 11, 2012 - Revision: 1.0
(Revised only. Date, package & files are remaining the same)
-Article ID: 2760730 - Last Review: January 29, 2014 - Revision: 2.0
Description of an update rollup that resolves interoperation issues in Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1.

Introduction:
This article introduces an update rollup that resolves interoperation issues between a computer that is running Windows 8 or Windows Server 2012 and a computer that is running Windows Vista Service Pack 2 (SP2), Windows Server 2008 SP2, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1.

After you install this update rollup, a computer that is running Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, or Windows Server 2008 R2 SP1 can interoperate with a computer that is running Windows 8 or Windows Server 2012.

More info about hotfixes rolled-up:
http://support.microsoft.com/kb/2760730/en-us

To apply this update, you must be running one of the following operating systems:

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

How to obtain this update:

Microsoft Update Catalog: Windows Update Catalog
(Type in search bar: 2760730)

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

-Article ID: 2807971 - Last Review: March 13, 2013 - Revision: 1.0
Internet Explorer takes a long time to open an HTTPS webpage in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:
Consider the following scenario:

You insert a smart card into a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
The Smart Card certificate is then propagated to the personal certificate store of the local computer.
You open a Secure Sockets Layer (SSL) website by using Windows Internet Explorer 8 or Windows Internet Explorer 9 in protected mode.

In this scenario, Internet Explorer takes about 30 seconds to load the webpage.

Note This issue occurs when any process runs in protected mode.

Cause:
This issue occurs because of incorrect logic that is used to handle an AccessDenied error.

Note The AccessDenied error occurs because the chain-building process only has read access in protected mode, and therefore cannot write various hash values in the certificate store. Additionally, the AccessDenied error triggers retry logic that results in a nonfatal error, and also adds an additional 6.6 seconds of processing time per certificate.

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

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

NoN · Jan 11, 2014

Do yourself a favor...Just don't give-up!
There's plenty of these for your best !

Hotfixes available is the last part for years 2012-2013, so here's: [PART SIX]

-Article ID: 2519922 - Last Review: February 16, 2012 - Revision: 2.0
The WUDFUsbccidDriver.dll driver crashes when you use a fingerprint reader for Windows logon or for some WBF-based applications 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 a fingerprint reader for Windows logon or for a Windows Biometric Framework (WBF)-based application.

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

Issue 1:
You connect the fingerprint reader to the computer and then install the WBF driver for the device. When you start the Biometric Devices control panel and then insert the fingerprint reader to enroll a fingerprint template finger for the logon functionality by using WBF, the WUDFUsbccidDriver.dll driver crashes. Additionally, the Biometric Devices control panel shows that the device is not available.

Issue 2:
When you retract and then insert the fingerprint reader while the fingerprint reader is capturing an image, the WUDFUsbccidDriver.dll driver crashes. Therefore, the WBF-based application cannot use the fingerprint reader. Additionally, depending on the application implementation, you may receive several error messages.

Note: This driver is also valid for the Generic USB 2.0-CRW Card reader.

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

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

-Article ID: 2674913 - Last Review: March 14, 2012 - Revision: 1.1
IPMI subsystem cannot obtain power information when the BMC interrupt is enabled on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Symptoms:
Assume that you try to use an application to obtain power information from a computer that has the baseboard management controller (BMC) interrupt enabled. The application uses the satellite management controllers in the Intelligent Platform Management Interface (IPMI) subsystem to connect to the BMC. In this situation, the application cannot obtain power information.

This issue occurs on a computer that is running one of the following operating systems:

Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2

Review & request hotfix:
IPMI subsystem cannot obtain power information when the BMC interrupt is enabled on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

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

-Article ID: 2699780 - Last Review: May 9, 2012 - Revision: 1.0
Memory leak in the Remote Registry service on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you query performance counters on a remote computer by using an application on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the memory usage of the Remote Registry service on the local computer increases until the available memory is exhausted.

Notes

The Remote Registry service runs in a Svchost.exe process. To identify this Svchost.exe process, open a command prompt, type the following command, and then press Enter: tasklist -svc

If you use Performance Monitor when this issue occurs, you notice that the memory used by the Svchost.exe process increases continuously.

Cause: This issue occurs because mutex objects and query handles are not closed.
Workaround: To work around this issue, restart the Remote Registry service.

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

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

-Article ID: 2797789 - Last Review: May 24, 2013 - Revision: 2.0
You cannot overwrite an exported event log file by using the Wevtutil.exe tool in Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7, Windows Server 2008 R2, Windows 8, or Windows Server 2012.
You use the WevtUtil.exe tool to export Windows event log files on the computer. For example, you run the following command to export the System log to an output file that is named as Systemexport.evtx on drive C:wevtutil epl system C:\systemexport.evtx
You run the wevtutil command together with the /ow:true switch to overwrite the file. For example, you run the following command to overwrite the Systemexport.evtx file: wevtutil epl system C:\systemexport.evtx /ow:true

In this scenario, the event log is incorrectly appended to the output file.

Note The expected result is that the output file is overwritten.

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

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

-Article ID: 2639043 - Last Review: June 18, 2012 - Revision: 4.0
A robocopy command updates DACLs incorrectly in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Assume that you use the following robocopy command to perform file replication on a computer that is running Windows 7 or Windows Server 2008 R2:
robocopy <Source> <Destination> /sec /mir
However, the Discretionary Access Control Lists (DACLs) for the files are updated incorrectly. This issue occurs even if the DACLs in the source location and in the destination location are the same.

Note When this issue occurs in a network environment that uses the Distributed File System Replication (DFSR) service, a very large DFS replication backlog is generated.

Review & request hotfix:
http://support.microsoft.com/kb/2639043/en-us?sd=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:
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

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

-Article ID: 2724133 - Last Review: October 10, 2012 - Revision: 2.0
Improvements are available for the Windows Security dialog box that is displayed when you open an encrypted email message in Windows 7 or in Windows Server 2008 R2.

Introduction:

This article describes an update that improves the default settings of the Windows Security dialog box. This dialog box appears when you open an encrypted email message by using Microsoft Outlook on a computer that is running Windows 7 or Windows Server 2008 R2. After you install this update, the following behavior is improved:

When you open an encrypted email message, the default setting for the Cryptographic Key access permission in the Windows Security dialog box is set to "Grant."
After you grant the Cryptographic Key access permission, the focus switches to the Password box by default.

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

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

-Article ID: 2627273 - Last Review: January 9, 2013 - Revision: 3.0
RSA key length is increased to 2048 bits for AD RMS in Windows 7 or in Windows Server 2008 R2.

Introduction:
This article introduces a hotfix that increases the length of RSA keys for Active Directory Rights Management Services (AD RMS) to 2048 bits on a computer that is running Windows 7 or Windows Server 2008 R2. Currently, AD RMS uses RSA keys that are 1024 bits long for encryption. Additionally, the hashing algorithm is updated from SHA-1 to SHA-256.

Review & request hotfix:
http://support.microsoft.com/kb/2627273/en-us?sd=rss&spid=14019

-----------------------------------------------------------------------------------------------------------
-Article ID: 2588507 - Last Review: August 13, 2012 - Revision: 3.0
Error messages when a 32-bit application has the /LARGEADDRESSAWARE option enabled in a 64-bit version of Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Symptoms:
Assume that you are running a 32-bit application that has the /LARGEADDRESSAWARE option enabled on a computer that is running a 64-bit version of Windows. Then, the application calls various network-related APIs such as GetHostByAddress() or GetAdaptersAddresses(). In this situation, you may receive an error message that resembles one of the following:

Code:

WSANO_DATA

Code:

ERROR_NO_DATA (232)

Code:

ERROR_NOACCESS (998)

This issue occurs on 64-bit versions of the following operating systems:

Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2

Note This issue occurs if the application experiences high memory usage.

Cause:
This issue occurs because of a problem with address-conversion routines. The 32-bit application passes a user-mode memory buffer that is allocated beyond the standard 2-gigabyte (GB) memory address space by using a network-related API such as GetHostByAddress() or GetHostByName(). The address is then converted from a 32-bit address to a 64-bit address in kernel routines. The address-conversion routines incorrectly sign-extend the particular address to convert it into a 64-bit address. This 64-bit address is outside the scope of the user-mode address pool. Therefore, the kernel denies read or write access to the address and returns an error to the application.

After you install the hotfix, the conversion routines correctly convert a 32-bit address that is supplied by the user application to an equivalent 64-bit address without sign-extension.

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

-----------------------------------------------------------------------------------------------------------------
-Article ID: 2866086 - Last Review: August 13, 2013 - Revision: 1.0
A user profile folder is unexpectedly re-created after you delete the profile in Windows 7 SP1.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1).
The computer is running the Windows Search service and has the Input Personalization interfaces enabled.
You delete a user profile on the computer.
You restart the computer or restart the Windows Search service.

In this scenario, the user profile folder is unexpectedly re-created in the following path:

C:\Users\username\AppData\Local\Microsoft\InputPersonalization\TextHarvester\TextHarvester.dat

Note The TextHarvester.dat file that is created is part of the Input Personalization system that adapts the language model and dictionary to a particular user, based on the user's usage. This usage information is primarily obtained through the search indexer.

This problem occurs because the presence of the user profile is not checked before the Textharvester.dat file is created.

Notes: The IPSPlugin.dll file caches the text-harvested data for each user in a corresponding TextHarvester.dat file.
This hotfix does not remove the re-created user profile folders. After you apply this hotfix, you have to delete the re-created user profile folders manually. This is a one-time action.

Applies to: Windows 7 Service Pack 1, when used with: Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate

Review & request hotfix:
http://support.microsoft.com/kb/2866086/en-us?sd=rss&spid=14019

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

-Article ID: 2870467 - Last Review: November 12, 2013 - Revision: 2.0
Memory leak in Oleaut32.dll on a Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8, or Windows Server 2012-based COM server.

Symptoms:

Consider the following scenario:

You have an out-of-proc COM server that is running Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1, Windows 8, or Windows Server 2012.
You run an application that is based on Microsoft COM technology on a client computer.
The application makes a COM call to the COM server. The client computer uses an interface to pass a SAFEARRAY user-defined data type to the COM server.

In this scenario, a memory leak occurs in Oleaut32.dll on the COM server.

Cause:
This issue occurs because Oleaut32.dll does not work correctly when the system frees allocated memory.

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

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

-Article ID: 2885974 - Last Review: November 13, 2013 - Revision: 4.0
FIX: More than 1,000 rules in the NRPT causes no rules to be loaded into memory in Windows.

Summary:
On a computer that is running Windows 7, Windows Server 2008 R2, Windows 8 or Windows Server 2012, there is a limit of 1,000 rules in the Name Resolution Policy Table (NRPT) that the DNS Client service can use. However, this limit is not enforced when you add a rule. Instead, no rules are loaded into memory when this limit is exceeded.

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

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

-Article ID: 2905216 - Last Review: December 12, 2013 - Revision: 1.0
FTP transfer rate is displayed incorrectly in an output file in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You have a computer that's running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
You redirect the displayed content of an FTP website to an output file.

In this scenario, the output that includes the transfer rate is displayed incorrectly.

For example, you expect the output to be displayed as follows:

ftp: 291 bytes received in 0.00 Seconds 291000.00Kbytes/sec
However, the actual output resembles the following:

ftp: 291 bytes received in Seconds Kbytes/sec.
ftp> 0.00291000.00get testsize.txt
Additionally, when you output the same content at the console, it is displayed correctly.

Cause:
This problem occurs because Windows uses an incorrect print function to print the information.

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

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

-Article ID: 2896820 - Last Review: December 24, 2013 - Revision: 2.0
Application that calls the GetFinalPathNameByHandle function crashes on Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You have an application that runs on a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 Service Pack 1 (SP1)-based computer.
The application calls the GetFinalPathNameByHandle function to retrieve the final path for a specific file.
The name of the file changes while the GetFinalPathNameByHandle function is executing.

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

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

THAT'S IT ! :devil2:

NoN · Jan 11, 2014

Those two Ones are special Ones, because they do add functionalities to the TCPIP Command "netsh interface tcp show global". I suggest you to test those and see if it doesn't drop your bandwidth connection or improve it.

Wanna looks like the latest OS?

Install:

1) -Article ID: 2780879 - Last Review: August 16, 2013 - Revision: 2.0
Hotfix improves TCP window scaling in Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Introduction:

This article describes a hotfix that improves the TCP window scaling feature on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. After you install the hotfix, additional netsh commands are available on the computer. You can run the following commands to enable or disable TCP window scaling after the second retransmission of a SYN packet in a TCP connection:

To enable TCP window scaling after the second retransmission of a SYN packet: netsh int tcp set heuristics enabled enabled
or
netsh int tcp set heuristics wsh=enabled forcews=enabled
To disable TCP window scaling after the second retransmission of a SYN packet: netsh int tcp set heuristics enabled disabled
or
netsh int tcp set heuristics wsh=enabled forcews=disabled

Note By default, the TCP window scaling feature is disabled after the second retransmission of a SYN packet in a three-way handshake in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

Review & request hotfix:
Hotfix improves TCP window scaling in Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

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

2) -Article ID: 2786464 - Last Review: September 12, 2013 - Revision: 2.0
Hotfix enables the configuration of the TCP maximum SYN retransmission amount in Windows 7 or Windows Server 2008 R2.

Introduction:

This article introduces a hotfix that re-enables the configuration of the number of TCP maximum SYN retransmissions on a computer that is running Windows 7 or Windows Server 2008 R2. After you install the hotfix, the following actions are possible:

You can configure the TCP maximum SYN retransmission value by running the following netsh command as administrator:netsh interface tcp set global MaxSynRetransmissions=number

Notes
- The minimum SYN retransmission value is 2, and the maximum value is 8.
- You do not have to restart the computer after you run the command.
You can query the TCP maximum SYN retransmission value by running the netsh interface tcp show global command. The result resembles the following:

TCP Global Parameters:
Receive-Side Scaling State enabled
Chimney Offload State automatic
NetDMA State enabled
Direct Cache Acess (DCA) disabled
Receive Window Auto-Tuning Level normal
Add-On Congestion Control Provider none
ECN Capability disabled
Max SYN Retransmissions 2

Notes: In Windows 7 and Windows Server 2008 R2, the TCP maximum SYN retransmission value is set to 2, and is not configurable. Because of the 3-second limit of the initial time-out value, the TCP three-way handshake is limited to a 21-second timeframe (3 seconds + 2*3 seconds + 4*3 seconds = 21 seconds).

On a computer that is running a Windows operating system earlier than Windows Vista or Windows Server 2008, you can configure the TCP maximum SYN retransmission value by changing the TcpMaxConnectRetransmissions registry entry that is located under the following registry subkey:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Note: The TcpMaxConnectRetransmissions registry entry is not available in Windows Vista, Windows Server 2008, Windows 7 , Windows Server 2008 R2, or any later version of Windows.

Review & request hotfix:
Hotfix enables the configuration of the TCP maximum SYN retransmission amount in Windows 7 or Windows Server 2008 R2

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

:warn:Note: If you ever troubleshooting the "Netsh" Command and above commands doesn't work there's a Hotfix available also applying to Windows 7:

3) -Article ID: 2472264 - Last Review: July 22, 2011 - Revision: 3.0
You cannot customize some TCP configurations by using the netsh command in Windows Server 2008 R2.

Symptoms:
You cannot configure some Transmission Control Protocol (TCP) configurations in Windows Server 2008 R2. These settings are important to optimize network latency in a dedicated data center network that is large-scale.

To apply this hotfix, you must be running one of the following operating systems:

Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)

And so Windows 7 in the requested package!

Review resolution chapter & request hotfix:
http://support.microsoft.com/kb/2472264

After those three Hotfixes the result should display ( :warn:Those are default parameters for Windows7):

"netsh interface tcp show global"

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : automatic
NetDMA State : enabled
Direct Cache Access (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 3000
Receive Segment Coalescing State : disabled
Max SYN Retransmissions 2

Note: You can also tune the Initial RTO value to your need with the netsh command:

"netsh int tcp set global initialrto={yourvalue}" (500 to default=3000)

NoN · Jan 15, 2014

So It's time for 2014....!

Amazing hotfix related to USB drivers again, all USB drivers similar to January 14, 2014 patch Tuesday: MS13-81

I haven't install yet this Hotfix that does superseded MS13-081 kb article.

The good?...its part for Windows XP just before its ending soon.

:warn: -Article ID: 2828030 - Last Review: January 15, 2014 - Revision: 2.0
USB audio devices stop streaming audio on a computer that is running Windows 7 SP1, Windows Server 2008 R2 SP1 or Windows XP SP3.

Symptoms:
Consider the following scenario:

Some USB Universal Host Controller Interface (UHCI) audio devices are connected to a computer that is running Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1 or Windows XP Service Pack 3 (SP3).
You start an application that sends and captures audio streams for the audio devices on the computer.
The application continues to run on the computer for about 49 days and 17 hours.

In this situation, the audio devices stop streaming the audio.

Note If you reset the USB audio devices, this issue is resolved temporarily.

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

Note: You must have the Article ID: 2533552 - Last Review: April 16, 2013 - Revision: 5.0 installed before on your Windows 7 to perform this update.

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

-Article ID: 2914748 - Last Review: January 15, 2014 - Revision: 1.0
Task Scheduler task fails if running at the same time as the DiskPart command.

Symptoms:
Assume that you have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. A batch file is setting up a task in Task Scheduler. Meanwhile, another batch file is running the DiskPart command. In this situation, the task and the DiskPart command fail intermittently, and you receive the following error message:

The requested operation was made in the context of a transaction that is no longer active.

Additionally, an event that resembles the following is logged in the event log:
Source: Microsoft-Windows-Kernel-Tm
Event ID: 1
Level: Warning
Description:
The Transaction (UOW={9b6c2628-49cd-11e2-b2d0-00155d45d86e}, Description='a.txt') was unable to be committed, and instead rolled back; this was due to an error message returned by CLFS while attempting to write a Prepare or Commit record for the Transaction.
The CLFS error returned was: 0xc01a002f.

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

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

This one also superseded January 14, 2014 patch Tuesday: Article ID: 2913431 - Last Review: January 14, 2014 - Revision: 1.1, so it will be wise to review carefully if its need to be patched.

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

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)

Notes

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

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.

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

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

NoN · Jan 17, 2014

-Article ID: 2914680 - Last Review: January 15, 2014 - Revision: 2.0
I/O delays in Windows 7 SP1 or Windows Server 2008 R2 SP1.

Symptoms:

Consider the following scenario:

You have a computer that running Windows 7 SP1 or Windows Server 2008 R2 SP1.
This computer is used to provide file service, and multiple volumes are used for the file share.
The disk is under a heavy load.

In this situation, there is a delay when creating or opening I/O request packets (IRPs).

Cause:
This issue occurs because resource contentions of NTFS volumes are locked.

Review & request hotfix:
I/O delays in Windows 7 SP1 or Windows Server 2008 R2 SP1

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

-Article ID: 2639077 - Last Review: January 15, 2014 - Revision: 3.0
Handle leak in Svchost.exe when a WMI query is triggered by using the Win32_PowerSettingCapabilities class in Windows 7 or in Windows Server 2008 R2

Symptoms:
Assume that a Windows Management Instrumentation (WMI) query is executed to determine the power settings of a computer that is running Windows 7 or Windows Server 2008 R2. The query is triggered by using the Win32_PowerSettingCapabilities class. In this situation, the handle count of the Svchost.exe process that hosts the power service increases. Additionally, when the handle count reaches the maximum number of handles that a process can have, no services that share this process open handles to any object.

Cause:
This issue occurs because the handles to the power policy registry keys that are opened by the power service (Umpo.dll) are not closed correctly. This behavior causes the handle leak.

Review & request hotfix:
Handle leak in Svchost.exe when a WMI query is triggered by using the Win32_PowerSettingCapabilities class in Windows 7 or in Windows Server 2008 R2

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

-Article ID: 2912821 - Last Review: January 15, 2014 - Revision: 1.0
The "w32tm /monitor" command output cannot be redirected to a file correctly in Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you have a domain member computer that is running Windows 7 or Windows Server 2008 R2. You run a variation of the following command from a command prompt to monitor the Windows Time service on the computer and collect the output in a file:

w32tm /monitor > result.txt

In this situation, the localized lines of the command prompt output are not redirected to the file correctly.

After you apply the hotfix, you have to open the redirected file by using Wordpad.exe instead of Notepad.exe to view newline characters correctly.

Note: redirected file result.txt will drop in C:\Windows\System32.

Review & request hotfix:
The "w32tm /monitor" command output cannot be redirected to a file correctly in Windows 7 or Windows Server 2008 R2

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

-Article ID: 2905407 - Last Review: January 15, 2014 - Revision: 2.0
Stop error 0xD1 when you download uTorrent content through an RNDIS 6.0 connection.

Symptoms:

Consider the following scenario:

You have the uTorrent client (or other high speed file transfer applications) installed on a computer that's running one of the following operating systems:
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
- Windows 8
- Windows Server 2012
You use an RNDIS USB device which implements the Remote Network Driver Interface Specification (RNDIS) 6.0 driver version.

When you download uTorrent content through the RNDIS 6.0 connection in this scenario, you receive Stop error 0xD1

Cause:
This problem occurs because of an issue in the Microsoft RNDIS 6.0 driver

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

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

-Article ID: 2896146 - Last Review: January 15, 2014 - Revision: 3.0
Packet loss occurs when MTU is below 576 and PMTU discovery is enabled in Windows.

Symptoms:
Consider the following scenarios:

The computers in a network environment run Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows RT 8.1.
Path MTU (PMTU) discovery (EnablePMTUDiscovery) is enabled on the computers.
The network environment is slow. Therefore, in order to increase the throughput, the MTU is required to be set to a value that is less than 576.

In this situation, the MTU is not set to less than 576 correctly. Therefore, data packets are dropped, and packet loss occurs during data transmission. This makes the network unreliable.

Cause:
This issue occurs because PMTU discovery does not allow an MTU value that is less than 576. Therefore, data packets are fragmented excessively.

Review and request hotfix:
http://support.microsoft.com/kb/2896146/en-us

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

NoN · Jan 17, 2014

Just a Note from me for those requesting those Hotfixes to Microsoft.

I try my best to describe the superseded article IDs that are renewed and the complementary ones that does not need to uninstall previous Kb Article(s). And optional ones.

I mean, when i do tell those are superseded, i have uninstall the previous article ID for the new one, and checked after if i can install the older one, and if not, i do conclude it is superseded by the newer as i got also a pop-up windows telling "This update is not for your computer" for the older one.

It is a long process... That's the only way i have to know what's the difference between one and one, as the files are the same.

Note that also, some are re-released Article ID and you'll be able to recognize them with the added extension v2, v3 or v4 before the .exe...

Another exemple are those Kbs that are apply-able all the three of them (corrected in post #176):

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

I thought first they were superseded because shared almost the same files. They do are complementary ones.

Cheers NoN!

NoN · Jan 24, 2014

This Article ID: 2820833 is more of an enforcement of NTFS file permissions over removable devices and other removable media.

This article ID provide Step-by-Step solutions and "Microsoft Fix-it" solutions for those wanted disallow read and write access to removable devices.

-Article ID: 2820833 - Last Review: May 17, 2013 - Revision: 2.0
NTFS disk access permissions for removable or external media could be bypassed.

Introduction:
We are aware of detailed information and tools that can be used to access files on removable devices. These tools can bypass NTFS file permissions on non-server distributions of Microsoft Windows. We are aware that this issue may affect internal disks, fixed disks that are marked as removable, and also external media such as USB, Firewire, E-SATA, SD, and other removable media. We are aware of situations in which disks on certain storage controllers may be marked as "removable" regardless of physical position inside or outside the computer case or the kind of connection that is used by the disk.

This issue does not affect the primary system volume (that is, the device from which Windows is currently running).

Systems that are affected in a default configuration are primarily at risk. For example, this includes systems multiple disks that are running Windows Vista, Windows 7 and Windows 8.

More Infos:
How to tell if your environment is affected
NTFS disk access permissions for removable or external media could be bypassed

NoN · Jan 26, 2014

You'll find here a list of re-released article IDs due to an issue in which the digital signature by Microsoft will expire prematurely.

NOTE:
Some of the Article IDs posted above are already re-released ones as they are tagged v2 or v3 when you do requesting them, thus it will make you be able to recognize more easily the version!

-Article ID: 2771149 - Last Review: March 15, 2013 - Revision: 6.0
List of Windows hotfixes that are affected by signed Microsoft binaries.

Summary:
This article lists the Windows hotfixes that were re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory (2749655)

Applies to:
Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008

More information about the hotfixes re-released:
List of Windows hotfixes that are affected by signed Microsoft binaries

Note: Some of the article IDs mentioned in that list do not appeared posted along this thread by me.

NoN · Feb 11, 2014

-Article ID: 2808693 - Last Review: February 10, 2014 - Revision: 8.0
Hotfix is available that disables the function that lets users change the format of a physical smart card PIN or a VSC PIN in Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012.

Introduction:
This article describes a hotfix that disables the function that lets users change the format of a Virtual Smart Card (VSC) personal identification number (PIN) by using the CTRL+ALT+DEL sequence. After you apply this hotfix, you can enable and disable this function.

By design, a VSC PIN must have a minimum of 8 digits and can contain any combination of numbers and characters. For example, Pin1234! and 12345678 are valid VSC PINs. Physical smart cards may not have this limitation.

For VSCs, you cannot use a mechanism that is built into Windows to apply a policy that enforces a specific PIN format (such as a 10 digit PIN that contains only numbers). However, for both VSCs and physical smart cards, you can enforce a PIN format by using other methods. For example, you can use a custom PIN tool to enforce the PIN format. To make sure that users do not change a specified PIN format, disable the function that lets users change the PIN format.
Prerequisites:

To apply this hotfix, you must be running running one of the following operating systems:

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

Registry information:
How to back up and restore the registry in Windows 322756

After you apply this hotfix, follow these steps to enable or disable the function that lets users change the smart card PIN:

Start Registry Editor. To do this, press the Windows logo key+R, type regedit, and then click OK.
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\
On the Edit menu, point to New, and then click Key.
Type SmartCardCredentialProvider, and then press Enter.
On the Edit menu, point to New, and then click DWORD Value.
Perform one of the following actions, based on the kind of smart card on which you want to restrict functionality:
- For VSCs, type AllowVirtualSmartCardPinChangeAndUnlock, and then click Modify.
- For physical smart cards, type AllowSmartCardPinChangeAndUnlock, and then click Modify.
Type 1 in the value data box, and then click OK.

Note If you set either the AllowVirtualSmartCardPinChangeAndUnlock or AllowSmartCardPinChangeAndUnlock value to 1, users can change the format of the PIN. If you set the value to 0, users cannot change the format of the PIN.
On the Edit menu, point to New, and then click REG_SZ or REG_EXPAND_SZ Value.
Perform one of the following actions, based on the kind of smart card on which you want to restrict functionality:
- For VSCs, type VirtualSmartCardPinChangeAndUnlockString, and then click Modify.
- For physical smart cards, type SmartCardPinChangeAndUnlockString, and then click Modify.
You can use the VirtualSmartCardPinChangeAndUnlockString and SmartCardPinChangeAndUnlockString registry values to display information on the user's computer. Type any information that you want to provide to the user, and then click OK.
Exit Registry Editor.

You can set the VirtualSmartCardPinChangeAndUnlockString or SmartCardPinChangeAndUnblockString registry entry value to REG_SZorREG_EXPAND_SZ. If you want the text on the Secure Desktop screen to contain carriage returns, follow these steps to change the binary data of the registry entry:

Set the VirtualSmartCardPinChangeAndUnlockString or SmartCardPinChangeAndUnblockString registry entry value to REG_EXPAND_SZ, and then input the text that you want to display to users.
Right-click the registry entry that you set in step 1, and then click Modify binary data....
Add "0D 00 0A 00" in each location that you want a line break to appear.

Note You can use Group Policy to set the registry entry to REG_EXPAND_SZ for a string that does not contain line breaks in the binary data. However, if you want the string to contain line breaks, edit the string, export the "0D 00 0A 00" values as an .REG file, and then deploy the .REG file. To do this, use Group Policy to run a startup, shutdown, logon, and logoff script.

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

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

-Article ID: 2923388 - Last Review: February 12, 2014 - Revision: 1.0
Plain text displayed when XSLT style sheet used to transform an XML document into HTML in Windows 7 or Windows Server 2008 R2.

Symptoms:

Consider the following scenario:

You have a computer that runs Windows 7 or Windows Server 2008 R2.
You use an XSLT style sheet to transform an XML document into HTML.
Your browser, such as Internet Explorer, uses xmllite.dll to transform XML documents.

In this scenario, the XML document transformation fails intermittently and plain text is displayed within the browser.

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

NoN · Feb 12, 2014

Here we can find three Hotfixes that all sharing to the same files and same "DTS Time Changeover & Software Products " problems and have to be installed one by one by order given or picked-up to suit the needs of the Operating System. The files will be recorded in the C:\Windows\winsxs and will let appear the last hotfix updates given.

I recon it's a little tricky to have three hotfixes sharing the same files in two days time!!

1) -Article ID: 2800213 - Last Review: February 11, 2014 - Revision: 3.0
High CPU usage during DST changeover in Windows Server 2008, Windows 7, or Windows Server 2008 R2.

Symptoms:
Consider the following scenarios:

Scenario 1

You have a computer that is running Windows Server 2008, Windows 7, or Windows Server 2008 R2.
You configure the complementary metal-oxide semiconductor (CMOS) clock according to Coordinated Universal Time (UTC).
You configure a DWORD type registry key named RealTimeIsUniversal in the following path, and set the value to 1:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation
The CMOS clock does not match the Windows clock.
The computer starts the daylight saving time (DST) changeover.

In this scenario, the computer uses 100 percent of CPU resources. The CPU usage remains at 100 percent until both the CMOS clock and the Windows clock pass the DST changeover time.

Scenario 2

You deploy a Hyper-V virtual machine that is running Windows Server 2008, Windows 7, or Windows Server 2008 R2.
The clock on the host server that runs the virtual machine is set to the UTC time zone.
You change the time zone of the Windows clock on the virtual machine to a local time zone.
After you restart the virtual machine, the Windows clock on the virtual machine does not reflect the local time zone, and is instead set to the UTC time zone.
You configure a DWORD type registry key named RealTimeIsUniversal in the following path on the virtual machine, and set the value to 1:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation
The CMOS clock does not match the Windows clock.
The virtual machine and the host server start the DST changeover.

In this scenario, the virtual machine uses 100 percent of CPU resources. The CPU usage remains at 100 percent until both the clock on the host computer and the Windows clock on the virtual machine pass the DST changeover time.

Cause:
This issue occurs because the hardware abstraction layer (HAL) uses the CMOS clock time incorrectly, and this causes a conflict. This behavior occurs when the RealTimeIsUniversal registry key is configured.

Review the Resolution:
High CPU usage during DST changeover in Windows Server 2008, Windows 7, or Windows Server 2008 R2

2) -Article ID: 2922223 - Last Review: February 11, 2014 - Revision: 2.0
You cannot change system time if RealTimeIsUniversal registry entry is enabled in Windows.

Symptoms:

Consider the following scenario:

You have a computer that is running Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1, or Windows Embedded Standard 7 SP1.
You configure the complementary metal-oxide semiconductor (CMOS) clock.
You apply a DWORD type registry key that is named RealTimeIsUniversal in the following path and set the value to 1: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation
You try to change the system time through Control Panel in Windows.

In this scenario, the time cannot be changed. Additionally, the time is changed back to the CMOS clock.

Note You can change the CMOS clock through the BIOS.

See section "Applies to" for your proper operating system.

Resolution: The following files are available for download from the Microsoft Download Center:

You cannot change system time if RealTimeIsUniversal registry entry is enabled in Windows

3) -Article ID: 2922790 - Last Review: February 12, 2014 - Revision: 1.0
Some software products function incorrectly in Windows 7 and Windows Server 2008 R2.

Symptoms:
When you have more than seven software products installed that use the PsSetLoadImageNotifyRoutine API in Windows 7 and Windows Server 2008 R2, some products cannot register for notifications and do not function correctly.

Cause:
This issue occurs because the operating system has a limit of 8 registrations. One is used by the operating system, leaving 7 for other software products.

Resolution:
This hotfix increases the limit to 64 registrations.

Workaround:
To work around this issue, you can uninstall some third-party software products.

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

NoN · Feb 12, 2014

This is another exemple of two Hotfixes sharing same drivers files, posted the same day.
So, according to their descriptions adapt to your needs the one suits you the best as they might superseded by drivers version and date.

1) -Article ID: 2907020 - Last Review: February 12, 2014 - Revision: 1.0
"Location is not available" error when you access a mapped network drive after Windows standby or resume.

Symptoms:
Consider the following scenario:

You have a Windows 7 or Windows Server 2008 R2 computer that supports the sleep and resume functionality and joined to a domain.
You access a mapped network drive from Explorer on a Windows 7 or Windows Server 2008 R2 computer.
You put the computer to sleep and wake the computer again after some time.

In this situation, you cannot access the mapped network drive for a short time. Additionally, you receive the following error message:

Location is not available.

Can't Access x:\

The specified network name is no longer available.

Cause:
This issue occurs because the Server Message Block (SMB) session is deleted on the server-side.

Review & request hotfix:
"Location is not available" error when you access a mapped network drive after Windows standby or resume

2) -Article ID: 2923398 - Last Review: February 12, 2014 - Revision: 1.0
A Remote Desktop session may stop responding when you access a remote shared folder by using SMB version 2.

Symptoms:
Consider the following scenario:

You have a server that is running Windows Server 2008 R2 Service Pack 1.
You start a Remote Desktop session from a client computer to the server.
Then, you access a remote shared folder by using the Server Message Block (SMB) version 2 protocol from the Remote Desktop session.

In this scenario, if the network between the server and the remote share is not stable, the Remote Desktop session may randomly stop responding.

Note This problem may also randomly occur when you access a file share by using SMB version 2 over a high latency network.

Cause:
This problem occurs because the SMB version 2 disconnect is handled incorrectly.

Applies to

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

Review & request hotfix:
A Remote Desktop session may stop responding when you access a remote shared folder by using SMB version 2

NoN · Feb 14, 2014

-Article ID: 2921916 - Last Review: February 11, 2014 - Revision: 1.0
The "Untrusted publisher" dialog box appears when you install a driver in Windows 7 or Windows Server 2008 R2.

Symptoms:
Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You install a driver that is signed by an SHA256, SHA384, or SHA512 certificate, and the "Untrusted publisher" dialog box appears.
You click to select the Always trust check box and then click OK.
You uninstall the driver.
You install the same driver again.

In this scenario, the "Untrusted publisher" dialog box appears even though you already set the Always trust option to always trust the publisher.

Review & request hotfix:
The "Untrusted publisher" dialog box appears when you install a driver in Windows 7 or Windows Server 2008 R2

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

-Article ID: 2920289 - Last Review: February 12, 2014 - Revision: 2.0
A Stop Error occurs on a computer that has IPSec configured in Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1.

Symptoms:
You configure Internet Protocol Security (Ipsec) on a computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1. When you start the computer, you experience a Stop error when IpSec rules are applied for the first time.

Cause:
This problem occurs because of a race condition in the TCP/IP driver.

Review & request hotfix:
A Stop Error occurs on a computer that has IPSec configured in Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1

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

-Article ID: 2924171 - Last Review: February 12, 2014 - Revision: 1.0
Resource Monitor (Perfmon /res) crashes in Windows 7 and in Windows Server 2008 R2.

Symptoms:
If you use Windows Task Manager or the Perfmon /res command to start Resource Monitor on a computer that is running Windows 7 or Windows Server 2008 R2, the Perfmon.exe process crashes. Additionally, you receive an error message that resembles the following:

Code:

Faulting application name: perfmon.exe, version: 6.1.7601.17514, time stamp: 0x4ce7972c
Faulting module name: wdc.dll, version: 6.1.7601.21854, time stamp: 0x4eb38833 
Exception code: 0xc0000005 
Fault offset: 0x0000000000061a1c 
Faulting process id: 0x548 
Faulting application start time: 0x01ceb90f1d977b61 
Faulting application path: C:\Windows\System32\perfmon.exe 
Faulting module path: C:\Windows\System32\wdc.dll 
Report Id: 63bef6f4-2502-11e3-bfa7-d89d671f169f

Cause:
This problem occurs because of a race condition in the WDC.dll module.

Review & request hotfix:
Resource Monitor (Perfmon /res) crashes in Windows 7 and in Windows Server 2008 R2

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

-Article ID: 2922059 - Last Review: February 13, 2014 - Revision: 2.0
A Windows 7-based tablet that uses the Intel Atom processor may stop responding for two minutes

Symptoms:
You have a tablet that uses the fourth-generation Intel Atom processor, that is running Windows 7, and that has an HDMI monitor connected to a dock. If you undock the tablet while it is in the sleep state and then resume the tablet from sleep, the tablet may not respond to Plug & Play or power requests for up to two minutes. For example, there may be a delay before Windows detects USB devices that are plugged in or a delay in putting the tablet back into the sleep state.

Cause:
This problem occurs because of an issue between Windows Power Manager and an audio device.

Review & request hotfix:
A Windows 7-based tablet that uses the Intel Atom processor may stop responding for two minutes

NoN · Feb 16, 2014

For those that have installed kb2592687: "Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1".

Please, refer to this post: #170

-Article ID: 2908518 - Last Review: February 13, 2014 - Revision: 1.0
Svchost.exe crashes after you install the RDP 8.0 update in Windows 7.

Symptoms:

Issue 1
Assume that you install the Remote Desktop Protocol (RDP) 8.0 update on a computer that is running Windows 7 Service Pack 1 (SP1). You enable the RDP 8.0 Host by using the Local Group Policy Editor. In this situation, the Svchost.exe process crashes intermittently on the computer.

Issue 2
Consider the following scenario:

You install the RDP 8.0 update on a computer that is running Windows 7 SP1.
The computer is configured to allow remote desktop connections.
You run an application that uses Windows Terminal Server virtual channel APIs (such as the WtsVirtualChannelOpen and WtsVirtualChannelClose APIs) to create and use virtual channels in a Remote Desktop Protocol (RDP) session.

In this scenario, RDP static virtual channels do not work. Additionally, virtual channel communication fails in the RDP session if you do not reestablish the connection.

Notes

This issue does not affect other running RDP sessions.
This issue can appear in different ways. For example, when you schedule several print jobs in a Remote Desktop Protocol session, the print jobs are deleted.

Issue 3
Consider the following scenario:

You install the RDP 8.0 update on a computer that is running Windows 7 SP1.
You run an application that uses Windows Terminal Server virtual channel APIs (such as the WtsVirtualChannelOpen and WtsVirtualChannelClose APIs) to create and use virtual channels in an RDP session.
The application tries to open a static virtual channel by using a channel name that does not exist.

In this scenario, the operation that opens the static virtual channel stalls for 10 seconds when the system tries to open the nonexistent virtual channel again.

Review & request hotfix:
Svchost.exe crashes after you install the RDP 8.0 update in Windows 7

NoN · Feb 25, 2014

System Update Readiness Tool for Windows 7 x32bits & x64 bits (KB947821-v32) [February 2014]

Fix Windows Update corruption errors such as 0x80070002 and 0x80070057:
Windows Update corruption errors prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. If the error you see is in the following list, try the solution in this article.

0x80070002 | 0x8007000D | 0x800F081F | 0x80073712 | 0x800736CC | 0x800705B9 | 0x80070246 | 0x8007370D | 0x8007370B | 0x8007370A | 0x80070057 | 0x800B0100 | 0x80092003 | 0x800B0101 | 0x8007371B | 0x80070490

To resolve this problem, use the System Update Readiness tool. Then, install the Windows update or service pack again.
This tool is updated regularly, we recommend that you always download the latest version.

Article ID: 947821 (v32)
Last review: January 13, 2014
Applies to: Windows 8.1, Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, Windows Vista Service Pack 2, Windows Server 2008 Service Pack 2.

Download the appropriate package for your OS Based System:
Fix Windows Update corruption errors such as 0x80070002 and 0x80070057

NoN · Mar 11, 2014

-Article ID: 2928800 - Last Review: March 11, 2014 - Revision: 1.0
Incorrect group name is displayed in folder permission list in Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you rename a security group or a distribution group, and then grant permissions for the group to a folder by editing the Security tab of the folder properties. You log on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. In this situation, when you check the system access control list (SACL) in the Security tab of the folder properties, the group is displayed as Group Name (Domain Name\name), which is invalid. We expect that the group is Group Name (Domain Name\sAMAccountName).

Notes

name is a placeholder for the name attribute in the group properties.
sAMAccountName is a placeholder for the sAMAccountName attribute in the group properties.

Cause:
This issue occurs because incorrect name attribute is used instead of the sAMAccountName attribute in the SACL group display function.

Review & request hotfix:
Incorrect group name is displayed in folder permission list in Windows 7 or Windows Server 2008 R2

NoN · Mar 11, 2014

-Article ID: 2928562 - Last Review: March 11, 2014 - Revision: 1.0
Event 55 when you copy an encrypted folder to EFS shared folder in Windows.

Symptoms:
Assume that you enable Encryption File System (EFS) on a shared folder on a computer that is running Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. You copy an encrypted folder to the shared folder. In this situation, the copied folder in the shared folder is corrupted. Additionally, the following event is logged in the System log:
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:"

Note When this issue occurs, you cannot access the shared folder until you run the chkdsk.exe process.

Cause:
This issue occurs because the NTFS.sys file incorrectly encrypts some content.

Review & request hotfix:
Event 55 when you copy an encrypted folder to EFS shared folder in Windows

Note: Might superseded the kb article ID: 2914680
-Article ID: 2914680 - Last Review: January 15, 2014 - Revision: 2.0
I/O delays in Windows 7 SP1 or Windows Server 2008 R2 SP1 => see post #189

List of Available Hotfixes for Windows 7

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer