MS09-061: Description of the security update for the Microsoft.NET Framework 1.1 Service Pack 1: October 13, 2009

Microsoft has released security bulletin MS09-061. To view the complete security bulletin, visit one of the following Microsoft Web sites:Home users:
( the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:
( professionals:
( to obtain help and support for this security update Help installing updates: Support for Microsoft Update
Security solutions for IT professionals: TechNet Security Troubleshooting and Support
Help protect your computer that is running Windows from viruses and malware:Virus Solution and Security Center
Local support according to your country: International Support

Prerequisites to install this security updateTo install this security update, you must have Microsoft Windows Installer 3.1 or a later version installed on the computer. To obtain the latest version of Windows Installer for the computer, visit the following Microsoft Web site:
( update replacement informationThis security update supersedes security updates 928366 and 929729 (security bulletin MS07-040). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
( of the security update for the .NET Framework 1.1 Service Pack 1 for Windows XP and Windows 2000: July 10, 2007
( of the security update for the .NET Framework 1.1 Service Pack 1 for Windows Vista and Windows Server 2008: July 10, 2007Update removal informationAfter you install this update, you can uninstall it by using the Add or Remove Programs item in Control Panel. Command-line switches for this updateYou can find information about the various command-line switches that this update supports in security bulletin MS09-061 and on the following MSDN Web site:
( more information about Windows Installer, visit the following MSDN Web site:
( issuesFor more information about installation issues with this update, click the following article numbers to view the articles in the Microsoft Knowledge Base:
( When you try to install an update for the .NET Framework 1.0, 1.1, 2.0, 3.0, or 3.5, you may receive Windows Update error code “0×643″ or Windows Installer error code “1603″
( The file version is rolled back to the version that was installed by the last service pack when you remove an update for the .NET Framework 1.0, the .NET Framework 1.1, Visual Studio .NET 2002 or Visual Studio .NET 2003
( Description of the Patch Registration Cleanup Tool

The performance of DFS Replication in Windows Server 2008 is slower than expected on a WAN connection, and no error message is logged in the DFS Replication log

In Windows Server 2008, the performance of Distributed File System (DFS) Replication for one or more replication groups is slower than expected. When you view the DFS Replication health report for these replication groups, or when you run the DFSRDIAG BACKLOG command against these replication groups, you notice that the number of backlog files continuously increases. Additionally, no error is logged in the DFS Replication log on the sending member.
This problem may occur for many reasons. For example, the wide area network (WAN) connection may be unstable. This problem is difficult to troubleshoot because the error condition is not logged in the DFS Replication log on the sending member.

Stop error when a registry management problem occurs on a Windows Server 2008 or Windows Vista SP1-based computer: “0x0000007E”

On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you receive the following Stop error message:

NotesThe first parameter is 0xc0000005. Other three parameters in this Stop error message may vary, depending on the configuration of the computer. Not all “0x0000007E” Stop error messages are caused by this problem. Additionally, the following event is logged in the System log:
Source: Microsoft-Windows-WER-SystemErrorReporting
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, <address>, <address>, <address>). A dump was saved in: <file path>.
This problem occurs because the registry management module does not manage mapped views in memory correctly. Therefore, a view is freed even though it is being mapped. Any access to this freed view will cause the system to trigger stop code 0x0000007E.

An error message occurs when you run “Sysprep /generalize” in Windows Vista or Windows 7: “A fatal error occurred while trying to Sysprep the machine”

When you try to run the System Preparation Tool (Sysprep) in Windows Vista or Windows 7, and you use theĀ /generalize option, you may receive the following error message:

A fatal error occurred while trying to Sysprep the machine.
The Setuperr.log file may contain lines that resemble the following:
Error [0x0f0082] SYSPRP LaunchDll: Failure occurred while executing ‘C:\Windows\System32\slc.dll, SLReArmWindows’, returned error code -1073425657
Error [0x0f0070] SYSPRP RunExternalDlls: An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657
Error [0x0f00a8] SYSPRP WinMain: Hit failure while processing sysprep generalize providers; hr = 0xc004d307
Note The Setuperr.log file is located in the \Windows\System32\Sysprep\Panther folder.
This error may occur if the Windows Software Licensing Rearm program has run more than three times in a single Windows image.

SQL Server Questions and Answers, SQL QA