Vista takes 55 minutes to shutdown

[Juan I. Cahis]

Dear friends:

Yesterday, after I finished to give a presentation to a group of
executives of the Company I work for, I ordered my Vista equipped
notebook to shutdown (Vista 32 bits, Business).

The process took 55 (fifty five) minutes to complete, and during that
period of time, only the "logging off" message (and the hourglass)
were displayed. The hard disk computer light was blinking all the
time, so I didn't wanted to power it down to avoid any data loss. No
other message was displayed, so I didn't have any idea of what Vista
was doing.

Do the brains of Redmond think that their users should spend almost an
hour after any presentation in order to make it more productive? Why
they don't make Vista to inform the user what is happening, and to
suggest what to do in order to accelerate the shutdown process?

Does somebody know how to handle this kind of problem?

Vista is very nice, but I am becoming bored of it, I think that
Microsoft's idea of building a mainframe operating system for normal
executive's notebooks doesn't works.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Bill Yanaire]

Maybe your system was installing some updates or a process froze. I have
Vista Ultimate on two PC's and they shutdown within a minute unless there
are updates. One time it took 20 minutes, but there was a message saying,
"Please don't shut off the PC, installing updates"


Dear friends:

Yesterday, after I finished to give a presentation to a group of
executives of the Company I work for, I ordered my Vista equipped
notebook to shutdown (Vista 32 bits, Business).

The process took 55 (fifty five) minutes to complete, and during that
period of time, only the "logging off" message (and the hourglass)
were displayed. The hard disk computer light was blinking all the
time, so I didn't wanted to power it down to avoid any data loss. No
other message was displayed, so I didn't have any idea of what Vista
was doing.

Do the brains of Redmond think that their users should spend almost an
hour after any presentation in order to make it more productive? Why
they don't make Vista to inform the user what is happening, and to
suggest what to do in order to accelerate the shutdown process?

Does somebody know how to handle this kind of problem?

Vista is very nice, but I am becoming bored of it, I think that
Microsoft's idea of building a mainframe operating system for normal
executive's notebooks doesn't works.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Adam Albright]

Dear friends:

Yesterday, after I finished to give a presentation to a group of
executives of the Company I work for, I ordered my Vista equipped
notebook to shutdown (Vista 32 bits, Business).

When Windows "hangs" after you told it to shut down the likely cause
is one or more applications, services or some process is still telling
Windows it is "busy" so Windows in effect waits, and waits and waits
some more for the application to let got of the handle usually to some
Registry link. No, this isn't suppose to happen. A normal shutdown
shouldn't take more than a minute or two. Five minutes tops and only
that long if Windows is installing some update then tells you to wait.

As a general rule you should "help" Windows shut down by manually
closing each application BEFORE you begin the shut down process. Don't
leave any applications showing on the task bar either. Shut them down.

This can be an annoying problem since Windows by this time has
probably already entered a catatonic state and trying to help it shut
down by forcing whenever is hanging by trying to bring up Task Manager
to nuke the offending process often no longer works.

So you did the right thing if you see disk activity... just wait as
annoying as it is. If you see no disk activity after a minute or two
you can just force a shut down by hitting the power switch. This may
cause Windows' shut down flag to not get set as it does in a
successful shutdown, so it may do a disk scan the next time you boot
or bring up some screen telling you about it and asking if you want to
boot into safe mode. Generally you don't have to. For what it's worth
XP did this too. One in a long list of stupid programming mistakes
Microsoft never seems to get around to fixing. Once you tell the OS to
shut down it should have the "smarts" to one by one kick everything
running out of memory once there is no longer any disk activity.

Of course Microsoft has never been known for it's programming skills.
I mean 50 million lines of code in Vista? It took way less than that
to get men to the moon and back.

 

[Guest]

Hola Juan,

Suggest cleaning up the system (clearing out all the Temp/Tmp folders,
clearing the browser TIF, doing a Disk CleanUp, Defragging, etc.) and then
running CHKDSK / R

Buena suerte

 

[Don]

Dear friends:

Yesterday, after I finished to give a presentation to a group of
executives of the Company I work for, I ordered my Vista equipped
notebook to shutdown (Vista 32 bits, Business).

The process took 55 (fifty five) minutes to complete, and during that
period of time, only the "logging off" message (and the hourglass)
were displayed. The hard disk computer light was blinking all the
time, so I didn't wanted to power it down to avoid any data loss. No
other message was displayed, so I didn't have any idea of what Vista
was doing...

There may be an error message which explains the delay in the Event
Viewer (Start-->Find and type 'event'). You will need to spend some
time just getting oriented in the Event Viewer because there is so
much information there. Once you know how to find what you need you
will be glad you spent the time.

 

[Guest]

I am glad to see that you "ordered" it to shut down!

You don't think that it just might have something to do with the
presentation that you were doing?
Either you never closed the program properly, or it malfunctioned.

You are too, too quick to blame vista, and anything else, rather than
yourself.

Vista is very reliable( I admit under protest);, so, the fault lies with
your operation of a computer

 

[Juan I. Cahis]

Dear Mick, I don't doubt of Vista's technical quality, I think that it
should give more info to the user of what is it doing, or ask the user
for alternatives.

For example, when I asked Vista to shut down, I would have liked a lot
to have been able to read a message like this one: "Vista will need to
correct some issues (or to install some updates) when shutting down
and that will take a long period of time. Would you like to hibernate
now, instead of shutting down, and to postpone the necessary
correction process to a later time?" (Please remember that I am not
very fluent in English, but I expect that you got the idea).

I think that they are some issues with Vista, like this one, that
makes it not very user oriented instead of a technical marvel only.

I am glad to see that you "ordered" it to shut down!

You don't think that it just might have something to do with the
presentation that you were doing?
Either you never closed the program properly, or it malfunctioned.

You are too, too quick to blame vista, and anything else, rather than
yourself.

Vista is very reliable( I admit under protest);, so, the fault lies with
your operation of a computer

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Don]

Juan I. Cahis wrote:
....

For example, when I asked Vista to shut down, I would have liked a lot
to have been able to read a message like this one: "Vista will need to
correct some issues (or to install some updates) when shutting down
and that will take a long period of time. Would you like to hibernate
now, instead of shutting down, and to postpone the necessary
correction process to a later time?" (Please remember that I am not
very fluent in English, but I expect that you got the idea).

I think that they are some issues with Vista, like this one, that
makes it not very user oriented instead of a technical marvel only.

Those 'issues' are better known as 'bugs' ;o) They need to be fixed,
and they will be fixed -- but don't ask me when. Taking 55 minutes
to shut down (I can say with confidence) is a bug.

Did you look at the event logs to see if Vista reported the reason
for the delay? It usually does.

 

[Juan I. Cahis]

Dear friends, I found a lot of "Information" events of this type, does
somebody understand them? Here they are:

Log Name: System
Source: yukonwlh
Date: 21-Jun-07 7:46:39 AM
Event ID: 126
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JicNBK4
Description:
Link Partner is not Auto-Negotiation able
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="yukonwlh" />
<EventID Qualifiers="24583">126</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-06-21T11:46:39.059Z" />
<EventRecordID>26261</EventRecordID>
<Channel>System</Channel>
<Computer>JicNBK4</Computer>
<Security />
</System>
<EventData>
<Data>\Device\NDMP7</Data>
<Data>\DEVICE\{0CFF78BA-14F3-4F45-9E38-A8F5511EA247}</Data>

<Binary>0000000002003000000000007E000760000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Juan I. Cahis wrote:
...

Those 'issues' are better known as 'bugs' ;o) They need to be fixed,
and they will be fixed -- but don't ask me when. Taking 55 minutes
to shut down (I can say with confidence) is a bug.

Did you look at the event logs to see if Vista reported the reason
for the delay? It usually does.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Jane C]

yukonwlh NDIS6.0 Miniport Driver for Marvell Yukon Ethernet Controller

It would appear to be a problem with your NIC - do you have the latest
drivers installed for it?

--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation ;-)
MVP Windows Shell/User

Dear friends, I found a lot of "Information" events of this type, does
somebody understand them? Here they are:

Log Name: System
Source: yukonwlh
Date: 21-Jun-07 7:46:39 AM
Event ID: 126
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JicNBK4
Description:
Link Partner is not Auto-Negotiation able
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="yukonwlh" />
<EventID Qualifiers="24583">126</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-06-21T11:46:39.059Z" />
<EventRecordID>26261</EventRecordID>
<Channel>System</Channel>
<Computer>JicNBK4</Computer>
<Security />
</System>
<EventData>
<Data>\Device\NDMP7</Data>
<Data>\DEVICE\{0CFF78BA-14F3-4F45-9E38-A8F5511EA247}</Data>

<Binary>0000000002003000000000007E000760000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Juan I. Cahis wrote:
...

Those 'issues' are better known as 'bugs' ;o) They need to be fixed,
and they will be fixed -- but don't ask me when. Taking 55 minutes
to shut down (I can say with confidence) is a bug.

Did you look at the event logs to see if Vista reported the reason
for the delay? It usually does.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

Dear Jane, is this NIC the one that installs when one syncs a WM5
PocketPC for the first time, or is it a standard NIC that ends in a
RJ45 jack?

yukonwlh NDIS6.0 Miniport Driver for Marvell Yukon Ethernet Controller

It would appear to be a problem with your NIC - do you have the latest
drivers installed for it?

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Jane C]

The Marvell Yukon NIC is most likely inbuilt on your motherboard - RJ45
connection.

--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation ;-)
MVP Windows Shell/User

Dear Jane, is this NIC the one that installs when one syncs a WM5
PocketPC for the first time, or is it a standard NIC that ends in a
RJ45 jack?

yukonwlh NDIS6.0 Miniport Driver for Marvell Yukon Ethernet Controller

It would appear to be a problem with your NIC - do you have the latest
drivers installed for it?

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

And then, I have a problem because according the computer's specs, I
don't have a Marvel Yukon NIC, but an Intel Gigabit NIC. So, Vista
installed the wrong driver.

How can I do to uninstall it (I know how to do it), and to avoid that
Vista will not install it again (I don't know how to do it), but it
will install the correct Intel driver instead?

I assume that a solution could be to rename the ".INF" file of the
Marvel Yukon NIC, but does somebody know the name of this file and
where is it located?

The Marvell Yukon NIC is most likely inbuilt on your motherboard - RJ45
connection.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Jane C]

Hello Juan,

If you go to Device Manager, what NICs are listed there? What drivers does
Device Manager have listed for them?

--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation ;-)
MVP Windows Shell/User

And then, I have a problem because according the computer's specs, I
don't have a Marvel Yukon NIC, but an Intel Gigabit NIC. So, Vista
installed the wrong driver.

How can I do to uninstall it (I know how to do it), and to avoid that
Vista will not install it again (I don't know how to do it), but it
will install the correct Intel driver instead?

I assume that a solution could be to rename the ".INF" file of the
Marvel Yukon NIC, but does somebody know the name of this file and
where is it located?

The Marvell Yukon NIC is most likely inbuilt on your motherboard - RJ45
connection.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

Dear Jane, it list the Yukon Marvel driver, but I know that I have an
Intel Gigabit device instead.

Hello Juan,

If you go to Device Manager, what NICs are listed there? What drivers does
Device Manager have listed for them?

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Jane C]

Hi Juan,

What make and model of motherboard do you have? Make and model of pc?
If you do indeed have an Intel Gigabit NIC, it most likely would not even be
working with Marvel Yukon drivers, so perhaps it has 2 onboard NICs?

--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation ;-)
MVP Windows Shell/User

Dear Jane, it list the Yukon Marvel driver, but I know that I have an
Intel Gigabit device instead.

Hello Juan,

If you go to Device Manager, what NICs are listed there? What drivers
does
Device Manager have listed for them?

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

Dear Jane, you were correct, an extra Yukon NIC existed. The problem
was that two ".INF" files related to this product existed in the
"C:\WINDOWS\INF" folder, and Vista choose the old one instead of the
latest one.

I took the opportunity to download an even newer driver set from the
manufacturer WEB site, and apparently, the problem was solved.

I must to confess that I never use wired networking on my PCs, so I
had no idea about how many NICs I had in my PCs, and if were working
OK or not. I use wireless networking only.

Hi Juan,

What make and model of motherboard do you have? Make and model of pc?
If you do indeed have an Intel Gigabit NIC, it most likely would not even be
working with Marvel Yukon drivers, so perhaps it has 2 onboard NICs?

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!