locked
Microsoft .NET Framework NGEN v4.0.30319_X86 service is causing startup delay RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi. On 2011-04-17, .NET Framework 3, 3.5 and 4 are updated via Automatic Update/Windows Update. Subsequently, all users (user accounts) experience significant startup delays during which Windows Shell (Explorer.exe) does not respond, especially Taskbar and Start Menu either do not respond or respond after a delay.

    I have confirmed that during the delay, Microsoft .NET Framework NGEN v4.0.30319_X86 service is in Starting state. Disabling this service would temporarily resolve the issue for one single startup. (I believe it is because installed .NET Framework applications put this service back to work.)

    How can I resolve this delay?

    P.S. Please don't tell me to .NET Framework forum; that one is a developers forum and I don't want to receive code optimization tips for applications that haven't written myself!

    The greatest moment of everyone's life is the moment of positive thinking.
    • Edited by Fleet Command Wednesday, April 20, 2011 6:17 AM Added an addendum
    Wednesday, April 20, 2011 6:16 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Someone else correct me if I'm wrong, but I don't think disabling those services hurts anything.  Maybe some .net apps will start slower.  You can also try compiling the .net apps manually (I have 64 bit windows 7):

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe executequeueditems
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe executequeueditems

    It actually took me over an hour to run the .net updates.  I think in my case it recompiled everything.

    .net could definitely be improved in terms of not impacting boot or login speed.

     

    • Marked as answer by Fleet Command Friday, April 22, 2011 7:39 PM
    Wednesday, April 20, 2011 2:32 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Someone else correct me if I'm wrong, but I don't think disabling those services hurts anything.  Maybe some .net apps will start slower.  You can also try compiling the .net apps manually (I have 64 bit windows 7):

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe executequeueditems
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe executequeueditems

    It actually took me over an hour to run the .net updates.  I think in my case it recompiled everything.

    .net could definitely be improved in terms of not impacting boot or login speed.

     

    • Marked as answer by Fleet Command Friday, April 22, 2011 7:39 PM
    Wednesday, April 20, 2011 2:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks. I haven't tried this yet but judging from what I read, it should do it. As for trying it, I must be personally present on the affected workstations. The users are very afraid unfriendly-looking commands like this. Let's see what I can do...
    The greatest moment of everyone's life is the moment of positive thinking.
    Friday, April 22, 2011 7:41 PM