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

Hi

Try this

Get CCleaner

Run Clean AutoComplete Form History

It will wipe the list and you can start again, being careful not to mistype.

At least you can start again.

I have this issue on my Windows phone email program and I cant think of any work around......

Thanks, Langware.

What you say about Microsoft is totally true. But I will keep an eye on this thread for any new development (a miracle? Unfortunately these are few and far between nowadays...) that may come from a Microsoft reply and/or solution to this problem. Maybe, if a fix is found, it can also be applied to the Office Outlook.

And I am counting on you to keep up the pressure requesting RELEVANT replies and effective action from Microsoft.!

Best wishes.

KikaMelo,

Sorry, but I do not use Office Outlook, and do not know if the problem with Office Outlook is the same as the problem with web-based Outlook.

Microsoft's quarterly revenue is over $20 BILLION dollars. They certainly have the financial ability to fix this problem AND the problem with Office Outlook .... but instead they choose to ignore both problems.

Very poor customer support.

Langware;

I am so happy when I find a soul mate who is persistent with his/her inquiries, and enough articulate to describe the problems and ask for a solution and straight reply! It is appalling to see the 8-page evolution (or, should we say, involution) of this thread, spanning over 2 years! And the mighty Microsoft is unable to fix a simple problem which should not have even existed in the first place if they had done enough tests to their product before releasing it to the customers!

I also find the same problem within the Office Outlook (2007 or 2010 - I have the 2 versions in different Windows 7 PCs), i.e., once you ever type (or mis-type) an email address, it comes up for auto-completion on the To or Cc boxes. No matter what you do, it is impossible to remove those old/inactive/wrong addresses from Outlook. I know you and the rest of the users who have been posting on this forum are referring to the Web-based Outlook.com, but do you know if the problem with the Office Outlook is the same, requiring the same solution?  

Thanks in advance for your help with this.

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.

Carlo_R:

Many Microsoft employees have responded to this thread .... I have included a summary of their replies at the end of this post.

It has been two years SINCE this thread was started, and a YEAR and SEVEN MONTHS since you posted your reply (on May 26, 2013) ... no Microsoft employee has posted in this thread since May 26, 2013 .... and customers are STILL waiting for this bug to be fixed, or feature to be implemented (depending upon whether one considers this issue a bug or a feature request).

Whether this is a bug or a feature ... waiting a YEAR and SEVEN MONTHS is way too long.

Can you please provide some meaningful status on when this issue will be resolved?

Here is a summary of all comments made by in this thread Microsoft employees:

Dec 19, 2012:

 However, we forwarded your suggestion to the product group, who appreciates feedback and considers suggestions for a future releases.

Dec 22, 2012:

please try to visit our Feedback area where you can send your feature requests.

Dec 27, 2012:

Microsoft is doing their best to accommodate every suggestions and feature request provided by our customers.

Dec 29, 2012

Our group is collecting all the said suggestion first, therefore those suggestion is still on progress.

Jan 2, 2013:

In as much as we want to assist you with your concern we need to refer you to our feedback team. Please post your concern on our Feedback area where you can send your feature requests.

Jan 10, 2013:

I have followed the steps that you have provided and I'm able to reproduce your concern.

The feature to remove the misspelled contact in the auto complete list is currently not available. Please post your feedback, comments or suggestions to http://feedback.live.com so the product group can make improvements on our product for future releases.

Jan 15, 2013:

We will send your feature request to our product team but there is no assurance that they will respond. Your best option is the feedback forum as they will scrub all the feature request and if there are considerable amount of request with a certain feature, they will add it up on their future development of the product.

March 25, 2013:

What I would suggest is that you reset your browser's setting to its default.

April 6, 2013:

Our Escalation group is still investigating on your issue and we will notify you as soon as there's an update.

April 9, 2013:

This is to inform you that your issue is still under investigation. Our escalation group is still working on this. We will notify you as soon as there's an update.

April 17, 2013:

Currently, we are still waiting for the results of the Microsoft engineers' investigation of this issue.

April 26, 2013:

Please be informed that the issue is still under investigation. There is no turnaround time on the investigation. However, I already made a follow-up to our Escalation Engineers so they will prioritize this issue.

May 6, 2013:

I made some follow up and can see that this issue was already taken over by the escalation team. The issue is still under investigation.

May 9, 2013:

I understand that you must be frustrated waiting for a resolution regarding removing an autocomplete suggestion. As what the previous moderators have mentioned, there is no turnround time in when this would be implented. As of the moment, our escalation team is still investigating for a resolution regarding this issue.

May 15, 2013:

I understand that you might feel ignored regarding this issue since there hasn't been an update. We extremely apologize for the inconvenience this has caused you. I understand that it might feel repetetive to hear that this is still under investigation. 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.