Slow logon to desktop - winlogon ?

[+Bob+]

I have a Win2KPro system that spends a long time starting up before
the desktop becomes active. That is, it puts the desktop up fairly
quickly after logon, but it takes a couple minutes before the system
is really ready for the user to interact.

You can see the hard drive access running wild while you wait. A check
in task manager shows that winlogon is using 25-40% of the CPU during
this time.

It acts like a system that lacks disk space and/or memory, but there's
10gb free on both drives and 500m main memory - that's always been
plenty in my other win2K systems. Swap files are 766/2048. The main
memory has around 300m used while it's doing the slow log on.

There are only a few programs starting up (AVG, ZA firewall, K9) and
they don't appear to be using any CPU time at all while I wait... it's
all going to winlogon. There's no AD on the network, logons are simple
local logons with two network drives being hooked up to a server via
matching user/pass on the server (no user interaction at logon).

Any idea what I should look at? I do have the improved process mgmt
tool that I could install to get a better idea of what is using the
time (assuming I know what to look for and can interpret it

Thanks,

 

[Frank Booth Snr]

I have a Win2KPro system that spends a long time starting up before
the desktop becomes active. That is, it puts the desktop up fairly
quickly after logon, but it takes a couple minutes before the system
is really ready for the user to interact.

You can see the hard drive access running wild while you wait. A check
in task manager shows that winlogon is using 25-40% of the CPU during
this time.

It acts like a system that lacks disk space and/or memory, but there's
10gb free on both drives and 500m main memory - that's always been
plenty in my other win2K systems. Swap files are 766/2048. The main
memory has around 300m used while it's doing the slow log on.

There are only a few programs starting up (AVG, ZA firewall, K9) and
they don't appear to be using any CPU time at all while I wait... it's
all going to winlogon. There's no AD on the network, logons are simple
local logons with two network drives being hooked up to a server via
matching user/pass on the server (no user interaction at logon).

Any idea what I should look at? I do have the improved process mgmt
tool that I could install to get a better idea of what is using the
time (assuming I know what to look for and can interpret it

There are a number of ways of dealing with this, I would download
msconfig.exe (it is not included with Win2k). Then do what is known as a
"clean boot" to begin with.

Read http://support.microsoft.com/?id=310353 first

Although the articla describes this for WinXP it's the same procedure
for Win2k. If the pc now boots up faster then you know it has to be one
(or more) applications under the MSConfig Startup tab that is causing
the problem.

 

[+Bob+]

There are a number of ways of dealing with this, I would download
msconfig.exe (it is not included with Win2k). Then do what is known as a
"clean boot" to begin with.

Read http://support.microsoft.com/?id=310353 first

Although the articla describes this for WinXP it's the same procedure
for Win2k. If the pc now boots up faster then you know it has to be one
(or more) applications under the MSConfig Startup tab that is causing
the problem.

Thanks, I will give that a shot and see what happens.