After three weeks of this thread being open (and three months for this related thread: http://answers.microsoft.com/en-us/windowslive/forum/mail-signin/cant-login-to-my-outlook-account/489f7199-5b88-4751-be1a-ba9aad0ff99e), I am losing hope that this
issue will be resolved in the near future. So far the only solutions offered have been users who found workarounds for their specific circumstances. This is wonderful for them (and hopefully a few others), but the details of their workarounds only apply
to specific situations, and not to everyone. While I understand that a free email service is not at the top of Microsft's list of support concerns, and that the percentage of the user base affected by this issue (based solely on the replies to these two threads)
is relatively small, it is nevertheless quite disappointing that this software giant finds it so difficult to resolve this problem even after being provided much detailed information.
To reiterate my situation:
I access my hotmail.com email account via the web.
After successful login, I am briefly redirected to a page called "Continue", then I am redirected to a blank page with URL: https://pod51044.outlook.com/owa/?hm=1&f=255&MSPPError=-2147205086. The error URL is exactly the same every time.
The above error is encountered however I attempt to access email (hotmail.com, outlook.com, login.live.com, POP3, etc.), although I can access my profile, calendar, etc. with no apparent issue.
The account experiencing this issue has not been used or signed up for any other service (Office, SkyDrive, etc.), only email.
The issue persists accross browsers, operating systems (including non-Windows), and networks. These connections worked previously.
I have provided everything requested by the forum moderators (FiddlerCap trace, screenshot, etc.)
My options are:
- Wait for Microsoft support to resolve the issue.
- Start changing settings on my account in hopes of blindly stumbling on fix.
- Abandon Microsft free email services.
Optimism for #1 is fading. I've seen no indication that Microsoft has made any progress toward identifying or resolving the issue (beyond the expected suggestions of clearing browser cache, etc.)
Option #2 is pure desperation, and is basically resignation to option #3.
Execution of option #3 would be unfortunate, especially considering that I'm a professional software developer currently using Microsoft technologies (.NET).
Users, please continue to keep posting your workarounds.