NET Framework 4 Client Profile update kills WinXP SP3 network startupAfter installing this update boot time increases (especially the time between log-in and desktop appear)Event log records PerfNet Event 2005 & 2006Reqets to moderators: Please move this post to appropriate category (WinXP).Sorry for mistake

Hi lechu54, There is a possibility that some third party programs installed on the computer is causing the slow boot.I would suggest that you perform clean boot and check. To help troubleshoot error messages and other issues, you can start Windows Vista by using a minimal set of drivers and startup programs. This kind of startup is known as a "clean boot." A clean boot helps eliminate software conflicts. Refer the below link to know more about clean boot procedure.How to configure Windows XP to start in a "clean boot" statehttp://support.microsoft.com/kb/310353 Reset the computer to start as usualAfter you have finished troubleshooting, follow these steps to reset the computer to start as usual:a) Click Start, type msconfig in the Start Search box, and then press ENTER.b) If you are prompted for an administrator password or for confirmation, type your password, or click Continue.c) On the General tab, click the Normal Startup option, and then click OK.d) When you are prompted to restart the computer, click Restart. Hope this helps!Halima S - Microsoft Support.Visit our Microsoft Answers Feedback Forum and let us know what you think.

Hello Halima SI'll try to be more specificI'm not looking for answers, I'am pointing a problem.After uninstaling .net Framework 4 update pakage the problem gone.The machine is brand new DELL with preinstalled Dell software only. The system is WinXP SP3 (domain enviroment)The only upates installed was GroupPolicyExtensions and .Net Framework 4System with .Net Framework4 installed delays booting on "Applying computer settings" for about 30 40- sec.

Hello,I also have this problem with HP computers. I think that Broadcom Control Suite is source of the issue since it runns on .net framework technology. Does this DELL you mentioned uses Broadcom network controller?

He is correct. The same thing was occurring on all 1,000 of the PCs on our domain. All brands and models. Increases logon time by at least 2 minutes. I used SCCM to push out a program that manually removed .NET 4 from all machines and the problem vanished.I have since declined .NET 4.0 from our WSUS server until this issue is resolved.

If you want to keep .net 4 go to Run type msconfig and choose the Services Tab. Scroll down to Microsoft .NET Framework NGEN v4.0 30319_X86, Uncheck the box, click apply and close. Restart. Click OK on the popup and do not put a check in the box. Go back to .NET 4 and put a check in the box to reenable. Click apply, OK, Restart. Once restarted click restart again and once restarted click restart again. Yes 3 restarts and now your computer should be back to normal! If it is not go to Control Panel, Administrative Tools, Services, scroll down to Microsoft. NET Framework NGEN v4.0 30319_X86 and double click, Change Startup Type to Manual. Hopefully Microsoft will fix this error soon!!!!!!!!!

I had the same problem and I spent many hours to find a solution. I think I've happily found :)I had to install Windows XP with SP3 on new HDD. I installed all updates from windows update. After installation of .NET FRAMEWORK 4 some problem appeared. After each computer start windows "freezes" for about 2 minutes (especially menu start and tray). I tryed solutions given by fyip and only "Change Startup Type to Manual" works but it only hides the problem.I read about "CRL" and I think that Framework 4 needs some initialisation from Microsoft before it starts to work properly. I'm getting internet to my home computer by USB Wi-Fi dongle. It starts at the end of windows startup queue and probably this "initialisation" can't be done. I temporary connected internet by LAN cable socket. Windows started properly and quick. I disconnected LAN cable and connected USB dongle again. Now my windows works fine with NET 4 :) I informed Microsoft support in Poland about my solution and I hope it will be helpfull.

I have since discovered that the fix only works for 50% of the computers affected, so I would assume it depends on ones configuration. .Net 4 is not really needed now and by the time it is Microsoft should have it fixed?????????