Bad Windows Update

Discussion in 'other software & services' started by KelvinW4, Oct 11, 2011.

Thread Status:
Not open for further replies.
  1. KelvinW4

    KelvinW4 Registered Member

    Joined:
    Oct 11, 2011
    Posts:
    1,199
    Location:
    Los Angeles, California
    Today I downloaded 10 important updates, and when I restarted the machine became extremely slow. why is this happening?
     
  2. cm1971

    cm1971 Registered Member

    Joined:
    Oct 22, 2010
    Posts:
    727
    It happens sometimes. I have even seen updates for updates in the past. That being said I haven't had any slowdown with the latest updates. So far so good on my end.
     
  3. cgeek

    cgeek Registered Member

    Joined:
    Mar 31, 2010
    Posts:
    328
    It could be due to .NET getting updated. Usually after the update assemblies need to be recompiled.
     
  4. KelvinW4

    KelvinW4 Registered Member

    Joined:
    Oct 11, 2011
    Posts:
    1,199
    Location:
    Los Angeles, California
    Yes I am highly suspicious of .Net update I have seen.
     
  5. cgeek

    cgeek Registered Member

    Joined:
    Mar 31, 2010
    Posts:
    328
    If you open task manager and see a process with the name mscorsvw.exe that is probably the issue.

    You have two options:

    1. Let the computer stay idle for around 15-40 min depending on your machine specs. (Higher will be faster)

    2. You can force the JIT compile process with the following command by opening a elevated command prompt and add the following:

    .NET version 4

    Code:
    c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems
    for .NET versions 2.0 to 3.5

    Code:
    c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems
    HTH
     
  6. BoerenkoolMetWorst

    BoerenkoolMetWorst Registered Member

    Joined:
    Dec 22, 2009
    Posts:
    3,764
    Location:
    Outer space
    Yes, I always have this after .net updates, mscorsvw.exe takes 100% of 1 CPU for quite a while.
     
Loading...
Thread Status:
Not open for further replies.