Errors opening/saving attachments and printing emails in New Outlook

Anthony Landati 0 Reputation points
2026-11-17T15:55:00.82+00:00

Two separate client tenants started having the same problem in new Outlook for Windows on the same day (Nov 16, 2026). Both work fine in Outlook on the web.

Tenant A: The user can’t open, preview, or save attachments from a shared mailbox.

  • Opening or previewing: “Something went wrong while the document preview was being created. Please try again later.”
  • “Open in desktop app”: “Something went wrong. The request could not be completed. Try opening the file again.”
  • Save as also fails.

Tenant B: The user can’t print emails from a shared mailbox (Full Access). The Print button does nothing or shows the same “document preview” error, and File > Print and Ctrl+P fail too. Printing from her own mailbox works. After an app reset, some emails print and others fail at random.

Already tried / ruled out:

  • New Outlook Repair, Reset, and an uninstall/reinstall
  • Exchange permissions (Full Access confirmed) and Windows file permissions
  • WebView2 is 157.0.4341.57, so not the 156.x build behind EX1528992
  • Outlook on the web works for both users, same mailboxes and items

Is anyone else seeing this since last week’s Exchange Online outage (EX1550543), or since EX1528992 was marked fixed? Has anyone found a fix, other than webmail or switching back to classic Outlook?

Outlook | Windows | New Outlook for Windows | For business
0 comments No comments

2 answers

Sort by: Newest
  1. AI answer

    2026-11-18T18:49:58.08+00:00

    No permanent client-side fix is publicly confirmed for this November 16 shared-mailbox regression, so each affected tenant should report it through Microsoft 365 Service Health and open a support request if no matching advisory appears.

    What is currently established

    • Other public reports describe the same November 16, 2026 onset: attachment open/preview/save failures and email-printing failures limited to shared mailboxes in New Outlook, while Outlook on the web continues to work ^1^.
    • The earlier EX1528992/WebView2 issue involved attachment-opening failures, but its public WebView2 thread was closed as fixed. A subsequent report in that thread described similar behavior with New Outlook and WebView2 157.0.4341.57; that is evidence of continued reports, not confirmation that this WebView2 build is the cause ^2^.
    • No public source definitively connects these new shared-mailbox failures to EX1550543, EX1528992, or WebView2 157.0.4341.57.
    • The documented New Outlook operations are attachment Preview/Open/Download and email Print/Ctrl+P. Your users are invoking supported operations, not relying on the unavailable Quick Print feature ^3^ ^4^.

    The shared-mailbox-only scope, simultaneous cross-tenant onset, successful OWA tests, and failure after Repair/Reset/reinstallation justify escalating rather than repeating local repair or permission changes. They do not, by themselves, establish the underlying cause.

    Report and escalate each tenant

    1. Sign in to the Microsoft 365 admin center with a Service Support, Helpdesk, or other role permitted to view service health.
    2. Go to Health → Service health.
    3. Check both:
      • Active issues Microsoft is working on
      • Issue history, including EX1550543 and EX1528992
    4. Open each incident and compare its stated user impact, affected services, start time, and scope with shared-mailbox attachment and printing behavior.
    5. If no entry matches, select Report an issue and submit one report from each tenant. Microsoft uses these reports to correlate impact across organizations ^5^.
    6. For operationally significant impact, create a Microsoft support request from the admin center. If an active advisory already represents the exact problem, track it in Service Health instead; otherwise, reporting the issue or opening a support request is the documented escalation route ^6^.

    Include this minimal reproduction matrix:

    • UTC reproduction time
    • Tenant and affected user, without posting identifiers publicly
    • New Outlook version, client version, WebView2 version, and Windows build
    • Shared mailbox versus primary mailbox result
    • The same message/item tested in New Outlook and OWA
    • Attachment operation: Preview, Open in desktop app, and Download/Save
    • Printing operation: toolbar Print, File → Print, and Ctrl+P
    • File types affected and whether failures are consistent or intermittent
    • Exact error text, screenshots, and New Outlook session ID
    • Confirmation that Repair, Reset, reinstall, permissions, and WebView2 156.x applicability have already been ruled out

    Report attachment and email-print failures as related observations but separate reproductions. That prevents the printing failure from being misclassified as the older known issue involving printing a Word attachment from its side-by-side preview.

    Workarounds pending mitigation

    The currently supported practical workarounds remain:

    • Outlook on the web, which your testing shows works.
    • Classic Outlook, where available.
    • For attachment printing only, open the attachment in its associated desktop or web application and print there. Microsoft documents this route for files that New Outlook cannot preview or print directly ^4^.

    Avoid removing and re-adding Full Access permissions: access already works in OWA and the affected shared mailboxes open in New Outlook, so the available evidence does not support permission propagation as the resolution.


    References

    1. Errors opening/saving attachments and printing emails in New Outlook - Microsoft Q&A
    2. [Problem/Bug]: EX1528992 — New Outlook still cannot open attachments directly in desktop Office · Issue #5791 · MicrosoftEdge/WebView2Feedback · GitHub
    3. [New Outlook](https://support.microsoft.com/outlook/mail/open-save-and-edit-attachments-received-in-outlook)
    4. [New Outlook](https://support.microsoft.com/outlook/print-attachments-received-in-email-messages)
    5. How to check Microsoft 365 service health
    6. Microsoft 365, Dynamics 365 & Power Platform incident readiness for Microsoft Engage Center
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Hani-Ng 2,935 Reputation points Independent Advisor
    2026-11-17T16:11:33.6966667+00:00

    Hi Anthony Landati
    Since Outlook on the web works as expected, Full Access permissions have been verified, and you've already ruled out application repair/reinstall and the WebView2 version associated with EX1528992, this does not immediately appear to be a mailbox permission or file access issue.

    To better understand your environment and whether there may be a common factor, could you provide a few additional details?

    • Are other users with access to the same shared mailboxes experiencing the same behavior?
    • Does the attachment issue occur with all attachment types (for example, PDF, Word, Excel, image files), or only certain file formats?
    • For the printing issue, do the affected messages have anything in common, such as attachments, embedded images, or a specific message format?
    • Are the affected users running the same New Outlook for Windows version/build?

    If others are seeing similar attachment preview/open/save issues or email printing failures from shared mailboxes in New Outlook for Windows, please share any details, including the Outlook version/build and whether the issue is limited to specific mailboxes, message types, or attachment types.

    As a temporary workaround, Outlook on the web or classic Outlook may be worth using while additional information is gathered.

    I hope this information helpful.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.