You may find slow down in system booting time after installing .NET Framework 4.0 client profile


You may find slow down in system booting time after installing .NET Framework 4 client profile on a system and removing .NET Framework 4.0 client profile may resolve the issue. First you should check if there is an mscorsvw process that is taking a bunch of the CPU time. That would suggest that the slow down is related to contention with the ngen service. Running ngen /executequeueditems for both Framework and Framework64 folders and then seeing if the boot time issue resolves would also help narrow it to an issue with ngen competing for resources. The ngen service does try to ngen assemblies in the background until all the assemblies are ngen’d.


Comments (2)

  1. Ken Massey says:

    Do you need to ngen /executequeueditems for each framework installed in both 32 and 64 bit framework? I have v1.0.3705, v1.1.4322, v2.0.50727, v3.0, v3,5, and v4.0.30319 under my …framework folder and v2.0.50727, v3.0, v3,5, and v4.0.30319 under my …framework64 folder. (Vista Home Premium, Visual Studio 2010 express).

  2. .net 1.1 and 3.0,3.5 don't have the mscorsvw service.

    Run the ngen command under C:WindowsMicrosoft.NETFramework64v4.0.30319 and C:WindowsMicrosoft.NETFrameworkv4.0.30319 because the .net 2 mscorsvw service is disabled after installing .net 4.

Skip to main content