asked on

Windows 7 Slow Login - LogonUI.exe Take 2+ Minutes to Process

Here is the issue a number of our Windows 7 workstations are having the following issue: When the workstation is started it will hang on "Please Wait" then after 2+ minutes the login prompt will appear. I have used Process Monitor with Boot logging and can see the LogonUI.exe takes over 2 minutes from start to finish. The workstation are blocked from GP for troubleshooting, no custom credential providers are in place, all items disabled vis msconfig, happen on both wired and wireless connections. I have used Windows Performance Monitor to capture process during boot but no closer to find the root cause. I have tried many suggestion regarding this online but all have failed to correct the issue and even tried to rebuild WMI.

Edward Pamias

I found this, which may help. See info below.

    Run gpedit.msc.
    Go to computer configuration.
    Go to Administrative templates.
    Go to System.
    Go to User profiles.
    Enable “Set maximum wait time for the network if a user has a roaming user profile or remote home directory” and set to 0 seconds.

Open in new window

John

Is the hard drive busy during login? Probably.

Do a Disk Cleanup (Admin Tools) to delete temporary files. Select all options for deletion.
Then do a Disk Defrag (Admin Tools) to defragment the hard drive.

compdigit44

ASKER

Here is added information: While the workstation is blocked from all GP's in enabled Verbose GP logging and see the workstation is setting at the "apply computer settings" for a very long time.

The hard drive does not appear to be busy while the message is on screen

John

Try running System File Checker. From an Admin Command prompt, run SFC /SCANNOW and allow to complete. Restart and test.

If that does not work, compare to another like Windows 7 machine. If definitely the Windows 7 machine problem, then run a Windows 7 Repair Install

compdigit44

ASKER

I ran a gpresult /h and confirmed that no Computer GP settings are being applied???

Edward Pamias

I was reading this may be caused by a DNS issue. Have you checked that?

Edward Pamias

Here is the solution to the DNS issue if it exists.

Solution

    Ensure the system is pointing to a valid DNS server inside the domain.
        Open a command prompt.
            Windows 7 and earlier: At the Windows desktop Start menu, select Run, type cmd, then press Enter.
            Windows 8 and later: Hold the Windows key and press Q, and type cmd in the Search box. Click the Command prompt icon when displayed.
        Type ipconfig /all and make a note of the primary DNS server.
        Check the IP addresses listed as DNS server entries to ensure they represent functional DNS servers. (Proceed to Step 2 if the DNS server addresses are missing or unknown.)
        At the command prompt, type hostname to get the name of the local system.
        Type nslookup.
        At the nslookup prompt, enter the hostname of the system currently being accessed and ensure name resolution is successful.
        If name resolution fails, locate the IP address of a functional DNS server for the Windows domain of which this system is a member.
        Alternatively, while still at the nslookup prompt, type set type=ns and enter the domain name. The command will return the DNS servers for the domain.

    Configure DNS resolution on the client.
        If the client system TCP/IP configuration is DHCP-assigned, refer to the DHCP service management utility and check the TCP/IP address scope options to ensure it assigns valid DNS servers.
        If the client has a static IP address, configure it to use a valid DNS server.
            Open the Control Panel.
            Open the Network and Sharing Center applet.
            Click Change Adapter Settings on the left-hand side. Right-click the active network adapter and select Properties. Click TCP/IPv4 and select its Properties button. Then type the DNS server’s address in the Preferred DNS Server field.
            Click OK to close all properties windows, and close the Network and Sharing Center applet.

Open in new window

compdigit44

ASKER

I have read that to and applied my DNS server IP statically and no change..

Edward Pamias

And my previous suggestion would not work for you? That one is the most common used.

pgm554

Enable boot logging on the system and post log files:

Type 'msconfig' (without the apostophes) and press OK. Select the 'Boot' tab and tick the Boot log box. Close msconfig and restart. A boot log should be created in the C:\Windows\ntbtlog.txt (assuming windows is installed to that directory!)

compdigit44

ASKER

Thanks again for all of the help everyone, the boot log has been attached.
ntbtlog.txt

pgm554

If you logon to the local user account ,is the boot time any faster?

compdigit44

ASKER

The problem is not loggin g in but the long delay in just have the login prompt come up. If I boot into safe mode it is very fast though

pgm554

If you disconnect the Ethernet cable,any faster?

compdigit44

ASKER