Beta Feedback responses from MS leave me questioning

[Guest]

I have made numerous beta feedback reports to MS about ongoing bugs and
problems I have with Vista. I'm finding a few days later I will get back an
automated response from MS saying they have closed or resolved the issue and
telling me I can click on the link in the message to learn more. However,
when I click on the link and log on with my passport info, I get the message
that I am not allowed to access the site, so I can't get any more info, and
the problem still exists. I don't know why or how they have "closed" it.
Anyone else have this experience? In one case they said it wasn't
repeatable, but it happens continually on my computer (ie. I get duplicate CD
drives listed in the folder window when I am working with files on a CD/RW).

Just wondering what is going on. Thanks

 

[Leen]

Those information is only accessible by technical betatesters. If you give
the report # I'll see if I can get more info (provided you made the report
Public when submitting it, otherwise only MS do have access those private
reports).

--
Leen
==> Please only reply in the newsgroup <==
*** This means, DO NOT send me Email also!!! ***

How to burn an ISO file :
http://iso.snoekonline.com/iso.htm

 

[Jupiter Jones [MVP]]

"wasn't repeatable"
That means they can not get this to occur on their computer.
That can be a tough one, it may be caused by hardware and/or software
specific to your system.

"resolved" means just that, but it may be resolved in a build currently
unavailable.
Even the Tech Beta testers may not yet have access to that build.

Have you performed another Clean Installation to verify the bug is not
caused by a bad installation?
That is what I have done before submitting any bug.

If you post the specifics of your bugs here, someone may be able to help
determine the cause.

 

[Guest]

I to received automated responses from Microsoft saying they resolved then
closed issues I reported and when I click the link I get the same message.
The latest response was on the Fingerprint Reader not working. I see
Jupiter's post and that makes sense we do not have the build that corrected
the problem. Does anyone know if a fix is posted somewhere for the reader?

 

[Colin Barnhorst]

If you have the bug id # post it and Jupiter or I (or some other TechBeta
tester) can see it if it is public. If you submitted it without changing
the default "private" to "public" then we will not be able to view it.

 

[Intel Inside]

"If you submitted it without changing the default "private" to "public" then
we will not be able to view it."
So we can expect your default answer to be 'we could not view it therefore
we don't know either'.

I'm not having a go at you Colin, it's just a crazy situation.

 

[Intel Inside]

Ditto Jo, Ditto,
I'm glad you raised the issue today (saved me all that typing).
I too get the same lack of feedback on my feedback, ie. just a very terse
"Field Status changed from [Resolved] to [Closed]"
Three bugs I very recently submitted have disappeared into the aether ie. no
feedback whatsoever!.

We're not mushrooms MS, and you should not treat us as such considering we
are finding multiple bugs for your benefit.

 

[Jupiter Jones [MVP]]

If it was left as private there is nothing anyone outside Microsoft can see
or do about it.
When it is set as private, Microsoft may see it as a potential privacy issue
for the sender if it were made public.
And unfortunately that is the cold reality if a bug is posted private.

 

[Lang Murphy]

Yeah... having the same problem... and this is the first time I'm hearing
about the private/public issue. Would have been nice if that had been fully
disclosed prior to me submitting bugs... guess I could resubmit ensuring
that private is unchecked (or whatever mechanizm makes it "public")

Are we all talking about the Microsoft Beta Client? I see no private/public
enabler in that app...

 

[Colin Barnhorst]

Yes, the MBC. On the left hand panel choose Options. Under Tracking
Options check the Enable Advanced Tracking Options. When you file a report
select "Public" on the Finish Tab.

Don't blame me for its obscurity. I sure didn't write it. The TechBeta
folks have been hammering on this feature of the MBC for a year. When we
started out last year we had to wait until we could see our report on the
database and then change it from private to public. Of course, lots of
folks forgot.

The issue from MS's perspective is one of privacy protection. Oh well.

 

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

Yes, the MBC. On the left hand panel choose Options. Under Tracking
Options check the Enable Advanced Tracking Options. When you file a report
select "Public" on the Finish Tab.

Hmm, never knew that there was such a feature, nice of you to tell us.
Anyway, when enabling Advanced Tracking Options the privacy-option
defaults to Public, could that mean that it defaults to Public even if
Advanced Tracking Options are not enabled? As a test could someone check
for bug #148135 (and if it's public report the solution?).

 

[Leen]

Hmm, never knew that there was such a feature, nice of you to tell us.
Anyway, when enabling Advanced Tracking Options the privacy-option
defaults to Public, could that mean that it defaults to Public even if
Advanced Tracking Options are not enabled?

Nope. Default is Private.

As a test could someone check for bug #148135 (and if it's public report
the solution?).

===> The content that you requested cannot be found or you do not have
permission to view it.

So it's private


--
Leen
==> Please only reply in the newsgroup <==
*** This means, DO NOT send me Email also!!! ***

How to burn an ISO file :
http://iso.snoekonline.com/iso.htm

 

[Colin Barnhorst]

A search on 148135 returns Invalid Feedback ID.

Hmm, never knew that there was such a feature, nice of you to tell us.
Anyway, when enabling Advanced Tracking Options the privacy-option
defaults to Public, could that mean that it defaults to Public even if
Advanced Tracking Options are not enabled? As a test could someone check
for bug #148135 (and if it's public report the solution?).

 

[Guest]

I was not aware of the public / private setting either and did not change it
to public.
Thanks for the heads up on it.

Hmm, never knew that there was such a feature, nice of you to tell us.
Anyway, when enabling Advanced Tracking Options the privacy-option
defaults to Public, could that mean that it defaults to Public even if
Advanced Tracking Options are not enabled?

Nope. Default is Private.

As a test could someone check for bug #148135 (and if it's public report
the solution?).

===> The content that you requested cannot be found or you do not have
permission to view it.

So it's private


--
Leen
==> Please only reply in the newsgroup <==
*** This means, DO NOT send me Email also!!! ***

How to burn an ISO file :
http://iso.snoekonline.com/iso.htm

 

[Lang Murphy]

Oh, yeah, Colin... it's all your fault... ;-D

Yes, the MBC. On the left hand panel choose Options. Under Tracking
Options check the Enable Advanced Tracking Options. When you file a
report select "Public" on the Finish Tab.

Don't blame me for its obscurity. I sure didn't write it. The TechBeta
folks have been hammering on this feature of the MBC for a year. When we
started out last year we had to wait until we could see our report on the
database and then change it from private to public. Of course, lots of
folks forgot.

The issue from MS's perspective is one of privacy protection. Oh well.

 

[Colin Barnhorst]

Thank goodness its hard to shoot the messenger over IP. (whew!)

 

[Guest]

I have made numerous beta feedback reports to MS about ongoing bugs and
problems I have with Vista. I'm finding a few days later I will get back an
automated response from MS saying they have closed or resolved the issue and
telling me I can click on the link in the message to learn more. However,
when I click on the link and log on with my passport info, I get the message
that I am not allowed to access the site, so I can't get any more info, and
the problem still exists. I don't know why or how they have "closed" it.
Anyone else have this experience? In one case they said it wasn't
repeatable, but it happens continually on my computer (ie. I get duplicate CD
drives listed in the folder window when I am working with files on a CD/RW).

Just wondering what is going on. Thanks

Having fallen victim for this my self I decided to make a small
complaint to MS and this is the response I got:

"Our records indicate you are not registered for the Longhorn/Vista beta
through an invitation that was provided through the Microsoft Connect
site. The Longhorn team appreciates the feedback provided by individuals
who received their betas from alternate sources. Our system auto
generates a response to everyone who submits feedback. Unfortunately,
only the testers who are registered through Microsoft Connect have
access privileges to review our feedback. In fairness to those outside
of our betas, this issue is being looked at."

 

[Colin Barnhorst]

I was afraid that was going to be the response. I didn't think Connect was
set up for two million beta testers. There are dozens of beta programs on
Connect and Connect handles distribution of a number of non-beta products
and services, but the bug reporting system is set up for a few tens of
thousands of testers, not millions.

 

[Intel Inside]

No one said that Connect had to be "set up for two million beta testers".
Some beta users are not interested in bugs & might not encounter any!.
However there are some users (like myself) who have submitted multiple bug
reports & would like access to the db to see what happened to them.
The handful of people posting here re this issue that would like this access
does not equate to "two million" at all.

 

[Colin Barnhorst]

Two million people do not post in the newsgroups, but more CPP people submit
bugs than just the people who post in the newsgroups.

Connect has logged around 140,000 Vista bugs submitted by TechBeta testers
alone (around 20,000 folks in TechBeta) in the first year. Additional
thousands of bugs have been posted by TAP, MSDN, TechNet, and Partner
testers.

All bugs in the Connect database are triaged and handled by the team that
owns the feature bugged.

The numbers get ugly fast.

The Connect team is new. I have seen a tremendous expansion of Connect's
ability to handle reports and give feedback in the year it has been in
operation. It has been heavily influenced by the input from the TechBeta
community.