NCover Documentation

There are a few cases in which the NCover environment does not get reset after running NCover on services or IIS.


An NCover environment that has not been properly cleaned up will cause every .NET application to take an abnormally long time to load. This time is caused by NCover being loaded by the application and proceeding to attempt its handshake with NCover.Console.


This scenario is primarily caused by NCover being killed during execution. This is especially common in build server environments where the build server includes functionality to stop the build.


The environment variables that cause this issue to occur are set in the registry. Open regedit.exe and browse to HKEYLOCALMACHINE\System\CurrentControlSet\Control\Session Manager\Environment and delete the following keys:

  • CorEnableProfiling
  • Cor_Profiler
  • NCover_PID

If you still need technical assistance, we can help:

Submit A Support Ticket