Using New Outlook on Windows for professional communication and productivity
Because the issue affects only one Outlook account, happens across multiple PCs, browsers, Outlook on the web, and new Outlook, while another account works on the same setup, the pattern points to an account or mailbox-side issue rather than a device problem.
Use this troubleshooting path:
- Test in an InPrivate/Incognito browser session.
- Open Edge, Chrome, or Firefox in a private session.
- Sign in to Outlook on the web and try the same attachment.
- If it works there, clear the browser cache for the normal session.
- Check whether the problem affects:
- only new emails or also older emails that previously worked
- internal mail, external mail, or both
- all attachment types or only some types
- whether an error appears, or nothing happens
- Check mailbox storage status in Outlook on the web.
- Go to Settings > Account > Storage.
- Look for a warning such as Storage Full or Quota Exceeded.
- If storage is flagged, attachment actions can be affected until the mailbox state is resolved.
- If the attachment is blocked by policy or file type, Outlook may prevent opening it.
- Outlook blocks certain potentially unsafe attachment types.
- For blocked types, a practical workaround is to have the sender compress the file, such as a .zip file, and resend it, or use OneDrive and send a link instead.
- If this is a Microsoft Exchange account, an administrator can review whether the file type is blocked in Outlook on the web mailbox policy. Changing allowed or blocked file types can take several minutes to apply and increases security risk.
- Use the current workaround if urgent.
- Since forwarding to the other account works, continue using that temporary path.
- If the sender can resend the attachment, test the resent copy in case the original item is corrupted.
Given the symptoms, if all file types fail only for this one mailbox across every PC and web client, escalation to the Microsoft 365 or Exchange administrator is the next step, because that strongly suggests a mailbox-specific server-side problem rather than an Outlook client issue.