none
Problems that i hv faced when using .NET framework. RRS feed

  • Question

  • What i experienced on various windows platforms & machines is that installing .NET framework actually slows the startup time of windows by a fracton of about 1 min.And also the response rate of machines decreases.why?

    You can experience it yourself by installng & uninstalling .NET framework..

    Wednesday, August 1, 2012 5:56 AM

Answers

  • Hi atulpathak,

    Thanks for your post.

    What's your OS version?

    Frankly speaking, many factors could cause your issues. So we may have to reproduce this issue.

    BTW, I have found a blog which may helpful to your issue:

    http://blogs.msdn.com/b/smondal/archive/2010/10/21/you-may-find-slow-down-in-system-booting-time-after-installing-net-framework-4-0-client-profile.aspx

    "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."

    For how to use the command, here is a example from this thread by FM-190http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/cb75c4dc-e0af-4b22-85b2-c2c1b08bfea1:

    You can change the folder from v2.0.50727 to v4.0.30319

    "When .NET redistributable is installed, it compiles the high priority assemblies in 5 to 10 minutes and then waits until your computer is idle to process the low priority assemblies. The following method forces all of the remaining items to be compiled with a command called NGEN.exe. Follow these steps:


    1) Run cmd.exe from Start > Run

    2) Type cd\

    3) Type cd Windows\Microsoft.NET\Framework\v2.0.50727

    4) Type NGEN executequeueditems and press Enter

    5) It will take about 10minutes depending upon system speed. After the process is complete, the following prompt will appear in the command prompt

    C:\Windows\Microsoft.NET\Framework\v2.0.50727>

    6) Type exit to close the command prompt.

    After performing these steps, your computer will boot up at usual speed.

    "

    Hope this info can help you

    Regards,


    Barry Wang [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, August 2, 2012 5:33 AM
    Moderator

All replies

  • This is slightly tricky to deals since such cases are specific to environment. This means, your issue might not be valid in higher or may be severe in lower configurations than recommended. Hence I recommend you to verify your environment agonist recommended hardware profile with some checks. You may find it here and some performance tips here. Also, it's highly recommended to have a service pack installed and regular windows update.


    If this post answers your question, please click Mark As Answer. If this post is helpful please click Mark as Helpful.

    Regards,
    Nair S

    Wednesday, August 1, 2012 9:20 AM
  • Hi atulpathak,

    Thanks for your post.

    What's your OS version?

    Frankly speaking, many factors could cause your issues. So we may have to reproduce this issue.

    BTW, I have found a blog which may helpful to your issue:

    http://blogs.msdn.com/b/smondal/archive/2010/10/21/you-may-find-slow-down-in-system-booting-time-after-installing-net-framework-4-0-client-profile.aspx

    "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."

    For how to use the command, here is a example from this thread by FM-190http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/cb75c4dc-e0af-4b22-85b2-c2c1b08bfea1:

    You can change the folder from v2.0.50727 to v4.0.30319

    "When .NET redistributable is installed, it compiles the high priority assemblies in 5 to 10 minutes and then waits until your computer is idle to process the low priority assemblies. The following method forces all of the remaining items to be compiled with a command called NGEN.exe. Follow these steps:


    1) Run cmd.exe from Start > Run

    2) Type cd\

    3) Type cd Windows\Microsoft.NET\Framework\v2.0.50727

    4) Type NGEN executequeueditems and press Enter

    5) It will take about 10minutes depending upon system speed. After the process is complete, the following prompt will appear in the command prompt

    C:\Windows\Microsoft.NET\Framework\v2.0.50727>

    6) Type exit to close the command prompt.

    After performing these steps, your computer will boot up at usual speed.

    "

    Hope this info can help you

    Regards,


    Barry Wang [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, August 2, 2012 5:33 AM
    Moderator
  • thnks for the post it really

    worked!!

    Sunday, August 5, 2012 7:26 PM
  • Hi atulpathak,

    Glad to hear it works for you.

    Regards,


    Barry Wang [MSFT]
    MSDN Community Support | Feedback to us

    Monday, August 6, 2012 2:37 AM
    Moderator