I have noticed a disturbing little trend in using Windows Vista Ultimate.
I'm noticing that when a program has stalled, and when I bring up the Task
Manager in order to force an application to quit, nothing comes as a result.



Meaning, Task Manager will bring about the normal processes involved in
force quitting/ending an application. After I have informed Task Manager
that yes I do indeed want to quit the application, ultimately the application
is never ended. It is never ultimately forced to quit. It just hangs on
there in its stalled state.

This doesn't happen the majority of the time, but I would say that it's
happening at least a third of the time... or more. And it happens with the
more memory intensive applications (Photoshop, Adobe Bridge, etc.)

Ultimately I have to completely restart the machine, which is very
frustrating.

Is anyone else noticing this emerging trend? Or is it just me?

Sometimes you must go into the process tab, identify the running process
associated with the program, and end the process from there. It usually
works.

--

Richard Urban
Microsoft MVP
Windows Desktop Experience



"husky86" <husky86@xxxxxx> wrote in message
news:E36F6B0A-53EC-4539-95ED-FC724A635BF3@xxxxxx

>I have noticed a disturbing little trend in using Windows Vista Ultimate.
> I'm noticing that when a program has stalled, and when I bring up the Task
> Manager in order to force an application to quit, nothing comes as a
> result.
>
> Meaning, Task Manager will bring about the normal processes involved in
> force quitting/ending an application. After I have informed Task Manager
> that yes I do indeed want to quit the application, ultimately the
> application
> is never ended. It is never ultimately forced to quit. It just hangs on
> there in its stalled state.
>
> This doesn't happen the majority of the time, but I would say that it's
> happening at least a third of the time... or more. And it happens with
> the
> more memory intensive applications (Photoshop, Adobe Bridge, etc.)
>
> Ultimately I have to completely restart the machine, which is very
> frustrating.
>
> Is anyone else noticing this emerging trend? Or is it just me?

"Richard Urban" <richardurbanREMOVETHIS@xxxxxx> wrote in message
news:u%23uA6h68IHA.4004@xxxxxx

> Sometimes you must go into the process tab, identify the running process
> associated with the program, and end the process from there. It usually
> works.

Yes, and the easiest way to find the right process is the right click on the
program in the Applications tab and select Go To Process.

ss.

Thanks for this info!

What happens when the process itself won't end? This also is happening more
often.


"Richard Urban" wrote:

> Sometimes you must go into the process tab, identify the running process
> associated with the program, and end the process from there. It usually
> works.
>
> --
>
> Richard Urban
> Microsoft MVP
> Windows Desktop Experience
>
>
>
> "husky86" <husky86@xxxxxx> wrote in message
> news:E36F6B0A-53EC-4539-95ED-FC724A635BF3@xxxxxx

> >I have noticed a disturbing little trend in using Windows Vista Ultimate.
> > I'm noticing that when a program has stalled, and when I bring up the Task
> > Manager in order to force an application to quit, nothing comes as a
> > result.
> >
> > Meaning, Task Manager will bring about the normal processes involved in
> > force quitting/ending an application. After I have informed Task Manager
> > that yes I do indeed want to quit the application, ultimately the
> > application
> > is never ended. It is never ultimately forced to quit. It just hangs on
> > there in its stalled state.
> >
> > This doesn't happen the majority of the time, but I would say that it's
> > happening at least a third of the time... or more. And it happens with
> > the
> > more memory intensive applications (Photoshop, Adobe Bridge, etc.)
> >
> > Ultimately I have to completely restart the machine, which is very
> > frustrating.
> >
> > Is anyone else noticing this emerging trend? Or is it just me?

>
>

Many thanks!


"Synapse Syndrome" wrote:

> "Richard Urban" <richardurbanREMOVETHIS@xxxxxx> wrote in message
> news:u%23uA6h68IHA.4004@xxxxxx

> > Sometimes you must go into the process tab, identify the running process
> > associated with the program, and end the process from there. It usually
> > works.

>
> Yes, and the easiest way to find the right process is the right click on the
> program in the Applications tab and select Go To Process.
>
> ss.
>
>
>

"husky86" <husky86@xxxxxx> wrote in message
news:8990C45F-B0B7-40B9-AE98-D25B900333FE@xxxxxx

> Thanks for this info!
>
> What happens when the process itself won't end? This also is happening
> more
> often.

I have never not been able to kill a process unless it completely freezes or
slows down the computer to a very slow crawl. There have been rare
occasions that I have needed to kill a rogue process like that through
another machine, with the Sysinternals PSKILL command, which can work
through network. You can also use it locally.

ss.