List of Available Hotfixes for Windows 7

[NoN]

Users will need to be running Windows 7 SP1 or Windows Server 2008 R2 SP1 in order to install those hotfixes.

-Article ID: 2619291 - Last Review: November 9, 2011 - Revision: 1.0
Thumbnails for TIFF files are slow to display in Windows Explorer on a Windows 7-based or Windows Server 2008 R2-based computer.

Symptoms:


Considering the following scenario:

• You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).
• You use Windows Explorer to visit a folder that contains TIFF image files.
• The TIFF image files are large, or are stored on a network share.

In this scenario, the thumbnails for the TIFF image files are slow to display.

Review and request the hotfix:
Thumbnails for TIFF files are slow to display in Windows Explorer on a Windows 7-based or Windows Server 2008 R2-based computer



-Article ID: 2584449 - Last Review: November 9, 2011 - Revision: 1.0
Print output is blank when you print text to a Generic/Text Only printer in Internet Explorer 9 on a computer that is running Windows 7 or Windows Server 2008 R2.

Symptoms:
Assume that you connect a Generic/Text Only printer to a computer that is running Windows 7 or Windows Server 2008 R2. When you try to use Windows Internet Explorer 9 on the computer to print text to the printer, the print output is blank.

Cause:
This issue occurs because the XPS-to-Graphics Device Interface (GDI) converter driver (Xpsgdiconverter.dll) cannot set custom fonts in the printer.

Review and request the hotfix:
Print output is blank when you print text to a Generic/Text Only printer in Internet Explorer 9 on a computer that is running Windows 7 or Windows Server 2008 R2

 

[NoN]

-Article ID: 2625845 - Last Review: November 9, 2011 - Revision: 1.0
List of currently available hotfixes for Windows Installer 4.5 and Windows Installer 5.0.

Summary:
This article lists the hotfixes that are currently available for users who use Windows Installer 4.5 and Windows Installer 5.0.

1. Windows Installer 4.5 is integrated in Windows Vista Service Pack 2 (SP2) and Windows Server 2008 SP2. The redistributable package is also available for the following operating systems:
   • Windows Server 2008 RTM
   • Windows Vista
   • Windows Vista Service Pack 1 (SP1)
   • Windows XP SP2
   • Windows XP Service Pack 3 (SP3)
   • Windows Server 2003 SP1
   • Windows Server 2003 SP2
   
   

2. Windows Installer 5.0 is included in Windows Server 2008 R2 and Windows 7.

More information:
List of currently available hotfixes for Windows Installer 4.5 and Windows Installer 5.0

 

[NoN]

-Article ID: 2633952 - Last Review: November 22, 2011 - Revision: 2.0
December 2011 cumulative time zone update for Windows operating systems.

Summary:
Important This update supersedes and replaces update 2570791, which was released in August 2011. No additional time zone changes were released as hotfixes after update 2570791 was published.

If you have already deployed update 2570791, read the descriptions of the specific time zone changes that are addressed in this article to determine whether you must deploy this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity.

We recommend that you deploy the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.



Important:

• Before you apply the update that is described in this article, be aware of potential issues that may affect Microsoft Outlook.

Appropriate package available for your "Operating System" HERE:
December 2011 cumulative time zone update for Windows operating systems

Release Date: November 22, 2011

Note:Update for Windows Server 2008 R2 for Itanium-based systems is not available at this time. The package will available on December 13, 2011.

 

[NoN]

Update 4.0.3 Beta for Microsoft .NET Framework 4 – Runtime Update (KB2599651)

This is Update 4.0.3 Beta for Microsoft .NET Framework 4 containing a set of new features addressing top customer feature requests and important .NET Framework scenarios.

Infos here:
Update 4.0.3 Beta for Microsoft .NET Framework 4

Direct Download MS Center:
Download: Update 4.0.3 Beta for Microsoft .NET Framework 4

 

[NoN]

-Article ID: 2640148 - Last Review: December 13, 2011 - Revision: 1.0
Windows Explorer stops responding if you try to expand a mapped drive in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Considering the following scenario:

• You have a mapped drive that connects to a shared network location on a computer that is running Windows 7 or Windows Server 2008 R2.
  
  Note The shared network location is indexed on the computer.
• You include the mapped drive in a library.
• You open Windows Explorer, and then expand Libraries in the navigation pane.
• The computer is disconnected from the network.
• You try to expand the mapped drive in the navigation pane.

In this scenario, Windows Explorer stops responding.

Note This issue also occurs if you try to expand an external drive (such as a USB drive or a DVD drive) that is either disconnected or no longer contains media.

Direct downloadable package Here:
Windows Explorer stops responding if you try to expand a mapped drive in Windows 7 or in Windows Server 2008 R2

 

[NoN]

Update for Windows 7 for x64 & x32-based Systems (KB2640696) v2.0

x32:Download: Update for Windows 7 (KB2640696) - Microsoft Download Center - Download Details

x64:Download: Update for Windows 7 for x64-based Systems (KB2640696) - Microsoft Download Center - Download Details

   Note

I'll post as soon as possible the infos for that KB2640696 v2.0 when MS Center will make it available.

____________________________________________________________________________

   Information

This one is a bit of Powershell cmds to apply to your needs, so read carefully before any actions! This package might not apply to some of you

HERE: http://support.microsoft.com/kb/2607047

-Article ID: 2607047 - Last Review: September 22, 2011 - Revision: 2.0
How to Determine the Minimum Staging Folder Quota that DFSR Needs for a Replicated Folder.

SUMMARY:
This article is a quick reference guide on how to calculate the minimum staging folder quota needed for DFSR to function properly. Values lower than these may cause replication to go slowly or stop altogether. Please note that these are only the minimums. When considering staging folder quota, the larger the staging folder size, up to the size of the Replicated Folder, is recommended.

How to Calculate the Minimum Staging Folder QuotaAt a minimum, the staging folder quota for servers running Windows Server 2008 R2 or Windows Server 2008 should be at least the size of the 32 largest files in the replicated folder, or the 16 largest files for read-only replicated folders. The minimum quota for staging folder quota must be equal to the 9 largest files in Windows Server 2003 R2.

To determine the 9 largest files in the replicated folder on Windows 2003 R2, use this Windows PowerShell command:

(get-childitem d:\docs -recurse | sort-object length -descending | select-object -first 9 | measure-object -property length -sum).sum /1gb

To determine the 32 largets files in the replicated folder on Windows 2008 and Windows 2008 R2 use this Windows PowerShell command:

(get-childitem d:\docs -recurse | sort-object length -descending | select-object -first 32 | measure-object -property length -sum).sum /1gb

Both the above Windows PowerShell cmdlets output the recommended minimum staging folder quota in GB units.

Package for x32:
Download: Update for Windows 7 (KB2607047) - Microsoft Download Center - Download Details

Package for x64:
Download: Update for Windows 7 for x64-based Systems (KB2607047) - Microsoft Download Center - Download Details

 

[NoN]

-Article ID: 2621146 - Last Review: December 13, 2011 - Revision: 1.0
MS11-095: Description of the security update for Active Directory: December 13, 2011.

From Security TechCenter:
Microsoft Security Bulletin MS11-095 - Important : Vulnerability in Active Directory Could Allow Remote Code Execution (2640045)

Infos:
MS11-095: Description of the security update for Active Directory: December 13, 2011

Direct downloadable package:
x64:
Download: Security Update for Windows 7 for x64-based Systems (KB2621146) - Microsoft Download Center - Download Details
x32:
http://www.microsoft.com/download/en/details.aspx?id=28430

 

[NoN]

Refering to this SevenForums thread: Microsoft Releases AMD Bulldozer-Boosting Hotfix

1)
-Article ID: 2645594 - Last Review: January 12, 2012 - Revision: 2.0
An update is available for computers that have an AMD FX, an AMD Opteron 4200, or an AMD Opteron 6200 series processor installed and that are running Windows 7 or Windows Server 2008 R2.

Introduction:

This article introduces an update for computers that are running Windows 7 or Windows Server 2008 R2 and that have a processor from one of the following series installed:

• AMD FX
• AMD Opteron 4200
• AMD Opteron 6200

Currently, the CPU scheduling techniques that are used by Windows 7 and Windows Server 2008 R2 are not optimized for the AMD Bulldozer module architecture. This architecture is found on AMD FX series, AMD Opteron 4200 Series, and AMD Opteron 6200 Series processors. Therefore, multithreaded workloads may not be optimally distributed on computers that have one of these processors installed in a lightly-threaded environment. This may result in decreased system performance for some applications.

Important: The power management policy for processor core parking on your computer may prevent this update from producing the desired performance increase. To disable core parking, install the hotfix that is described in Microsoft Knowledge Base (KB) article 2646060.

View & request hotfix:
An update is available for computers that have an AMD FX, an AMD Opteron 4200, or an AMD Opteron 6200 series processor installed and that are running Windows 7 or Windows Server 2008 R2


2)
-Article ID: 2646060 - Last Review: January 11, 2012 - Revision: 1.0
An update that selectively disables the Core Parking feature in Windows 7 or in Windows Server 2008 R2 is available.

Introduction:
This article introduces an update that enables the hotfix installer to selectively disable the Core Parking feature in Windows 7 or in Windows Server 2008 R2 if an AMD FX, AMD Opteron 4200 Series, or AMD Opteron 6200 Series processor is installed.

Currently, the CPU Power Policies that are used by Windows 7 and Windows Server 2008 R2 are not optimized for the dual core AMD Bulldozer module architecture. This architecture is found on AMD FX series, AMD Opteron 4200 Series, and AMD Opteron 6200 Series processors. This can result in decreased system performance with multithreaded workloads in lightly-threaded environments.

When this update is installed, Bulldozer modules will be less likely to achieve the C6 power state. This potentially results in increased power consumption in more lightly-threaded environments.

Important: If you apply this update, you cannot revert the settings by uninstalling this update. This update should only be installed on computers that have KB2645594 installed.

View & request hotfix:
An update that selectively disables the Core Parking feature in Windows 7 or in Windows Server 2008 R2 is available

 

[NoN]

-Article ID: 2649904 - Last Review: January 16, 2012 - Revision: 2.0
It takes a long time for Games Explorer to be displayed in Windows 7.

Symptoms:
Assume that you try to open Games Explorer on a computer that is running Windows 7. However, it takes a long time for Games Explorer to be displayed. This issue occurs if the value of the DevicePath registry entry under the following registry subkey includes locations that contain many device drivers:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Cause:
This issue occurs because of an error in the Windows System Assessment Tool (WinSAT). When you open Games Explorer, WinSAT displays the performance rating score of the computer in the Games Explorer window. WinSAT calculates the performance rating score by enumerating system devices. System devices are specified in the DevicePath entry. Therefore, if the value of the DevicePath entry includes locations that contain many device drivers, WinSAT takes a long time to calculate the performance rating score.

View & request hotfix:
It takes a long time for Games Explorer to be displayed in Windows 7

 

[NoN]

This one appears to be listed since January 23rd, 2012 on the MS Download Center but the article is from dec 2011.


-Article ID: 2624668 - Last Review: December 14, 2011 - Revision: 1.0
"STOP: 0x0000003B" error occurs during the shutdown process in Windows Server 2008 R2 or in Windows 7.

Symptoms:

Consider the following scenario:

• You create multiple virtual Wi-Fi adapters on a physical Wi-Fi adapter on computer that is running Windows Server 2008 R2 or Windows 7.
• You connect the physical Wi-Fi adapter to a network.
• You try to shut down the computer.

In this scenario, you receive the following Stop error message randomly:

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

Note This Stop error describes a SYSTEM_SERVICE_EXCEPTION issue.


Notes

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

Cause:
This issue occurs because of a synchronization problem in the Ndis.sys driver. Specifically, one thread is accessing a variable while another thread is deleting it at the same time. This behavior causes a thread to try to access a freed variable. When this occurs, the operating system triggers the Stop error that is mentioned in the Symptoms section.

Infos:
"STOP: 0x0000003B" error occurs during the shutdown process in Windows Server 2008 R2 or in Windows 7

Direct MS Center Downloadable package:

x32:
Download: Update for Windows 7 (KB2624668) - Microsoft Download Center - Download Details
x64:
Download: Update for Windows 7 for x64-based Systems (KB2624668) - Microsoft Download Center - Download Details




-Article ID: 2652531 - Last Review: January 26, 2012 - Revision: 2.0
FIX: Decreased performance when you load flow documents in a WPF application that targets the .NET Framework 4.

Symptoms:
If you load flow documents in a Windows Presentation Foundation (WPF) application that targets the Microsoft .NET Framework 4, decreased performance occurs compared to in a WPF application that targets the Microsoft .NET Framework 3.5.

Note The issue typically occurs when you load flow documents that contain many glyphs from a font file.

Cause:
This issue occurs because WPF relies on DirectWrite for processing flow documents. DirectWrite introduces a new behavior to mitigate problems when fonts are updated while an application is running. The new behavior causes relatively slow disk access when the last write time of the font file is being retrieved.

Direct MS Center Download:
Download: Hotfix for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server - Microsoft Download Center - Download Details

Don't forget to set back to manual the .NET Framework 2.0 in the services.msc.

 

[NoN]

-Article ID: 2657025 - Last Review: February 14, 2012 - Revision: 1.0
Update for 2011 calendar history in Windows operating systems.

Summary:


Previous cumulative time zone updates for Windows introduced a discrepancy in the 2011 calendar history of the following time zones:

• Samoa Standard Time
• Russian Standard Time
• Ekaterinburg Standard Time
• N. Central Asia Standard Time
• North Asia Standard Time
• North Asia East Standard Time
• Yakutsk Standard Time
• Vladivostok Standard Time
• Magadan Standard Time
• Kaliningrad Standard Time

This update fixes 2011 calendar history for these time zones.

The following files are available for download from the Microsoft Download Center (same link for all operating system):
Update for 2011 calendar history in Windows operating systems

 

[NoN]

-Article ID: 2640696 - Last Review: February 14, 2012 - Revision: 1.0
An ADO-based application that is compiled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 does not run in earlier versions of Windows.

Symptoms:
Assume that you develop an ActiveX Data Objects (ADO)-based data access application on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). However, the application does not run on a computer that is running an earlier version of Windows.


Notes

• ADO-based applications that are compiled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 use the new interface identifiers (IIDs) in the ADO type libraries that were included in the SP1 packages for Windows 7 and for Windows Server 2008 R2.
• This issue does not occur if the hotfix that is described in the following Microsoft Knowledge Base article is installed on the computer that is running an earlier version of Windows: 983246 "Type Mismatch" error message when you run a VBA macro in a 64-bit version of an Office 2010 application.

More infos:
Update information

Assume that you compile a VB6-based or VBA-based application that is compatible with versions of Windows that are earlier than Windows 7 SP1 and Windows Server 2008 R2 SP1. After you install this update, Visual Basic automatically displays the Microsoft ActiveX Data Objects 6.1 Library in the Available References list when you try to add references to the current project. To manually locate the ADO 6.0 type library (Msado60.tlb) in this situation, browse to the following location:
%program files%\common files\system\ado

Notes

• Visual Basic automatically displays the ADO 6.0 type library in the Available References list if the reference to the ADO 6.0 type library was added to current project.
• If you are a C++ developer and if you include the following line of code in the application, you must change the code when you recompile the application:

  #import msado15.dll

  
  You must change this code to the following:

  #import msado60.tlb

• If you are a C++, VB6, or .NET developer and if you apply "Method 1" in the "Workaround" section that is described in Microsoft Knowledge Base (KB) article 2517589, you do not have to change the code. However, we recommend that you install this update to make sure that the ADO interfaces on your computer are up to date. For more information about KB 2517589, click the following article number to view the article in the Microsoft Knowledge Base:2517589 (An ADO application does not run on down-level operating systems after you recompile it on a computer that is running Windows 7 SP 1 or Windows Server 2008 R2 SP 1 or that has KB983246 installed ) An ADO application does not run on down-level operating systems after you recompile it on a computer that is running Windows 7 SP 1 or Windows Server 2008 R2 SP 1 or that has KB983246 installed.

The following files are available for download from the Microsoft Download Center (same link):
An ADO-based application that is compiled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 does not run in earlier versions of Windows

 

[NoN]

-Article ID: 2639308 - Last Review: February 14, 2012 - Revision: 2.0
An update is available for the ASLR feature in Windows 7 or in Windows Server 2008 R2.

Summary:
This update introduces the Force ASLR feature, which is an addition to the Address Space Layout Randomization (ASLR) feature for Windows 7 or Windows Server 2008 R2. For more information about ASLR, visit the following Microsoft website:

General information about ASLR (Windows ISV Software Security Defenses)
Currently, ASLR is enabled only for executable images that are built by using a special linker flag. For more information about this special linker flag, visit the following Microsoft website:

General information about the /DYNAMICBASE linker flag (/DYNAMICBASE (Use address space layout randomization))
Executable images that do not specify this linker flag will generally load at their preferred base address.

This update provides support for the Force ASLR feature. This makes it possible for applications to forcibly relocate images that are not built with the /DYNAMICBASE linker flag. Applications can enable this feature by using new Image File Execution Options (IFEO). For more information about IFEO, visit the following Microsoft website:

General information about IFEO http://msdn.microsoft.com/en-us/library/windows/desktop/ff190925(v=vs.85).aspx


The following files are available for download from the Microsoft Download Center (same link):
An update is available for the ASLR feature in Windows 7 or in Windows Server 2008 R2

 

[NoN]

Hotfix for Microsoft .NET Framework 3.5.1 on Windows 7 RTM & Windows 7 Service Pack 1 and Windows Server 2008 R2 & Service Pack 1!

-Article ID: 2637518 - Last Review: February 20, 2012 - Revision: 2.0
FIX: WCF services that are hosted by NLB computers to route messages to Exchange Server fail when WebHeader settings are added by using a .NET Framework 3.5 SP1 application.

Symptoms:


Consider the following scenario:

• You use Network Load Balancing (NLB) to route messages for a set of computers that host Windows Communication Foundation (WCF) services.
• The services use secure sessions by setting the authenticationMode attribute to SecureConversation to communicate with Microsoft Exchange Server.
• You add WebHeader settings to messages in the application layer by using a Microsoft .NET Framework 3.5 SP1 application. After you do this, NLB should use the WebHeader settings to route messages.

In this scenario, WebHeader settings are not added to messages that are used to negotiate the session. Therefore, messages are routed to different host computers. In this situation, any cached session data in the host computer is unavailable, and the WCF services fail.

This fix is available for download from the Microsoft Download Center (same link):
FIX: WCF services that are hosted by NLB computers to route messages to Exchange Server fail when WebHeader settings are added by using a .NET Framework 3.5 SP1 application

 

[NoN]

New System Update Readiness Tool available!
This article is in fact dated/revised February 28, 2012 at MS download Center.

-Article ID: 947821 - Last Review: December 9, 2011 - Revision: 18.0
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2.

Introduction:
This article describes the System Update Readiness Tool for Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7.
You may become unable to install updates from Windows Update, due to inconsistencies in file data or registry data. By installing the System Update Readiness Tool, you can resolve these inconsistencies and you will be able to install updates from Windows Update. After the System Update Readiness Tool is installed, install updates again from Windows Update

All Infos and Package for your appropriate Operating System to download HERE:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

 

[NoN]

-Article ID: 2600211 - Last Review: March 6, 2012 - Revision: 2.0
Update 4.0.3 for Microsoft .NET Framework 4 – Runtime Update.

Introduction:
Update 4.0.3 for Microsoft .NET Framework 4 is now available. This update includes a set of new features and fixes some bugs, based on top customer requests and the .NET Framework scenarios.


Notes:

• This update release updates only the runtime files for the Microsoft .NET Framework 4. For more information about the details of this update, see the "More Information" section.
• This update contains all the runtime changes from the following updates:
  • 2544514 (http://support.microsoft.com/kb/2544514/ ) Update 4.0.2 for Microsoft .NET Framework 4 - Runtime Update
  • 2478063 (http://support.microsoft.com/kb/2478063/ ) Update 4.0.1 for Microsoft .NET Framework 4 - Runtime Update
  Therefore, this update is a cumulative update. Any application built for the .NET Framework 4.0.1 or the .NET Framework 4.0.2 can run on a computer that has the .NET Framework 4 and the .NET Framework 4.0.3 runtime installed.
• We do not support any application that this update was used to build on any prerelease version of the .NET Framework 4, such as a Beta. Additionally, we recommend that any such application be upgraded to at least the Microsoft .NET Framework 4 RTM.

Information & Download the package Here:
http://support.microsoft.com/?kbid=2600211

*****************************************************



-Article ID: 2647753 - Last Review: March 13, 2012 - Revision: 1.0
Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2.

Introduction:
Microsoft has released an update rollup for the printing core components that are included in Windows 7 and in Windows Server 2008 R2. This update is dated March 14, 2012. This article describes the following information about the update rollup:

• The issues that the update rollup resolves
• How to obtain the update rollup
• The prerequisites to install the update rollup

Direct Download the package x32 & x64 HERE:
Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2

 

[NoN]

-Article ID: 2675785 - Last Review: March 14, 2012 - Revision: 1.0
Data transfer speed is slow in Windows 7 or in Windows Server 2008 R2.

Symptoms:
In a high-bandwidth and low-latency network environment, the data transfer speed is slow. This issue occurs on a computer that is running Windows 7 or Windows Server 2008 R2.

Cause:
This issue occurs because TCP window scaling does not work when network latency is between 1 millisecond and 8 milliseconds.

View and request the hotfix:
Data transfer speed is slow in Windows 7 or in Windows Server 2008 R2

 

[NoN]

Enable Network Level Authentication (NLA)

This had been made on March 13, 2012.
Those are MS Fix-it Solutions to run on your computer or through the Group Policy.

Security Update MS12-020 addresses two vulnerabilities in Microsoft’s implementation of the Remote Desktop Protocol (RDP). One of the two, CVE-2012-0002, is a Critical, remote code execution vulnerability affecting all versions of Windows.

CVE-2012-0002: A closer look at MS12-020's critical issue - Security Research & Defense - Site Home - TechNet Blogs


You can read more about it, here [Issues - january 2012]:
Why Use Network Level Authentication?

 

[NoN]

System Update Readiness Tool [may 2012]

-Article ID: 947821 - Last Review: April 30, 2012 - Revision: 20.0
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2.

More infos & Download links Here:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2



-Article ID: 2698707 - Last Review: May 22, 2012 - Revision: 5.0
Morocco DST Update

Symptoms:
The government of Morocco has announced that the country will switch to daylight saving time (DST) every year from 2012 onwards. According to the new law, clocks in Morocco will be turned forward one hour on the last Sunday in April and turned back again on the last Sunday in September.

The legal time in Morocco will be advanced by 60 minutes on the last Sunday of April each year, at 2:00 A.M. Then, Morocco will return to standard time on the last Sunday of September each year at 3:00 A.M., with the exception of the holy month of Ramadan.

This year's switch from standard time to DST will occur in the early hours of April 29, 2012. Clocks will be turned from 2:00 A.M. (02:00) to 3:00 A.M. (03:00) local time. The end of the 2012 DST period occurs on September 30, when clocks will be turned back one hour from 3:00 A.M. (03:00) to 2:00 A.M. (02:00) local time.

No DST during Ramadan
According to the new law, the DST period will be interrupted during the Muslim month of Ramadan (July 20 to August 19, 2012 in the Gregorian calendar). For that period, clocks will be turned back to standard time. This interruption in the DST schedule is designed to shorten evenings, making it easier for Muslims to observe the Ramadan fast during hours of daylight.

"Fix it for me" or "Let me fix it myself" available Here:
Morocco DST Update

 

[NoN]

-Article ID: 2703157 - Last Review: June 12, 2012 - Revision: 1.0
You encounter a memory leak issue when an application calls the WinHttpGetProxyForUrl function in Windows 7 or in Windows Server 2008 R2.

Symptoms:
Assume that you develop an application that makes use of the WinHTTP Web Proxy Auto-Discovery Service (WinHttpAutoProxySvc) or calls the WinHttpGetProxyForUrl function. When you run this application on a computer that is running Windows 7 or Windows Server 2008 R2, you encounter a memory leak issue.

Note The memory leak issue is in the WinHTTP Web Proxy Auto-Discovery Service (WinHttpAutoProxySvc) host process. The issue occurs when the WinHttpGetProxyForUrl function is called. Therefore, the memory usage of the process increases every time that the WinHttpGetProxyForUrl function is called.

Cause:
This issue occurs because the cleanup code is not executed in DLL_PROCESS_DETACH when the Jscript.dll file is dynamically unloaded.

To resolve this issue, install one of the following updates, depending on your operating system:

Update for Windows 7 x32-based system: Download: Update for Windows 7 (KB2703157) - Microsoft Download Center - Download Details

Update for Windows 7 x64-based system: Download: Update for Windows 7 for x64-based Systems (KB2703157) - Microsoft Download Center - Download Details

Note:
Some of you might not be able to install this update due to its particular setting and/or might be already included in kb2699988.