After you install a Microsoft .NET Framework 2.0 update, a file system's case sensitivity changes from case sensitive to case insensitive.
Consider the following scenario. You enable case sensitivity on a Microsoft Windows file system for Windows/UNIX interoperability. You install an update for the Microsoft .NET Framework 2.0, and then restart the computer. In this scenario, the file system is no longer case sensitive. Because the file system is no longer case sensitive, you may receive error messages in applications that depend on case sensitivity. Additionally, this may cause data loss because files are accidentally overwritten by the unexpected case insensitivity.
This problem occurs because a problem in the original .NET Framework 2.0 Setup sets the value of the
registry key determines whether a file system is case sensitive or case insensitive.If the value of this key is set to 1, the file system is treated as case insensitive. If the value of this key is set to 0, the file system is treated as case sensitive.
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.
registry key to 0 because you must have case sensitivity for the file system, and an update for the .NET Framework 2.0 has set this value back to 1, set the value for this registry key back to 0 manually. Restart the system for the changes to take effect. For example, if the server is an NFS server in a heterogeneous environment and the registry key value is set to 1, you can set the value back to 0 manually.
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.
kbsecurity kbprb case insensitive insensitivity .NET Framework 2.0