Article ID: 2431806 - View products that this article applies to.
When you install certain updates for the .NET Framework 2.0 Service Pack 2, the .NET Framework 3.0 Service Pack 2, or the .NET Framework 3.5 Service Pack 1, the update may install successfully. However, files may not be updated. Therefore, the update may be reoffered on Windows Update.
This scenario may occur for several reasons that include certain installation failure issues that are related to dual branch servicing. Between January 2009 and July 2009, several hotfixes for the .NET Framework 2.0 Service Pack 2, the .NET Framework 3.0 Service Pack 2, and the .NET Framework 3.5 Service Pack 1 were released with a defect. When hotfixes that have this defect are installed, and then a security update is installed, the presence of the hotfix prevents the payload files in the security update from being updated correctly. In certain cases, this issue may also manifest itself in the form of the error that is described in the following Microsoft Knowledge Base article:
2262911Microsoft has removed all the hotfixes that included this defect and has replaced these with new hotfixes that do not have the defect. The Microsoft Knowledge Base articles for the defective hotfixes were updated, and they list the replacement hotfixes without the defect. If you have installed one of the defective hotfixes that are listed here, apply the workaround that is described in the "Workaround" section of this article to address the issue. If you do not apply the workaround, there is a possibility that the files in the payload for a security update may not be updated correctly, leaving the computer in an inconsistent and possibly vulnerable state.
(http://support.microsoft.com/kb/2262911/ )"Could not load type 'System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy'" exception error after you install update 982167 or update 982168
List of defective Hotfixes
For more information about dual branch servicing, click the following article number to view the article in the Microsoft Knowledge Base:
Collapse this tableExpand this table
(http://support.microsoft.com/kb/960043/ )Dual Branch Servicing for the .NET Framework 2.0 Service Pack 2, the .NET Framework 3.0 Service Pack 2, and the .NET Framework 3.5 Service Pack 1
To work around this problem, follow these steps.
Step 1Install hotfix 975954. To download the MSI updates, visit the following MSDN webpage:
Step 2Run a repair of the product. We can repair the product for you automatically, or you may repair the product yourself.
Run the repair for meTo run a repair of the product automatically, click the Fix it button. Then click Run in the File Downloaddialog box, and then follow the steps in the Fix it wizard.
Fix this problemNote This wizard is in English only. However, the automatic fix also works for other language versions of Windows.
Microsoft Fix it 50468
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or a CD so that you can run it on the computer that has the problem.
Let me repair it myselfTo repair the product yourself, type the following appropriate command lines from an elevated command prompt:
This resolves the issue that is caused by the bad baseliner and lets the update apply its payload successfully.
For more information about how to run a command that uses elevated permissions, visit the following Microsoft webpage:
Step3You may have to reinstall a hotfix that was updated and replaced as mentioned in the "Cause" section. To determine whether you have to reinstall such an updated hotfix, examine the "Hotfix replacement information" section in the Knowledge Base article for the hotfix that you installed.
For more information about the command-line switches that are supported by Windows Installer, visit the following MSDN webpage:
Command-Line OptionsFor more information about Windows Installer, visit the following MSDN webpage:
About Windows Installer
Article ID: 2431806 - Last Review: June 21, 2014 - Revision: 10.0
Contact us for more help