Because of the way that the Windows Installer update works, each update returns the registry changes in the original .NET Framework 2.0 Setup. Therefore, the value of the registry key is set to 1, similar to the .NET Framework Setup. This behavior may then overwrite any user-configured value for this key. For example, if you set the value of this registry key to 0 for a case sensitive file system, and you install an update for the .NET Framework 2.0 that was released before November 27, 2006, the value of this registry key will be set to 1 after the update is installed. The result is a case insensitive file system.
Note This problem does not occur in updates for the .NET Framework 2.0 that were released after November 27, 2006.
Note If you reinstall the .NET Framework 2.0 or you repair or reinstall any .NET Framework 2.0 updates that were released before November 27, 2006, you will have to apply the manual workaround again.
Article ID: 929110 - Last Review: Jul 16, 2008 - Revision: 1