Jesus wrote:

> What you say about having a list of the websites visted just before
> experiencing the problem... is something impossible to remember.

It might be in the browers history,
also perhaps in the ie temp folder (often you get cookies).
That is just my suspicion so far...needs verification.

> Because when you buy Vista you think it's a finished product (TESTED) then
> you dont expect that this error can happen, so you are not all the time with
> a paper, a pencil and all the patience, writting all the websites to
> communicate them to Microsoft.

It might not be Vista/IE but something new online or a very
badly coded website..the browser does work but when you
bang into something unexpected it isn't invulnerable.

> So the thing is we have some icons useless (you click on them, and we dont
> have a response) and we have to communicate this to Microsoft in order to
> help them to solve the problem.

Well..they can't solve very many problems unless they
get enough data to reproduce the problem and see for
themselves if it's Vista, IE, some active scripting or
an optional plugin for IE that has nothing todo with MS.

> Now, how can we do this?

Have to wait and fish...test your desktop as you go
along the internet, or leave it alone and hope someone
else will trip over a solution.

> Is there any MS MVP to contact?

The MS MVP are really like you and I but more experienced
in some areas...they can't help unless they see it happen.

> Is there any way to explain the problem to the Customer Experience Feedback
> from Microsoft?

I don't know, unless it show up in your admin event log
and then you'd have something to relate.

> Thanks

A more specific group like
hey...I can't tell, ng listing not complete here. lol
something ending with Vista.IE

NT Canuck
'Seek and ye shall find'