Hi, Try temporarily turn off the firewall and anti-virus software then Clean Boot the computer and see the result. If still not work, since the Netlogon service may start before the network is ready, the computer may be unable to locate the logon domain controller. Based on your description, it seems the Netlogon service and Group Policy processing are both failed. I suggest you set a registry value to delay the application of Group Policy then see the result, follow these: 1. Open the Registry Editor, expand the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon 2. Right-click Winlogon, point to New, and then click DWORD Value. 3. To name the new entry, type GpNetworkStartTimeoutPolicyValue, and then press ENTER. 4. Right-click GpNetworkStartTimeoutPolicyValue, and then click Modify. Click Decimal, in the Value data box, type 60. 5. Quit Registry Editor, and then restart the computer. 6. If the Group Policy startup script does not run, increase the value of the GpNetworkStartTimeoutPolicyValue registry entry. If the issue still persists, I think you need to create a Windows 7 boot trace and analyze which steps cause the long time. Refer to this: http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/ (Since the site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.) Regards, Miya TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have a windows 7 SP1 computer that suddenly this week after MS updates started to hang at the Welcome screen after entering the domain account credentials - happens on a User account and Admin account. I've tried the suggestion here: http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/6580ad18-82f4-4922-bab3-7fa34d00ac31 to change the desktop background. No change. I believe it may have something to do with group policy, but the same policies work on other computers. The reason it may be GP related is this: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logon). eventually one time followed by: The winlogon notification subscriber <GPClient> took 153 second(s) to handle the notification event (Logon). events in the event log. Oddly enough, I can make the login happen normally by rebooting via the power button, and booting with the network disconnected until the desktop shows up. Otherwise, the issue is I've waited over 30 minutes at the welcome screen... When I do that, I do get a lot of group policy errors in the event logs such as the network path is not found... Any ideas to fix this before I do a re-install?

Hi, Try temporarily turn off the firewall and anti-virus software then Clean Boot the computer and see the result. If still not work, since the Netlogon service may start before the network is ready, the computer may be unable to locate the logon domain controller. Based on your description, it seems the Netlogon service and Group Policy processing are both failed. I suggest you set a registry value to delay the application of Group Policy then see the result, follow these: 1. Open the Registry Editor, expand the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon 2. Right-click Winlogon, point to New, and then click DWORD Value. 3. To name the new entry, type GpNetworkStartTimeoutPolicyValue, and then press ENTER. 4. Right-click GpNetworkStartTimeoutPolicyValue, and then click Modify. Click Decimal, in the Value data box, type 60. 5. Quit Registry Editor, and then restart the computer. 6. If the Group Policy startup script does not run, increase the value of the GpNetworkStartTimeoutPolicyValue registry entry. If the issue still persists, I think you need to create a Windows 7 boot trace and analyze which steps cause the long time. Refer to this: http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/ (Since the site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.) Regards, Miya TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Since the thread has been quiet for a while, we assume that the issue is resolve. We'll mark it as 'Answered' as the previous steps could help other people who encounter the similar issue. If you have any update, please feel free to let us know, we'll be notified to follow it up. Thanks for your understanding and cooperation! Regards, Miya TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.