Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Hotfix rollup 3166738 for the .NET Framework 4.6 and 4.6.1 in Windows


View products that this article applies to.

This article describes hotfix rollup 3166738 for the Microsoft .NET Framework 4.6 and 4.6.1. For more information about the issues that the hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.

↑ Back to the top


Resolution

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

Download Download the x86 package now.

Download Download the x64 package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.


Note To verify the hotfix update version, check the value of the Release keyword to determine the installed version. To be forward-compatible, you can check for a value that's greater than or equal to the value that's listed in the following table.

Hotfix rollup version Value of the release DWORD
Hotfix rollup 3166738 for the .NET Framework 4.6 and later versions 394299
For more information about how to determine the .NET Framework versions, see How to: Determine which .NET Framework versions are installed.

↑ Back to the top


More Information

Prerequisites

To apply this hotfix, you must have the .NET Framework 4.6 or 4.6.1 installed.

Restart requirement

You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

This hotfix package doesn't replace a previously released hotfix package.

↑ Back to the top



Issues that this hotfix rollup fixes

Workflow issue  

If you're using the classes in System.Workflow.* and you're also using workflow tracking and have enabled FIPS compliance on the computer where the workflows are running, you must create the following AppSetting in the application's configuration file (or web.config for Workflow Services):
<add key="microsoft:WorkflowRuntime:FIPSRequired" value="true"/> 

↑ Back to the top


Keywords: kb, kbfix, kbsurveynew, kbexpertiseadvanced, atdownload

↑ Back to the top

Article Info
Article ID : 3166738
Revision : 1
Created on : 1/7/2017
Published on : 7/13/2016
Exists online : False
Views : 276