How to delete one mis-spelled email address from auto-complete list

Carol_R:

Thank you for your reply.

I must admit that this has been a most painful experience.

Basically, it has taken Microsoft OVER FIVE MONTHS to finally tell me that they acknowledge the problem I have reported, they have reproduced it, but they have no current plans to fix the problem.

I may not like the final response (i.e., that Microsoft has no plans on fixing the issue), but what I find to be totally unacceptable and unprofessional is the fact that it took Microsoft OVER FIVE MONTHS to provide a response that should have been provided within a month or less!!!!

Part of the delay was due to Forum Moderators not understanding the issue I was describing, which required significant persistence on my part to convince Forum Mods to reproduce the problem themselves. This (getting Forum Mods to reproduce the issue) should not have been so difficult to accomplish.  Forum Mods need better training in troubleshooting customer's issues.

Another part of the delay (once the problem I described was reproduced by Forum Mods) was the lack of a timely response from Microsoft's Engineers. They need better training in the importance of providing feedback to customers who have taken the trouble of documenting a bug for them.

I realize that this is not personally your fault ... so please just pass my dissatisfaction back to your management (including Jennifer) and their contacts at Microsoft. Microsoft's unprofessional behavior (FIVE MONTHS to respond) truly discourages people from reporting bugs ... but perhaps that is their intention!

Finally, I have unmarked your response as an "answer". I would like to leave this thread unanswered until such time that a fix for this issue becomes available in a future release of Outlook.com. When such a fix is available, just post a response in this thread. I will gladly test the fix, and if the problem is resolved, I will mark this thread as answered.

Hi langware,

This is Carlo of the Outlook.com Support Escalations Team.  I am a Senior Support Analyst for Microsoft and I am part of the team handling Outlook.com related concerns and issues.

I have read through this thread and I have studied your queries and the steps that you used in order to reproduce the issue.  I would like to inform you that we have also simulated this issue on our end and we have encountered the same results.  As such, we have escalated this issue even further to our Microsoft Engineers for further investigation a while back.  We apologize for the wait but we have just received word from them regarding this concern.

Our Microsoft Engineers have confirmed that this feature is currently not available in the Outlook.com User Interface (UI).  They informed us to instruct you to suggest this feature via the feedback link and since you have already done so, this issue has been properly documented.

Another point that we can discuss here is the fact that our Microsoft Engineers are now aware of this issue.  Although there is no definite turnaround time, this feature may become available in future releases of Outlook.com.

I hope this satisfies your queries regarding this issue.  We have enough documentation on our end and we have submitted everything to our Microsoft Engineers following our standard protocol.  We will immediately reach out to everyone once we have an update regarding this feature.

Thank you.

Regards,

Carlo

I have described a bug in outlook.com (on Dec 17, 2012); the bug was reproduced by two Forum Mods.

I asked a simple question:  will the bug be fixed sometime in 2013?

The only response I received has been: ***Please be informed though that our escalation engineers have not found a current solution for this yet but they are still working on it currently.***Only members of the outlook.com Product Team can write the code necessary to fix the bug, so I asked a followup question:  **So please tell me whom you are referring to when you say "our escalation engineers" ... do you mean employees of the outsourcing firm, or do you mean outlook.com developers who work directly for Microsoft?**After FIVE MONTHS neither question has been answered.

WILL THIS BUG BE FIXED IN 2013?????????????

I am still waiting for you to answer this question ....

So please tell me whom you are referring to when you say "our escalation engineers" ... do you mean employees of the outsourcing firm, or do you mean outlook.com developers who work directly for Microsoft?

Denise T,

You stated that:

Please be informed though that our escalation engineers have not found a current solution for this yet but they are still working on it currently.

When you refer to "our escalation engineers", do you mean other employees of the outsourcing company that you work for, or do you mean people directly employed by Microsoft.

If you mean other employees of the outsourcing company that you work for, then please know that they CANNOT SOLVE this problem and that they CANNOT FIND A SOLUTION because there is no solution to be found.

The only way to solve this problem is for the outlook.com developers who work directly for Microsoft to write the code necessary to provide "add, delete, and change" functions for managing the contents of the auto-complete history list.

So please tell me whom you are referring to when you say "our escalation engineers" ... do you mean employees of the outsourcing firm, or do you mean outlook.com developers who work directly for Microsoft?