Was curious if anyone else has had this problem.

Upon downloading the Microsoft update which installs .NET 4.0 (did this a long time ago when it came out and had this problem and decided to try it again yesterday), the bootup time on my WinXP machine takes MUCH longer. After uninstalling .NET 4.0, my boot times went back down. What I consider "bootup time" starts when the BIOS flashes on the screen until the last items are done loading in the Windows system tray at the bottom right of the screen. Without .NET 4.0, my system completes this boot time in 45 seconds. With .NET 4.0 installed, this is stretched out to 2 minutes 8 seconds because it takes forever for the Microsoft security center to load (the little shield) and also network support (which I have the icon for in the system tray as well). The system shows no adverse effects otherwise in terms of speed once it's finally booted up and running, but I find this almost tripling of the bootup time simply unacceptable, so I'm running without .NET 4.0 again and have no intention of installing it unless I absolutely HAVE to at some point in order to get something to run that cannot go without it.

This is on a custom built machine running XP 32-bit with all other updates intact (SP3, etc.). It's a relatively fresh custom format which is only about 6 months old. The system is relatively fast (for circa 2006 hardware), very stable, and has no other "issues" whatsoever. So is this just me or does everyone have this problem with .NET 4.0?



Last edited by JR96CK on Sun Mar 17, 2013 4:01 pm; edited 2 times in total

you have received no replies

Actually, tbi™ replied. It's just that when tbi™ replies it doesn't show up as a post in a thread, the knowledge just gets beamed directly into your brain.

I also now know how to compress liquids.

JR96CK wrote:

I also now know how to compress liquids.

in the Ronco Liquid compressor!

JR96CK wrote:

Was curious if anyone else has had this problem.

Upon downloading the Microsoft update which installs .NET 4.0 (did this a long time ago when it came out and had this problem and decided to try it again yesterday), the bootup time on my WinXP machine takes MUCH longer. After uninstalling .NET 4.0, my boot times went back down. What I consider "bootup time" starts when the BIOS flashes on the screen until the last items are done loading in the Windows system tray at the bottom right of the screen. Without .NET 4.0, my system completes this boot time in 45 seconds. With .NET 4.0 installed, this is stretched out to 2 minutes 8 seconds because it takes forever for the Microsoft security center to load (the little shield) and also network support (which I have the icon for in the system tray as well). The system shows no adverse effects otherwise in terms of speed once it's finally booted up and running, but I find this almost tripling of the bootup time simply unacceptable, so I'm running without .NET 4.0 again and have no intention of installing it unless I absolutely HAVE to at some point in order to get something to run that cannot go without it.

This is on a custom built machine running XP 32-bit with all other updates intact (SP3, etc.). It's a relatively fresh custom format which is only about 6 months old. The system is relatively fast (for circa 2006 hardware), very stable, and has no other "issues" whatsoever. So is this just me or does everyone have this problem with .NET 4.0?

I didn't know what it was but some time back after I installed an update my XP boot time is almost 4 mins. maybe this is my issue and i should try to uninstall it. I also noticed some time ago after updating that i get errors while shutting down as well that i didnt have before. I have just been avoiding that laptop lol.

Aloicious wrote:

in the Ronco Liquid compressor!

All for just $19.95.

s10mods wrote:

I also noticed some time ago after updating that i get errors while shutting down as well that i didnt have before. I have just been avoiding that laptop lol.

My problem was definitely .NET 4.0, as my system runs perfectly without it.

JR96CK wrote:

Aloicious wrote:

in the Ronco Liquid compressor!

All for just $19.95.

But wait, there's more. Call in the next 10 minutes and you will get TWO Ronco Liquid Compressors for the price of one! Just pay separate shipping and handling.

I compressed 5 gallons of water down so I could carry it in my pocket, but it pulled my pants down it was so heavy.

The second post from the top by user "FM-190" is what I used to fix this problem completely.

http://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/kb982670-net-framework-4-client-profile-slows-down/4476f6ab-3355-4ed6-bec2-bfe18dd408b0

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


NOTE:

The directory v2.0.50727 may be different if no earlier versions of .NET framework were already installed. It will be v4.0.30319 with only the version 4 present."

Also, you can just shut off the .NET 4.0 service and all .NET applications will apparently still run fine (although I have not personally tried this approach since the first one worked for me). You would need to shut down the "Microsoft .NET Framework NGEN v4.0.30319_X86" service form what I have read.

So now, two months after posting the fix for this issue, I just did another round of Windows updates on my laptop. The slow boot problem returned.

I did the above procedure again and now all is well. Apparently, any time you do Windows updates now, you have to manually go in and do this step through the command line as outlined above. Thanks, Microsoft.