Vista Tutorial - 10 Minutes to Boot Up

I have Vista Business installed on my Dell Core 2 Duo laptop. I bought the
laptop a few weeks after Vista was launched and had it preinstalled.

My laptop is part of a business network and I hadn't had this problem until
just a couple of weeks ago.

When I log into my laptop from anywhere not connected to my business
network, it boots rather quickly.

When I have it connected to my business network and log in, the log in takes
10 minutes. It's an exact 10 minutes so this tells me that something is set
to time out after 10 minutes. From what I can see in the event logs it
appears this is the culprit.
-----------------------
Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 4/25/2007 8:38:57 AM
Event ID: 6006
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: JimDLaptop.DOMAIN.com
Description:
The winlogon notification subscriber <GPClient> took 599 second(s) to handle
the notification event (StartShell).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Winlogon"
Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
<EventID Qualifiers="32768">6006</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-04-25T15:38:57.000Z" />
<EventRecordID>5520</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JimDLaptop.DOMAIN.com</Computer>
<Security />
</System>
<EventData>
<Data>GPClient</Data>
<Data>599</Data>
<Data>StartShell</Data>
<Binary>04000000</Binary>
</EventData>
</Event>
-----------------------

In case it matters our AD servers are running Windows 2000.

"Jim De Vico" wrote:

> I have Vista Business installed on my Dell Core 2 Duo laptop. I bought the
> laptop a few weeks after Vista was launched and had it preinstalled.
>
> My laptop is part of a business network and I hadn't had this problem until
> just a couple of weeks ago.
>
> When I log into my laptop from anywhere not connected to my business
> network, it boots rather quickly.
>
> When I have it connected to my business network and log in, the log in takes
> 10 minutes. It's an exact 10 minutes so this tells me that something is set
> to time out after 10 minutes. From what I can see in the event logs it
> appears this is the culprit.
> -----------------------
> Log Name: Application
> Source: Microsoft-Windows-Winlogon
> Date: 4/25/2007 8:38:57 AM
> Event ID: 6006
> Task Category: None
> Level: Warning
> Keywords: Classic
> User: N/A
> Computer: JimDLaptop.DOMAIN.com
> Description:
> The winlogon notification subscriber <GPClient> took 599 second(s) to handle
> the notification event (StartShell).
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-Winlogon"
> Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
> <EventID Qualifiers="32768">6006</EventID>
> <Version>0</Version>
> <Level>3</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2007-04-25T15:38:57.000Z" />
> <EventRecordID>5520</EventRecordID>
> <Correlation />
> <Execution ProcessID="0" ThreadID="0" />
> <Channel>Application</Channel>
> <Computer>JimDLaptop.DOMAIN.com</Computer>
> <Security />
> </System>
> <EventData>
> <Data>GPClient</Data>
> <Data>599</Data>
> <Data>StartShell</Data>
> <Binary>04000000</Binary>
> </EventData>
> </Event>
> -----------------------
>
> In case it matters our AD servers are running Windows 2000.

Sorry for not asking a question but does anyone know why Vista is taking
this 10 minutes to log in and how I can fix it?

Thanks.

Jim

Have you checked for rogue programs that are starting with the operating
system? Run msconfig and disable everything there except for your security
software. Antivirus and Windows defender. If that fixes the problem then
re-enable each item one at a time and reboot each time. If the problem comes
back then you know it was the last item you re-enabled.

If you can narrow it down then re-post here and I am sure someone can help
you out further.

"Jim De Vico" <Jim De Vico@discussions.microsoft.com> wrote in message
news:B4455A1D-6104-432D-AB50-AB0A5D17E5A0@microsoft.com...
>I have Vista Business installed on my Dell Core 2 Duo laptop. I bought the
> laptop a few weeks after Vista was launched and had it preinstalled.
>
> My laptop is part of a business network and I hadn't had this problem
> until
> just a couple of weeks ago.
>
> When I log into my laptop from anywhere not connected to my business
> network, it boots rather quickly.
>
> When I have it connected to my business network and log in, the log in
> takes
> 10 minutes. It's an exact 10 minutes so this tells me that something is
> set
> to time out after 10 minutes. From what I can see in the event logs it
> appears this is the culprit.
> -----------------------
> Log Name: Application
> Source: Microsoft-Windows-Winlogon
> Date: 4/25/2007 8:38:57 AM
> Event ID: 6006
> Task Category: None
> Level: Warning
> Keywords: Classic
> User: N/A
> Computer: JimDLaptop.DOMAIN.com
> Description:
> The winlogon notification subscriber <GPClient> took 599 second(s) to
> handle
> the notification event (StartShell).
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-Winlogon"
> Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy"
> />
> <EventID Qualifiers="32768">6006</EventID>
> <Version>0</Version>
> <Level>3</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2007-04-25T15:38:57.000Z" />
> <EventRecordID>5520</EventRecordID>
> <Correlation />
> <Execution ProcessID="0" ThreadID="0" />
> <Channel>Application</Channel>
> <Computer>JimDLaptop.DOMAIN.com</Computer>
> <Security />
> </System>
> <EventData>
> <Data>GPClient</Data>
> <Data>599</Data>
> <Data>StartShell</Data>
> <Binary>04000000</Binary>
> </EventData>
> </Event>
> -----------------------
>
> In case it matters our AD servers are running Windows 2000.

"Jim De Vico" wrote:

> "Jim De Vico" wrote:
>
> > I have Vista Business installed on my Dell Core 2 Duo laptop. I bought the
> > laptop a few weeks after Vista was launched and had it preinstalled.
> >
> > My laptop is part of a business network and I hadn't had this problem until
> > just a couple of weeks ago.
> >
> > When I log into my laptop from anywhere not connected to my business
> > network, it boots rather quickly.
> >
> > When I have it connected to my business network and log in, the log in takes
> > 10 minutes. It's an exact 10 minutes so this tells me that something is set
> > to time out after 10 minutes. From what I can see in the event logs it
> > appears this is the culprit.
> > -----------------------
> > Log Name: Application
> > Source: Microsoft-Windows-Winlogon
> > Date: 4/25/2007 8:38:57 AM
> > Event ID: 6006
> > Task Category: None
> > Level: Warning
> > Keywords: Classic
> > User: N/A
> > Computer: JimDLaptop.DOMAIN.com
> > Description:
> > The winlogon notification subscriber <GPClient> took 599 second(s) to handle
> > the notification event (StartShell).
> > Event Xml:
> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> > <System>
> > <Provider Name="Microsoft-Windows-Winlogon"
> > Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
> > <EventID Qualifiers="32768">6006</EventID>
> > <Version>0</Version>
> > <Level>3</Level>
> > <Task>0</Task>
> > <Opcode>0</Opcode>
> > <Keywords>0x80000000000000</Keywords>
> > <TimeCreated SystemTime="2007-04-25T15:38:57.000Z" />
> > <EventRecordID>5520</EventRecordID>
> > <Correlation />
> > <Execution ProcessID="0" ThreadID="0" />
> > <Channel>Application</Channel>
> > <Computer>JimDLaptop.DOMAIN.com</Computer>
> > <Security />
> > </System>
> > <EventData>
> > <Data>GPClient</Data>
> > <Data>599</Data>
> > <Data>StartShell</Data>
> > <Binary>04000000</Binary>
> > </EventData>
> > </Event>
> > -----------------------
> >
> > In case it matters our AD servers are running Windows 2000.
>
> Sorry for not asking a question but does anyone know why Vista is taking
> this 10 minutes to log in and how I can fix it?
>

I'm betting your DNS isn't set correctly. It should point to the DNS server
on the domain you connect to at work. if not it will have to wait for the
timeout before it searches and eventually finds your domain controller.


> Thanks.
>
> Jim

I know that it has been awhile since the last post here, but I have been searching for a solution to this problem for a long time and I believe I have found a solution. My computers are on a domain with Active directory. When they are not in a managed group, the log on is quick. When the machines are put into a managed group, it takes 599 seconds to load (10 minutes) the desktop. When I read the last post here regarding DNS, it prompted me to start looking at this, and this is where I saw the IPV6 checkbox. My DNS settings are automatically provided for me, but I added them anyway. BUT I also removed the checkbox for IPV6 (Since I'm using DHCP with IPV4) and then restarted the computer. The computer is now in the managed group in active directory and it's logging in quickly.
My reason for posting this is because I have not been able to find any documentation on this particular problem and I hope this will help someone else.
Since I started writing this post, I thought I would narrow it down some more. I removed the DNS settings and now they're set to automatically obtain, logged off and back on. It logged on instantly. So I'm fairly certian that it is the IPV6 checkbox causing this.

I had the same problem with my Asus notebook running Vista Premium, and experienced exactly the same symptoms with my notebook.

I later figured out that because I had an adapter for my MicroSD card in the built-in cardreader (it was simply the adapter to convert MicroSD to SD, the memory itself wasn't in the adapter) and this made Windows spend time to look for the drive itself. I removed this adapater and rebooted, and voila, problem solved.

Hope this helps you.