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

Anonymous
2012-12-18T01:03:01+00:00

I previously mis-spelled an email address when sending a message .... and now, that mis-spelled address is displayed in the auto-complete list each time I begin to type the correct email address.

This is NOT an issue with my contact list ... I do not have a contact defined for this address.

I do have this option enabled:  Give suggestions for anyone I've communicated with (contacts and non-contacts) and I want to keep that option enabled. I realize that I could select this option: Only suggest people in my contact list, and the mis-spelled address would not appear in the auto-complete list .... but I want the auto-complete function to give suggestions from both contacts and non-contacts.

What I am looking for is the ability to delete one entry from the non-contact addresses that are maintained by the auto-complete feature. Can this be done in Outlook.com??

Outlook | Web | Outlook.com | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

81 answers

Sort by: Oldest
  1. Anonymous
    2013-04-24T05:12:26+00:00

    I am still waiting for someone from Microsoft to tell me if the issue I described will be fixed sometime in 2013.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-04-26T23:47:39+00:00

    Hello langware,

    Thank you for making a follow-up.

    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. For the updates, you may check on this thread.

    Your patience regarding this issue is highly appreciated.

    Regards.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-04-30T02:01:32+00:00

    Ace_J.

    I started this thread on December 17, 2012 .... that is 4.5 MONTHS AGO.

    Since that time, at least two Forum Moderators have stated that they were able to reproduce the problem.

    You state:

    "Please be informed that the issue is still under investigation. There is no turnaround time on the investigation."

    First, please tell me what still needs to be investigated??????? Your own Forum Moderators have reproduced the problem.

    Second, the reason there is no turn around time on the investigation is because there is nothing more to investigate.

    I have been patient for 4.5 MONTHS. I would like a response from a MICROSOFT EMPLOYEE. I would like to know if the bug I have described (and that your own Forum Mods have reproduced) is or is not scheduled to be fixed in 2013.

    Please, no more excuses, no more "investigations", no more scripted replies .... just answer this question:

    IS THE BUG I HAVE REPORTED GOING TO BE FIXED SOMETIME IN 2013?????????????

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-05-04T19:40:40+00:00

    I am STILL WAITING for someone to answer my question ......

    IS THE BUG I HAVE REPORTED GOING TO BE FIXED SOMETIME IN 2013?????????????

    If you are unwilling or unable to answer this question, then escalate this to someone who can, but please DO NOT reply with scripted text saying that the issue is "under investigation". That reply is insulting. There is NOTHING TO INVESTIGATE. The bug has been reproduced by several Moderators (re-read this thread for details). I just need to know if the bug will be fixed in 2013.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-05-07T04:57:02+00:00

    Hi,

    I sincerely apologize that this issue has taken too long to be resolved. 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. We will inform you as soon as there are developments regarding your concern.

    Thank you.

    Was this answer helpful?

    0 comments No comments