none
Why does .NET Framework 4 client profile slow down boot time network creation?

    General discussion

  • I've been running a Windows XP sp3 KVM virtual machine for a long time now, and some recent update made the initial network startup go from a few seconds at boot time to around 90 seconds. Using Add/Remove program to uninstall recent updates points the finger at .NET Framework 4 client profile. With it installed, if I right click on network and ask for properties right after booting, there is a 90 second delay before the network dialog with the list of network interfaces finally appears. In addition, the network drive I have automounted at login is not accessible for the same 90 seconds. As an experiment, I tried going into the device manager and deleting the network interface, and if I reboot after that it takes 90 seconds for the new hardware wizard to appear. All these 90 second delays vanish if I remove this .NET update. The network comes up as soon as the system boots.
    • Changed type Larcolais Gong Sunday, September 12, 2010 6:56 AM General
    Friday, August 06, 2010 1:23 AM

All replies

  • Hi, I have just done a format and reinstall last night. I went through all the microsoft updates and all was ok. I noticed Net Framework 4.0 was out so installed that too. Same thing happened to me, machine boots up at the same speed but I cannot access the web or device manager for about 90+ seconds. Did a system restore to before I installed it and everything ok again. Its definately .Net Framework 4 causing it.

    Sunday, August 08, 2010 5:31 PM
  • Hi Tom,

    Thank you for your post in MSDN forum!

    Sorry for the late reply!

     

    Some clarification with you

    Have you any issues during installing .NET Framework 4 client profile?

     

    Based on your description, it seems that your issue might not be more related with .NET Framework 4.

    I would recommend that you could check whether your machine is installed some add-ins or not.

    Frankly speaking, many factors could cause your issues. E.g. virus, malware and so on

     

    Hope this helps your concern!

    Best Regards

    Larcolais Gong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Monday, August 09, 2010 5:14 AM
  • I don't think any external issues could be in play here. I clean installed a brand new Windows XPsp2 virtual machine and merely applied updates, starting with SP3 and going through the 70 or so updates offered by windows update after that. The network slowdown started immediately after applying the .NET Framework 4 client profile update, and stopped immediately upon un-installing it.No 3rd party software installed no websites visited other than windows update through the entire process.

     

    Another side effect I noticed later was right clicking in the desktop to bring up desktop setting then going to the desktop tab. The background image no longer shows in the little monitor that normally previews your background selection. It is just solid microsoft blue all the time. (And that bit didn't start working after 90 seconds, it was permanently busted).

    Monday, August 09, 2010 11:32 AM
  • Yes, same scenario here....  went from a rather quick boot

    running XP sp3   and after install.... the wallpaper boots up

    on screen and sits for 45 seconds...  Uninstalled both .net 4

    componenets and all was back to normal.  WHEW

    Thursday, August 12, 2010 4:12 PM
  • Hi Tom,

    I'm glad to see your feedback.

     

    You issue might be related with many factors and is a special one, cannot follow common step.

    Here is .NET Framework Setup Forum. I would do my best to help you solve .net framework installation issues.

     

    Could you have some issues about .NET Framework Setup?

    If you have some issues or concerns about installation, you could consult it here.

    If the installation works well, I would encourage that you could consult your concerns in KVM forum.

    You will get more helpful suggestions there.

    http://www.linux-kvm.org/page/KVM_Forum

     

    Thank you for your understanding!

    Best Regards

    Larcolais Gong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Friday, August 13, 2010 6:35 AM
  • I've just done two clean XP SP3 installs.  The first one began acting as described above, taking about 90 seconds before the network connections showed up in the systray, hanging up if I tried to open network connections in the control panel.  On my second machine after each installation of updates i rebooted to see if the problem occurred again.  It did following install of the optional software updates which included the .NET Framework 4 client.  I uninstalled the .NET Framework 4 client  and things  began working normally again.  I then went back to machine #1 and uninstalled .NET Framework 4 client and the machine now boots up properly again.
    Friday, August 13, 2010 7:26 PM
  • I have just repeated the updates on my real hardware running XP, and the same slowdown happens on real hardware as soon as the framework 4 update is installed and goes away as soon as it is removed, so this clearly has nothing at all to do with running on a virtual machine.
    Saturday, August 14, 2010 11:40 PM
  • SAME here!

    Virus is mythos, my system is virgin like the maria:

    I have formatted my whole HD > then run Windows Update > install .Net Frameworks 4 > BUM! slow down the next boot as said above

    When i remove .Net Frameworks 4 verything runs like a rocket.

    Developers, you have a problem!

    Solution:

    in terminal type:

    cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319
    ngen update

    ^ this will rebuild native images. run like rocket!

    info here: http://stackoverflow.com/questions/2947118/wpf-slow-to-start-on-x64-in-net-framework-4-0

    Sunday, August 15, 2010 3:47 PM
  • That certainly may be related, but my systems are all 32 bit. (And why does my text cursor go invisible in this edit dialog in the forum? :-).
    Sunday, August 15, 2010 4:02 PM
  • I'm having the same problem here on two new machines (clean Install of XP SP3). Installing .net 4.0 drastically increased boot times. Removing .net 4.0 "solved" the problem.

    Thursday, August 19, 2010 7:53 AM
  • Hi Tom,

    Visual Studio 2010(.Net 4) runs faster when the Windows Automation API 3.0 is installed follow the Link http://support.microsoft.com/kb/981741

    For XP OS install http://www.microsoft.com/downloads/details.aspx?FamilyId=cd55456d-9703-42a0-b982-8a8a89ca0aa3&displaylang=en 

     

     


    Regards, tnvbalaji http://in.linkedin.com/in/tnvbalaji
    Sunday, August 22, 2010 7:11 AM
  • Absolutely correct.

    NetFramework 4 DOES slow down boot time in the manner mentioned.

    I have built & rebuilt several machines from scratch with a clean fresh install of Windows XP SP3 (Home or Pro - doesn't matter which type) AND with NO installation issues.

    Upon removal of the Net Framework 4 boot up time returns to normal.

    So until a fix for this issue is released NO installation of Net Framework 4 from this shop.

    Friday, August 27, 2010 11:02 PM
  • Just chiming in that I have also been experiencing this on both new and old hardware with XP SP3.  As soon as I install .NET Framework 4 client profile there is a 90-120 second delay in network startup.  If I remove the update all goes back to normal.  3 from scratch machines including one very new pc with plenty of power so does not appear to be related to horse power of machine.  All 3 have different network cards and motherboard and all exhibit exactly the same behavior and the issue is resolved after removal of the update.
    Thursday, September 02, 2010 3:09 PM
  • We recently allowed Windows Update to install the .NET 4.0 kit on an entire division and experienced the same issue. Windows XP becomes unresponsive for up to two minutes on every boot after login for every workstation with the update, all others are fine. All workstations are exactly the same Dell systems (dual core, 4Gb ram workhorses... not weak machines). Restoring the stations back to a previous image or removing the 4.0 framework removes the problem. We've now experimented on several completely clean machines (new OS alone).. same behaviour. Clearly this is a problem with the framework, not the planet's PC's.
    Tim
    Thursday, September 02, 2010 6:49 PM
  • Have exactly the same problem .... also waiting on an answer / fix

    This has nothing to do with other programs, but only Framework 4.   :(

    This also seems only related to XP ... have have a Win7 machine with this update which seems fine  ;)

    Tuesday, September 07, 2010 12:50 PM
  • I have the exactly same issue. Just restored a netbook from hidden partition and started updating WinXP through Windows Update. All fine until it installed .NET updates. I've had the same problem on a friends system where the thing fixed itself after installing new updates for .NET Framework. But i guess the order of updates was in the same order as planetary alignment was to the sun and the problem went away by itself. However in netbook's case, after second system restoration, still stupid dead slow initialization of network interface. I'm going to try removing .NET 4 profile, but i think this is just ridiculous. Why on Earth is some stupid .NET Framework update doing this? It's not a random problem because it happened on 2 completely different platforms, one AMD based with AthlonXP and another Intel based with Atom. AMD one had Windows XP Professional 32bit, my netbook is using Windows XP Home Edition 32bit. Someone really has to test these .NET updates thoroughly.
    Tuesday, September 07, 2010 4:39 PM
  • I've just purchased visual studio 2010 and had to install .net framework 4(from the setup disk). I agree completely with what these guys are saying. I have installed/reinstalled several times now and found in no uncertain terms the .net framework 4 is the issue.

    After spending a lot of money on development software i don't expect it to sabotage my boot up time from 1 minute to nearly 3 minutes. I am running XP pro 32bit, i have done a clean install to try and rectify this, i have no worms, rootkits, viruses or malware and would like a reasonable solution rather than trying to justifying the problem by some other means. I feel that after spending a lot of money on this software, i am very annoyed that i have no choice but to put up with this slow annoying problem .net 4 has created.

    I also build and repair computers for a living and at present choose not to install .net 4 on client machines as it looks very bad for my business that the pc that i've built or repaired takes so long to boot up.

    By looking on this thread it seems to be only XP users that are suffering with this issue(I thought microsoft had pledged support for XP users through 2014)

    Come on guys your customers deserve better than this.

    Wednesday, September 08, 2010 12:16 PM
  • Ok make a batch file in notepad with the following,

    c:
    cd \
    cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
    ngen update
    cd \
    cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    ngen update
    cd \
    cd C:\Windows\Microsoft.NET\Framework\v4.0.30319\
    ngen update

    Make sure you save it as .bat (I use netfix.bat) and ensure that C: is the system drive on your PC, tested on 32-but versions of XP YMMV

    Wednesday, September 08, 2010 6:01 PM
  • Hi David, thanks for your reply - That worked great. I got a few version errors when running the batch file but it worked none the less. Took my boot time from 180 seconds to 90 seconds.

    you've saved me a lot of hassle.

    Kind Regards

    DMonair

    Wednesday, September 08, 2010 6:30 PM
  • Glad to hear! I still dont really know what .net actully is!

    My version comes up with version errors and the like too, to me it looks like a screen from a movie! *I think that the more .net software you have the less errors you get, or something like that, we just need an expert to enlighten us now :)

    Wednesday, September 08, 2010 6:35 PM
  • your fix is one of many on the web.....

    same as just going to "services.msc" and switch  "Microsoft .NET Framework NGEN v4.0.30319_X86" from auto startup to "disable" or "manual" ....

    problem is, we still don't know why it's like this in the first place ... the developers will have to admit they F@##$$'d up & fix it accordingly :@

    Wednesday, September 08, 2010 8:27 PM
  • Same problem same solution.  Only on my main PC my taskbar would freeze for like 30-40 seconds.  On another PC I experienced the network issue.  I disabled the service on the PC with the network lag and voila!  I had to uninstall the 2 components from my main PC to get it working right again.
    Wednesday, October 06, 2010 11:18 AM
  • Add me as another one. Installed through updates on one of my laptops and it ground everything to a complete halt. The laptop was completely unusable.

    Uninstalled it and everything back to normal.

    Typical Microsoft, we really are all your Beta testers really.

    As my university lecturer used to say 'test, test and test again'.

    As usual there are several 'hacks' on the internet to attempt to fix the issue when really the installation and deployment should cater for it. Microsoft you really do take the p$$s. I seem to spend most of my time dealing with your so called solutions usually with integration issues. Change the registry here, extract the installer there.....

    Sunday, October 10, 2010 12:46 PM
  • Same problem...Installed .NET Framework 4 & Client updates and my Windows XP SP3 computer stops booting about midway through.  After 2-3 minutes, it will resume S L O W L Y to completion, but stops occasionally to catch its breath.  This is not acceptable, but, fortunately, was able to remove .NET Framework 4 through Control Panel, and things look like they have returned to Windows XP normal boot foibles.  I gather the problem is related to the combination of .NET 4 and Windows XP.  Is this some plan to get us stubborn XP users to update to Windows 7?  If you can't entice us over with features or improvements, try sabotaging the systems!

     

     


    edelorenzo
    Monday, October 11, 2010 9:23 PM
  • Ohhhhhh, more services that run at startup! Windows BLOAT continues...

     

    Microsoft .NET Framework NGEN v4.0.30319_X86 => Automatic  WTF for????

    Microsoft .NET Framework NGEN v4.0.30319_X64 => Automatic  WTF for????

     

    Thursday, October 21, 2010 6:14 PM
  • Some times it takes 3 restarts for a update or installation to catch. I had the same problem after installing .net 4 startup was very slow, my desktop took about 1 and 1/2 min. to load. After 3 restarts it was back to normal.

    Tuesday, November 16, 2010 11:36 PM
  • Changing it from Auto to Manual in Services.msc fixes problem for me as well. Rebooting 5 times did not kick it into a normal boot.
    Sunday, November 21, 2010 11:18 PM
  • It was doing the same thing on all 800 of my systems on our domain. I pushed out an SCCM SMS program that manually removed .NET 4 and they are all working fine now. I have since declined any .NET 4 Windows updates on our WSUS server.
    Monday, November 22, 2010 5:47 PM
  • Having the EXACT same problem.

    I loaded 2 clean machines behind a DMZ so this isn't a trojan/virus.

    Both x86-64 cpus, one amd, one intel.

    XP32bit, SP3.

    Then it comes to installing .NET4 Client Profile and bam - 90second boot before the network is available.

    This is an absolute joke.

    Do people at microsoft not realise how much time this wastes?

    This is why we avoid running microsoft systems where we can help it, with linux you dont have all this unexpected downtime.

    Thursday, December 09, 2010 5:28 AM
  • On XP pro SP3. I need .NET framework 4 for one application. After installing the security update KB 2416472, I also found that on startup some 20 seconds elapsed between the desktop background showing and the task bar, desktop icons and systray apps loading. Event viewer showed a long (20 second) delay between 'Microsoft .NET Framework NGEN v4.0.30319_X86 service entered the running state' and the next event, Symantic antivirus starting.

    So in services I disabled the 'Microsoft .NET Framework NGEN v4.0.30319_X86 service , restarted and startup was back to normal. The app that uses .NET framework 4 is unaffected. No errors or warnings in event viewer either.

    This is a stand alone PC, I do not develop any software I don't need NGEN as far as I understand its purpose.

    Sunday, December 19, 2010 12:06 AM
  • ARRRRGGGHHHHHHH

    Ive spent 4 hours this evening, rebuilding my pc, restoring, rolling back drivers, software.. etc only to find out it was a Mircrosoft Update causing the problem!!!...... and its been a problem for months, and no fix!!!

    I should bill them for my time!!!

     

    NOT HAPPY!!!


    DrSoton
    Saturday, January 15, 2011 11:24 PM
  • One of the things that .NET does is allow you to write a program that will run on different types of computers.  Commonly, there are two types of Windows computers you can buy -- 32 bit or 'x86' computers and 64 bit or 'x64' computers.

    NGEN is a program that looks at a .NET application and says "if this computer is x86, optimize the program to run well there.  Otherwise if the computer is x64, optimize it for that type of computer'.

    What's happening is that in order to decrease installation time, .NET 4.0 doesn't run this 'ngen' process when you install .NET 4.0.  Instead, it starts a service and does it in the background later.  As one previous poster said, "after three boots, the computer ran fine."  In his case the background NGEN service had finished its work and was no longer slowing boot down.

    If you don't uninstall .NET 4.0, you should notice that the boots speed comes back to normal after a few hours have passed and NGEN has had time to finish its work -- which it only does once per installation.

    Monday, January 31, 2011 8:38 PM
  • http://my.opera.com/rejzor/blog/slow-windows-xp-sp3-startup-with-net-framework-4

    Check my blog on the link above (www.rejzor.tk) and get a quick fix. I've had the same problem on netbook running WinXP which i later solved with the little tool that generates .NET stuff at once.

    After everything is generated it should be booting significantly faster after that.

    Sunday, February 06, 2011 9:58 PM
  •  

     Thanks for posting a description of this -  I had noticed strange behavior in the NIC delay on bootup under Windows XP - I couldn't figure what had changed - I knew i had done Windows updates for everything - but i progressed logically by deleting the Antivirus, then the Firewall, etc and nothing changed.  I even ran HijackThis and removed all booting services, and the network delay still persisted.   I ran BOOTVIS and it showed a NIC delay of 15 seconds, but nothing that indicated any strange services were starting.

     

    Finally I came across this, and removed ".NET 4.0 Client Profile".

    Fixed it.   Instead of waiting 45-60 secondsfor the NIC icon to appear on the traybar, it now shows up within 10 seconds.

    Wow.. is MS aware of this?  I can see some critical internet applications which need to establish a link right after bootup, and this delay would be impacting that significantly if they have to wait 1min+ for startup.

    By the way, even though the NIC driver loads under Bootvis, it still doesn't have network connectivity until the NIC icon appears on the traybar, so i don't think MS can argue that the driver is loading on time.  

    It's a definite issue with .NET 4.0 Client Profile.

    Wednesday, May 04, 2011 8:36 PM
  • Thanks to everyone for this forum - I can finally stop banging my head against the wall! I also performed a fresh install of XP SP 3 and saw the same drop in performance following installation of .NET 4.0 - removing the update fixed the issue.

    Michael Delcour

    Thursday, May 05, 2011 8:40 AM
  • the .net NGEN optimisation service recompiles the .net assemblies to native for the host system configuration.

    This usually occurs on the first reboot and may take up to 30mins (system capabilities dependant).

     

    Once completed, it will(should) only run in periods where the system is completely idle to optimise updated/changed assemblies.

     

    Try being patient for the first time in your lives guys.

    Tuesday, June 07, 2011 1:21 PM
  • NET Framework 4 client profile for Microsoft Office 2010 purposes . Please do not install it if you do not have office 2010.

    It will spoiled you systems

     

    Thanks

     

    Error -

    Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

    Conversion from string "<html>

    <head>

    <title>OpenDNS<"to type 'Double' is not valid.

    And here is the information in the Details box:

     See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.InvalidCastException: Conversion from string "<html>
    <head>
    <title>OpenDNS<" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.
    at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
    --- End of inner exception stack trace ---
    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)
    at CPAX20.utilities.Dec(String strCode)
    at CPAX20.Form1.tmrOffer_Tick(Object sender, EventArgs e)
    at System.Windows.Forms.Timer.OnTick(EventArgs e)
    at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------
    CPAX2
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Common%20Files/alg.exe
    ----------------------------------------
    Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.4926 built by: NetFXw7
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    Microsoft.mshtml
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.0.3300.0
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
    ----------------------------------------
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.


    Monday, June 27, 2011 1:08 PM
  • In my (unfortunately for you, german) Blog http://habitec.wordpress.com I tell the story of a Notebook with Win 7 that can be destroyed by installing the .Net 4 Update! Friends had similar issues too. Another Blog http://www.borncity.com/blog/2011/07/02/viel-rger-mit-dem-net-framework-4-0-client-profile-update/ has a bit more information.

    Here my Google-supported translation of the issue:

    An HP NW9440 laptop of a customer that has worked well with XPpro/SP3. Since the last update (I do not know if NET 4.0 was in it)  the PC will not boot anymore, but reports "broken registry".

    Customer says, if I have to re-install it, then with Windows 7. I've now tried everything to systematically narrow down the problem, I am now in my 10th Installation or something ...

    - Windows 7 32 bit and 64 bit are affected
    - Vanilla installation, install all updates and latest drivers other than any NET -> PC is working properly
    - Then (! Not with the other updates!) install the updates NET351 -> PC still works
    -. As soon as the update installs NET4.0 client -> PC will not boot, system repair can not repair, restore point failed

    No repair possible, just reinstall.
    [This shows, incidentally, the failure of the
    built-in backup program, because only with Acronis I can back to a point before the installation ...]

    For my friend it was some PCs that had  network problems
    after NET4.0 update. After uninstalling everything went fine. [This tip brought me only on the right track]

    Saturday, July 02, 2011 8:45 AM
  • Solution to this problem

    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.
    Saturday, September 03, 2011 10:58 PM
  • I've been running a Windows XP sp3 KVM virtual machine for a long time now, and some recent update made the initial network startup go from a few seconds at boot time to around 90 seconds. Using Add/Remove program to uninstall recent updates points the finger at .NET Framework 4 client profile. With it installed, if I right click on network and ask for properties right after booting, there is a 90 second delay before the network dialog with the list of network interfaces finally appears. In addition, the network drive I have automounted at login is not accessible for the same 90 seconds. As an experiment, I tried going into the device manager and deleting the network interface, and if I reboot after that it takes 90 seconds for the new hardware wizard to appear. All these 90 second delays vanish if I remove this .NET update. The network comes up as soon as the system boots.
    Hello the solution is to disable the Windows CardSpace
    Sunday, September 04, 2011 1:17 AM
  • Thanks FM-190! Worked for me (with a different folder name -- v.4x, not v2.x). The program launched and started to recompile some packages. After finished, I've turned the .NET 4 service into Automatic start up state, rebooted and discovered no delays. 

    Now the question is: if the service was freezing when it was some uncompiled queue and after compilation of the queue it stopped to freeze, will it start freezing again if there will be a new queue after couple of days or weeks or months?


    • Edited by GraveD Sunday, September 04, 2011 3:40 PM
    Sunday, September 04, 2011 3:39 PM
  • Thank you FM-190!
    Saturday, September 17, 2011 3:29 AM
  • Thanks :)

     

    Saturday, September 17, 2011 9:23 PM
  • Welcome all :)

    Sunday, September 25, 2011 9:10 AM
  • I have a program on my computer called Soluto. It shows specifically what is running in boot and what time is taken for each item. Microsoft .Net Framework Client Profile adds 89 seconds to my boot time. Try installing and running this program to see what is causing your boot time.
    Thursday, October 13, 2011 4:42 PM
  • Excellent help FM-190 solved a Small Basic slowdown for me as well.

     

    Just wondering why you run the  

     NGEN executequeueditems

    from the  Windows\Microsoft.NET\Framework\v2.0.50727 directory

    as opposed to other more recent Framework directories?


    Saturday, November 05, 2011 1:45 PM
  • If you had any previous version of .NET installed then NGEN and other major files are contained in the that old version's directory. I had earlier version installed that's why executed it from that directory.
    Thursday, December 15, 2011 11:40 AM
  • WOW GREAT FIX all runs well now.Using Windows XP and installed Sopcast.To use PC Streams I had to download Net Framework 4 as primarly Net frameworks does not work with PC STREAMS. My PC slowed down to 3 minutes boot. Real crazy. MS has an official fix for thisbut does not work at all FM -190 fix is great all the DOS commands run great.

    Result GREAT performance on my pc XP with PC Streams and SopCast 

    Thanks a lot FM 190 great help!

    Why does this MS Fix not work? h*tp://support.microsoft.com/kb/2570538

    Friday, April 13, 2012 9:22 PM
  • Solution to this problem

    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.

    I followed your steps but this is what i got. i did not wait for minutes, just for a second.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Reyes>cd\

    C:\>cd Windows\Microsoft.NET\Framework\v4.0.30319

    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>NGEN executequeueditems
    Microsoft (R) CLR Native Image Generator - Version 4.0.30319.1
    Copyright (c) Microsoft Corporation.  All rights reserved.
    All compilation targets are up to date.

    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>

    HEEEELLLLPPPPP!!! I cant fix this problem!

    • Edited by Harpi101 Saturday, May 26, 2012 12:26 PM
    Saturday, May 26, 2012 12:25 PM
  • I followed the steps of FM-190 but this is what i got. i did not wait for minutes, just for a second.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Reyes>cd\

    C:\>cd Windows\Microsoft.NET\Framework\v4.0.30319

    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>NGEN executequeueditems
    Microsoft (R) CLR Native Image Generator - Version 4.0.30319.1
    Copyright (c) Microsoft Corporation.  All rights reserved.
    All compilation targets are up to date.

    C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>

    HEEEELLLLPPPPP!!! I cant fix this problem!

    Saturday, May 26, 2012 12:28 PM
  • Yes I have the same problems and have competed all the steps here to no avail. This is the third reinstall and it is frustrating. I just went to premium MS Services, They want a hundred bucks to remote in and try to fix the system. This is an xp computer, probably not worth the hundred bucks -So what does he do? He sends right back to this same formum and says the answer may be in here and he has now given me enough troubleshooting points that I should be able to work it out unless I want to pay the 100 bucks. Hey thanks MS
    Wednesday, May 30, 2012 5:32 AM
  • I have the same problem! Windows XP Pro SP3 x32 is loading very slow, programs and menus aren't accessible for about 2 min.
    Thursday, August 30, 2012 10:49 AM
  • You're my personal hero. Thank you for solving the problem.
    Thursday, March 28, 2013 1:03 PM