In one forum post, a user said: If the same thing happens when you try to log in to the Outlook web app, check out some of these resolutions.
How do I fix the custom error module in Outlook?
1. Is the Outlook.com service down?
It might be the case that the Outlook.com service is down for a maintenance period. To check, open Microsoft’s service page in a browser. That shows users a current status for Microsoft services. If that page doesn’t display a green tick for the Outlook.com service, then you might need to wait a bit for that service to get up and running again.
2. Delete corrupted Outlook cookies
The custom error module does not recognize this error is often due to corrupted browser cookies. You can delete Outlook cookies in browsers like Opera and Mozilla Firefox much the same. Open the Outlook.com URL in those browsers. Click the information buttons on the left of their URL bars. Then select to delete all the Outlook cookies in the Cookies in use windows. Tired of Outlook issues? Check out this guide for some great software alternatives.
3. Delete cookies in Edge
If the custom error module does not recognize this error arises in Edge, however, you’ll need to clear all the browser’s cookie data.
4. Open Outlook in an alternative browser
As the custom error module does not recognize this error is often a browser cookie issue, try opening Outlook.mail in an alternative browser to the one you’re utilizing. The issue often arises within Chrome and Opera. You might find that you can sign in to Outlook.com ok with the likes of Edge or Firefox. Those are a few of the confirmed resolutions that have fixed the custom error module does not recognize error for some users. This error usually pertains to browser cookies. So, clearing browsers’ data or resetting them are probable fixes.
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
