Jump to content

Slow startup after logon


Recommended Posts

Posted

Re: Slow startup after logon

 

PATRICK wrote:

> Yes, even in safe mode it experiances the same length as normal

> startup.

 

In that case, I would make sure all your drivers are up to date. Don't

use Windows Update. Rather, use the manufacturers' Web sites.

> This thing just baffles me. I did notice when i did

> unsigned drivers i had a lot of avg files in my drivers file, i dont

> know if that has anything to do with it, but since my desktop has avg

> and it doesn't have the same problem. Which also leads me to believe

> it has something to do with the drivers i have, since those all boot

> up even in safe mode.

 

Ditto.

Guest John John
Posted

Re: Slow startup after logon

 

That (KB906485) is not where you should enable it, that is for a

different purpose. I should have called it "verbose messages" (instead

of verbose logging) but I pointed you the the proper articles earlier:

 

How to enable verbose startup, shutdown, logon, and logoff status

Messages in the Windows Server 2003 family

http://support.microsoft.com/kb/325376/

 

If you find nothing after doing the above the problem might be related

to the User Environment or GPO, you can enable User Environment logging

for further troubleshooting:

 

How to enable user environment debug logging in retail builds of Windows

http://support.microsoft.com/kb/221833

 

Try KB232376 first. After you enable verbose messages reboot the

computer, during the startup you will see on screen information telling

you what Windows is doing when it is starting the computer, with these

messages see if you can find out what it is that is causing the delay.

 

John

 

 

PATRICK wrote:

> Ok, i went into the regedit and setup the verbose logging. As far as the

> links you sent, i didnt quite understand what you were wantin me to do.

> Where can i view this verbose log file/post it here?

>

> thank you,

> patrick

>

> "Daave" wrote:

>

>

>>Patrick,

>>

>>The reason I had asked about overclocking is that one of your startup

>>processes (Nvcpl - rundll32.exe) can safely be permanently disabled.

>>It's only useful for overclockers. And as I mentioned before, a number

>>of your other processes can be safely permanently disabled as well. Use

>>Google. Also see:

>>

>>Startup Programs Database

>>http://www.bleepingcomputer.com/startups/

>>

>>TASK LIST PROGRAMS

>>http://www.answersthatwork.com/Tasklist_pages/tasklist.htm

>>

>>I still think you need to rule out startup issues with a more diligent

>>approach. Try clean boot troubleshooting:

>>

>>http://support.microsoft.com/kb/316434

>>

>>And I don't believe you answered John John's verbose logging question.

>>For more info:

>>

>>http://support.microsoft.com/kb/906485

>>

>>

>>

>>PATRICK wrote:

>>

>>>Daave's Question

>>>---------------------

>>>I thought you said you had disabled AVG. I suppose you re-enabled it.

>>>Is

>>>it the barebones antivirus or the deluxe suite, including the

>>>firewall?

>>>If the latter, it's conflicting with Zone Alarm. Also, have you

>>>disabled

>>>the Windows firewall?

>>>

>>>Unless you have malware disguised as a legit process, you seem clean.

>>>Search Google for details, but you'll see a number of these are not

>>>essential. Do you overclock? If not, the first one can be disabled.

>>>

>>>One trick is to disable half of these startup items and see if the

>>>slow

>>>startup is fixed. Then narrow it down further.

>>>

>>>Do you have AVG set up to automatically scan your hard drive? If so,

>>>when is it scheduled to do so?

>>>---------------------------------------------------------

>>>

>>>My Response

>>>I did disable all items on startup, and started the computer with no

>>>difference, so re-enabled all the stuff that i disabled, because it

>>>made no

>>>difference.

>>>There should be no conflicts because i dissabled ALL programs. The

>>>windows

>>>firewall is dissabled.

>>>I do not overclock.

>>>I also turned off auto scan with avg.

>>>

>>>I'm just baffled on what could be causing this.

>>>When i did search for this issue, which there is many answers to slow

>>>startup, the only one that really discribed my problem was an issue

>>>described

>>>by windows, and said that if too many/incorrect drivers were

>>>installed it

>>>could slow startup, but i really dont want to go in and tamper with my

>>>drivers, because im unsure of which are which.

>>

>>

>>>"John John" wrote:

>>>

>>>

>>>>You didn't answer Daave's last post (re: AVG) so we don't know

>>>>where you are at with your troubleshooting efforts. Did you enable

>>>>verbose loging?

>>

>>

>>

Posted

Re: Slow startup after logon

 

Ok, enabled verbose messages, and i notice after i logon, it pauses at the

blue logon screen with "starting" or "enabling Wlnotify.dll" than it moves

on, and i can see my background and wait there for my icons to load.

 

"John John" wrote:

> That (KB906485) is not where you should enable it, that is for a

> different purpose. I should have called it "verbose messages" (instead

> of verbose logging) but I pointed you the the proper articles earlier:

>

> How to enable verbose startup, shutdown, logon, and logoff status

> Messages in the Windows Server 2003 family

> http://support.microsoft.com/kb/325376/

>

> If you find nothing after doing the above the problem might be related

> to the User Environment or GPO, you can enable User Environment logging

> for further troubleshooting:

>

> How to enable user environment debug logging in retail builds of Windows

> http://support.microsoft.com/kb/221833

>

> Try KB232376 first. After you enable verbose messages reboot the

> computer, during the startup you will see on screen information telling

> you what Windows is doing when it is starting the computer, with these

> messages see if you can find out what it is that is causing the delay.

>

> John

>

>

> PATRICK wrote:

>

> > Ok, i went into the regedit and setup the verbose logging. As far as the

> > links you sent, i didnt quite understand what you were wantin me to do.

> > Where can i view this verbose log file/post it here?

> >

> > thank you,

> > patrick

> >

> > "Daave" wrote:

> >

> >

> >>Patrick,

> >>

> >>The reason I had asked about overclocking is that one of your startup

> >>processes (Nvcpl - rundll32.exe) can safely be permanently disabled.

> >>It's only useful for overclockers. And as I mentioned before, a number

> >>of your other processes can be safely permanently disabled as well. Use

> >>Google. Also see:

> >>

> >>Startup Programs Database

> >>http://www.bleepingcomputer.com/startups/

> >>

> >>TASK LIST PROGRAMS

> >>http://www.answersthatwork.com/Tasklist_pages/tasklist.htm

> >>

> >>I still think you need to rule out startup issues with a more diligent

> >>approach. Try clean boot troubleshooting:

> >>

> >>http://support.microsoft.com/kb/316434

> >>

> >>And I don't believe you answered John John's verbose logging question.

> >>For more info:

> >>

> >>http://support.microsoft.com/kb/906485

> >>

> >>

> >>

> >>PATRICK wrote:

> >>

> >>>Daave's Question

> >>>---------------------

> >>>I thought you said you had disabled AVG. I suppose you re-enabled it.

> >>>Is

> >>>it the barebones antivirus or the deluxe suite, including the

> >>>firewall?

> >>>If the latter, it's conflicting with Zone Alarm. Also, have you

> >>>disabled

> >>>the Windows firewall?

> >>>

> >>>Unless you have malware disguised as a legit process, you seem clean.

> >>>Search Google for details, but you'll see a number of these are not

> >>>essential. Do you overclock? If not, the first one can be disabled.

> >>>

> >>>One trick is to disable half of these startup items and see if the

> >>>slow

> >>>startup is fixed. Then narrow it down further.

> >>>

> >>>Do you have AVG set up to automatically scan your hard drive? If so,

> >>>when is it scheduled to do so?

> >>>---------------------------------------------------------

> >>>

> >>>My Response

> >>>I did disable all items on startup, and started the computer with no

> >>>difference, so re-enabled all the stuff that i disabled, because it

> >>>made no

> >>>difference.

> >>>There should be no conflicts because i dissabled ALL programs. The

> >>>windows

> >>>firewall is dissabled.

> >>>I do not overclock.

> >>>I also turned off auto scan with avg.

> >>>

> >>>I'm just baffled on what could be causing this.

> >>>When i did search for this issue, which there is many answers to slow

> >>>startup, the only one that really discribed my problem was an issue

> >>>described

> >>>by windows, and said that if too many/incorrect drivers were

> >>>installed it

> >>>could slow startup, but i really dont want to go in and tamper with my

> >>>drivers, because im unsure of which are which.

> >>

> >>

> >>>"John John" wrote:

> >>>

> >>>

> >>>>You didn't answer Daave's last post (re: AVG) so we don't know

> >>>>where you are at with your troubleshooting efforts. Did you enable

> >>>>verbose loging?

> >>

> >>

> >>

>

Guest John John
Posted

Re: Slow startup after logon

 

How long does it pause at enabling Wlnotify.dll? Is the logon delay

there or is it after, when loading the desktop?

 

Try http://support.microsoft.com/kb/221833

 

Use Registry Editor to add or to modify the following registry entry:

Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows

NT\CurrentVersion\Winlogon

Entry: UserEnvDebugLevel

Type: REG_DWORD

Value data: 10002 (Hexadecimal)

 

After you reboot look for the file Userenv.log int the

%Systemroot%\Debug\UserMode\ folder. The events in there are listed

down to milliseconds. The time will be shown like so: hh:hh:ss:mss or

something like this: 19:29:52:862 which means 19 hour 29 minute 52

seconds 862 milliseconds. Is there a significant time delay shown in

the log? From start to end does it record for several minutes? If yes

do you see where the delay is?

 

John

 

PATRICK wrote:

> Ok, enabled verbose messages, and i notice after i logon, it pauses at the

> blue logon screen with "starting" or "enabling Wlnotify.dll" than it moves

> on, and i can see my background and wait there for my icons to load.

>

> "John John" wrote:

>

>

>>That (KB906485) is not where you should enable it, that is for a

>>different purpose. I should have called it "verbose messages" (instead

>>of verbose logging) but I pointed you the the proper articles earlier:

>>

>>How to enable verbose startup, shutdown, logon, and logoff status

>>Messages in the Windows Server 2003 family

>>http://support.microsoft.com/kb/325376/

>>

>>If you find nothing after doing the above the problem might be related

>>to the User Environment or GPO, you can enable User Environment logging

>>for further troubleshooting:

>>

>>How to enable user environment debug logging in retail builds of Windows

>>http://support.microsoft.com/kb/221833

>>

>>Try KB232376 first. After you enable verbose messages reboot the

>>computer, during the startup you will see on screen information telling

>>you what Windows is doing when it is starting the computer, with these

>>messages see if you can find out what it is that is causing the delay.

>>

>>John

>>

>>

>>PATRICK wrote:

>>

>>

>>>Ok, i went into the regedit and setup the verbose logging. As far as the

>>>links you sent, i didnt quite understand what you were wantin me to do.

>>>Where can i view this verbose log file/post it here?

>>>

>>>thank you,

>>>patrick

>>>

>>>"Daave" wrote:

>>>

>>>

>>>

>>>>Patrick,

>>>>

>>>>The reason I had asked about overclocking is that one of your startup

>>>>processes (Nvcpl - rundll32.exe) can safely be permanently disabled.

>>>>It's only useful for overclockers. And as I mentioned before, a number

>>>>of your other processes can be safely permanently disabled as well. Use

>>>>Google. Also see:

>>>>

>>>>Startup Programs Database

>>>>http://www.bleepingcomputer.com/startups/

>>>>

>>>>TASK LIST PROGRAMS

>>>>http://www.answersthatwork.com/Tasklist_pages/tasklist.htm

>>>>

>>>>I still think you need to rule out startup issues with a more diligent

>>>>approach. Try clean boot troubleshooting:

>>>>

>>>>http://support.microsoft.com/kb/316434

>>>>

>>>>And I don't believe you answered John John's verbose logging question.

>>>>For more info:

>>>>

>>>>http://support.microsoft.com/kb/906485

>>>>

>>>>

>>>>

>>>>PATRICK wrote:

>>>>

>>>>

>>>>>Daave's Question

>>>>>---------------------

>>>>>I thought you said you had disabled AVG. I suppose you re-enabled it.

>>>>>Is

>>>>>it the barebones antivirus or the deluxe suite, including the

>>>>>firewall?

>>>>>If the latter, it's conflicting with Zone Alarm. Also, have you

>>>>>disabled

>>>>>the Windows firewall?

>>>>>

>>>>>Unless you have malware disguised as a legit process, you seem clean.

>>>>>Search Google for details, but you'll see a number of these are not

>>>>>essential. Do you overclock? If not, the first one can be disabled.

>>>>>

>>>>>One trick is to disable half of these startup items and see if the

>>>>>slow

>>>>>startup is fixed. Then narrow it down further.

>>>>>

>>>>>Do you have AVG set up to automatically scan your hard drive? If so,

>>>>>when is it scheduled to do so?

>>>>>---------------------------------------------------------

>>>>>

>>>>>My Response

>>>>>I did disable all items on startup, and started the computer with no

>>>>>difference, so re-enabled all the stuff that i disabled, because it

>>>>>made no

>>>>>difference.

>>>>>There should be no conflicts because i dissabled ALL programs. The

>>>>>windows

>>>>>firewall is dissabled.

>>>>>I do not overclock.

>>>>>I also turned off auto scan with avg.

>>>>>

>>>>>I'm just baffled on what could be causing this.

>>>>>When i did search for this issue, which there is many answers to slow

>>>>>startup, the only one that really discribed my problem was an issue

>>>>>described

>>>>>by windows, and said that if too many/incorrect drivers were

>>>>>installed it

>>>>>could slow startup, but i really dont want to go in and tamper with my

>>>>>drivers, because im unsure of which are which.

>>>>

>>>>

>>>>>"John John" wrote:

>>>>>

>>>>>

>>>>>

>>>>>>You didn't answer Daave's last post (re: AVG) so we don't know

>>>>>>where you are at with your troubleshooting efforts. Did you enable

>>>>>>verbose loging?

>>>>

>>>>

>>>>

Posted

Re: Slow startup after logon

 

Its on the Wlnotify.dll for maybe 45 seconds, and then it closes the login

screen and shows my background, but pauses there for a while as well. I'll

try the userenv.log and post the results

 

"John John" wrote:

> How long does it pause at enabling Wlnotify.dll? Is the logon delay

> there or is it after, when loading the desktop?

>

> Try http://support.microsoft.com/kb/221833

>

> Use Registry Editor to add or to modify the following registry entry:

> Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows

> NT\CurrentVersion\Winlogon

> Entry: UserEnvDebugLevel

> Type: REG_DWORD

> Value data: 10002 (Hexadecimal)

>

> After you reboot look for the file Userenv.log int the

> %Systemroot%\Debug\UserMode\ folder. The events in there are listed

> down to milliseconds. The time will be shown like so: hh:hh:ss:mss or

> something like this: 19:29:52:862 which means 19 hour 29 minute 52

> seconds 862 milliseconds. Is there a significant time delay shown in

> the log? From start to end does it record for several minutes? If yes

> do you see where the delay is?

>

> John

>

> PATRICK wrote:

>

> > Ok, enabled verbose messages, and i notice after i logon, it pauses at the

> > blue logon screen with "starting" or "enabling Wlnotify.dll" than it moves

> > on, and i can see my background and wait there for my icons to load.

> >

> > "John John" wrote:

> >

> >

> >>That (KB906485) is not where you should enable it, that is for a

> >>different purpose. I should have called it "verbose messages" (instead

> >>of verbose logging) but I pointed you the the proper articles earlier:

> >>

> >>How to enable verbose startup, shutdown, logon, and logoff status

> >>Messages in the Windows Server 2003 family

> >>http://support.microsoft.com/kb/325376/

> >>

> >>If you find nothing after doing the above the problem might be related

> >>to the User Environment or GPO, you can enable User Environment logging

> >>for further troubleshooting:

> >>

> >>How to enable user environment debug logging in retail builds of Windows

> >>http://support.microsoft.com/kb/221833

> >>

> >>Try KB232376 first. After you enable verbose messages reboot the

> >>computer, during the startup you will see on screen information telling

> >>you what Windows is doing when it is starting the computer, with these

> >>messages see if you can find out what it is that is causing the delay.

> >>

> >>John

> >>

> >>

> >>PATRICK wrote:

> >>

> >>

> >>>Ok, i went into the regedit and setup the verbose logging. As far as the

> >>>links you sent, i didnt quite understand what you were wantin me to do.

> >>>Where can i view this verbose log file/post it here?

> >>>

> >>>thank you,

> >>>patrick

> >>>

> >>>"Daave" wrote:

> >>>

> >>>

> >>>

> >>>>Patrick,

> >>>>

> >>>>The reason I had asked about overclocking is that one of your startup

> >>>>processes (Nvcpl - rundll32.exe) can safely be permanently disabled.

> >>>>It's only useful for overclockers. And as I mentioned before, a number

> >>>>of your other processes can be safely permanently disabled as well. Use

> >>>>Google. Also see:

> >>>>

> >>>>Startup Programs Database

> >>>>http://www.bleepingcomputer.com/startups/

> >>>>

> >>>>TASK LIST PROGRAMS

> >>>>http://www.answersthatwork.com/Tasklist_pages/tasklist.htm

> >>>>

> >>>>I still think you need to rule out startup issues with a more diligent

> >>>>approach. Try clean boot troubleshooting:

> >>>>

> >>>>http://support.microsoft.com/kb/316434

> >>>>

> >>>>And I don't believe you answered John John's verbose logging question.

> >>>>For more info:

> >>>>

> >>>>http://support.microsoft.com/kb/906485

> >>>>

> >>>>

> >>>>

> >>>>PATRICK wrote:

> >>>>

> >>>>

> >>>>>Daave's Question

> >>>>>---------------------

> >>>>>I thought you said you had disabled AVG. I suppose you re-enabled it.

> >>>>>Is

> >>>>>it the barebones antivirus or the deluxe suite, including the

> >>>>>firewall?

> >>>>>If the latter, it's conflicting with Zone Alarm. Also, have you

> >>>>>disabled

> >>>>>the Windows firewall?

> >>>>>

> >>>>>Unless you have malware disguised as a legit process, you seem clean.

> >>>>>Search Google for details, but you'll see a number of these are not

> >>>>>essential. Do you overclock? If not, the first one can be disabled.

> >>>>>

> >>>>>One trick is to disable half of these startup items and see if the

> >>>>>slow

> >>>>>startup is fixed. Then narrow it down further.

> >>>>>

> >>>>>Do you have AVG set up to automatically scan your hard drive? If so,

> >>>>>when is it scheduled to do so?

> >>>>>---------------------------------------------------------

> >>>>>

> >>>>>My Response

> >>>>>I did disable all items on startup, and started the computer with no

> >>>>>difference, so re-enabled all the stuff that i disabled, because it

> >>>>>made no

> >>>>>difference.

> >>>>>There should be no conflicts because i dissabled ALL programs. The

> >>>>>windows

> >>>>>firewall is dissabled.

> >>>>>I do not overclock.

> >>>>>I also turned off auto scan with avg.

> >>>>>

> >>>>>I'm just baffled on what could be causing this.

> >>>>>When i did search for this issue, which there is many answers to slow

> >>>>>startup, the only one that really discribed my problem was an issue

> >>>>>described

> >>>>>by windows, and said that if too many/incorrect drivers were

> >>>>>installed it

> >>>>>could slow startup, but i really dont want to go in and tamper with my

> >>>>>drivers, because im unsure of which are which.

> >>>>

> >>>>

> >>>>>"John John" wrote:

> >>>>>

> >>>>>

> >>>>>

> >>>>>>You didn't answer Daave's last post (re: AVG) so we don't know

> >>>>>>where you are at with your troubleshooting efforts. Did you enable

> >>>>>>verbose loging?

> >>>>

> >>>>

> >>>>

>

Posted

Re: Slow startup after logon

 

Ok, so i restarted and it was like 2 minutes at the executing Wlnotify.dll

 

Posted the userenv log on the following site, since it was way to long to

fit on here

You can just download it, its an exact copy of the log

http://www.tunerworldstreet.com/Jeep/userenv.log

Posted

Re: Slow startup after logon

 

PATRICK wrote:

> Ok, so i restarted and it was like 2 minutes at the executing

> Wlnotify.dll

 

Do you have ZoneAlarm installed by any chance?

Guest John John
Posted

Re: Slow startup after logon

 

I get a "Page Not Found" at that address. The wait at wlnotify.dll

seems quite long, I'm not sure why it would wait 2 minutes there. Are

any errors recorded in the Event Log? Could you confirm to us again if

the same delay happens when you start the computer in Safe-Mode?

 

John

 

PATRICK wrote:

> Ok, so i restarted and it was like 2 minutes at the executing Wlnotify.dll

>

> Posted the userenv log on the following site, since it was way to long to

> fit on here

> You can just download it, its an exact copy of the log

> http://www.tunerworldstreet.com/Jeep/userenv.log

×
×
  • Create New...