.NET Framework Security

The .NET Framework Configuration Tool's Self Protection Mechanism

The tool is itself written in managed code. This means that it is subject to security checks within the .NET Framework security system just as any other assembly is. Although the security default policy is designed to give the tool enough trust to run properly irrespective of from where it is started, it is possible to change security policy such that the tool will not receive sufficient permissions to do its job. Consequently, the tool has a self protection mechanism built in that evaluates whether the policy change you are about to make would jeopardize the proper running of the tool during future tool sessions.

NOTE

Security policy changes are always only applied to assemblies ...