New Outlook for Windows - Unable to Open or Send Emails (ErrorType: Component)

Question

Hello,

I am experiencing an issue with New Outlook for Windows.

Issue Description

New Outlook is unable to open email messages or send emails. When opening folders or messages, I receive errors such as:

• "We couldn't complete the request right now."
• "We can't display this message right now."
• ErrorType: Component

Environment

• New Outlook Version: 1.2026.902.100
• Client Version: 20260904006.07
• BE Server: Unknown

What Works

• Outlook on the Web (OWA) works normally.
• Classic Outlook works normally.
• Outlook settings open correctly.
• Search functionality works and can find messages.

What Does Not Work

• Opening email messages.
• Opening mailbox folders.
• Sending emails.
• The issue occurs with both my Microsoft 365 account and a personal Naver account.

Troubleshooting Already Performed

• Reinstalled New Outlook.
• Reset New Outlook application.
• Removed and re-added accounts.
• Recreated Outlook local profile/cache.
• Tested using a mobile hotspot connection.
• Verified that Outlook package installation status is OK.
• Verified account synchronization is successful.
• The same issue occurs even with a local Windows profile.

Error Information

ErrorType: Component

Could you please review the logs and advise what component is failing and how this issue can be resolved?

Thank you.

Answer 1

Disclaimer: Although this site is hosted on the Korean-language (ko-kr) site, your question was submitted in English. To avoid any misunderstanding and provide the most accurate assistance possible, I will respond in English. If anything in my reply is unclear, please feel free to ask for clarification.

Hi,

Based on the information provided, I would not repeat the account removal, cache reset, or New Outlook reinstallation steps.

Because Outlook on the web and classic Outlook continue to work, while New Outlook is affected with both the Microsoft 365 and Naver accounts, a mailbox-specific configuration issue appears less likely. However, this does not prove that the problem is entirely local. A New Outlook-specific client or service component, a device-wide dependency, or a machine-level security policy could still be involved.

The displayed diagnostic summary is not sufficient to identify the failed component. ErrorType: Component does not name a specific module, and BE Server: Unknown does not by itself confirm a server-side problem. As this is a peer-to-peer forum, contributors cannot access Microsoft’s internal diagnostic systems or review unpublished service telemetry.

Microsoft documents that New Outlook uses WebView2 together with a Native Windows Integration Component. Microsoft also explains that some New Outlook functionality and fixes are delivered separately from the installed package version. Therefore, the version numbers alone are not enough to confirm that this is a regression in a particular build: Overview of the new Outlook for Windows (The content in this link only available in English)

I suggest the following remaining checks:

1. Test the same Microsoft 365 account in New Outlook on another supported Windows device, if available. Record both the New Outlook version and client version on that device.
   • If it works there, this would support focusing further investigation on the original Windows environment.
   • If it fails there as well, include that result in the support request because the issue may not be limited to one device.
2. On the affected computer, open Control Panel > Programs > Programs and Features and confirm that Microsoft Edge WebView2 Runtime is present. Record its version and make sure its normal update process has not been blocked by organizational policy or endpoint security software. If WebView2 Runtime is missing, the administrator can obtain the Evergreen installer from Microsoft. I would not recommend manually uninstalling an existing runtime solely because of this error, since the available information does not confirm that WebView2 is the cause: Microsoft Edge WebView2 and Microsoft 365 Apps
3. Ask the Microsoft 365 administrator to check Health > Service health for any relevant Exchange Online, Microsoft 365 Apps, or New Outlook advisory. The public New Outlook known-issues page can also be reviewed, although an issue not appearing there does not rule out a newly emerging or tenant-specific problem.

If no relevant advisory is listed, this case has reached the point where a Microsoft 365 support request is appropriate. The request should focus on the Microsoft 365 account failing in New Outlook; the Naver account can be mentioned as an additional comparison.

Please include:

• A fresh UTC timestamp from a reproduction
• Client ID and Session ID from that occurrence
• New Outlook and client versions
• Windows version and build from winver
• WebView2 Runtime version
• When the issue began and whether it followed an Outlook or Windows update
• Results from the different-device test
• Confirmation that Outlook on the web and classic Outlook work normally

Microsoft Support can then advise which diagnostic logs are required and investigate beyond what is accessible through the forum. Full logs and diagnostic identifiers should be provided privately through the support request rather than posted publicly.

The Microsoft 365 administrator can open a request from Help & support in the admin center. If all subscriptions were purchased through a Microsoft partner, the administrator may need to contact that partner instead:

Get support for Microsoft 365 for business

Until the cause is identified, Outlook on the web or classic Outlook remains the practical workaround.