Fix "The Operation Cannot Be Performed" in Outlook (2026)

You're about to move a critical client email to a project folder, and Outlook suddenly blocks you with the cryptic error: "The operation cannot be performed." Or maybe you're hitting Send on a carefully drafted reply, and instead of whooshing away, the message just sits there—frozen, with that same maddening notification staring back at you.

I've been there. In fact, over the past 15 years of working with Outlook in everything from small law firms to enterprise deployments, I've seen this error pop up in more variations than I can count. The good news? It's almost always fixable. The bad news? There's no single magic bullet—the root cause can range from a rogue add-in to a corrupted data file.

This guide takes a scenario-based approach to help you diagnose and fix the issue across Outlook 2010, 2013, 2016, 365, and Mac. We'll also touch on related outlook error codes along the way, so you can identify whether you're dealing with the standard "operation cannot be performed" message or a variant that points to a different underlying problem.

---

Why Does Outlook Say "The Operation Cannot Be Performed"?

Before we dive into fixes, it helps to understand what's actually happening under the hood. The outlook operation cannot be performed error isn't a single, well-defined failure—it's a catch-all message that Outlook throws when an operation conflicts with the current state of your mailbox or data files.

The Root Cause: Local Cache vs. Server Sync Conflicts

Here's the mental model that's served me well: think of your Outlook client as a translator between you and your mail server. When you open an email, reply to it, or move it to a folder, Outlook is working with a local copy of that item—stored in your OST (for Exchange/365 accounts) or PST (for POP/IMAP) file. Meanwhile, the server has its own version.

The error typically appears when these two versions fall out of sync. This happens more often than you'd think when:

• The same mailbox is open on multiple devices simultaneously
• A mobile device updates an item while your desktop client is offline
• Another process (like a rule or add-in) modifies the item in the background

When Outlook detects that the local copy's metadata—things like read status, flags, or modification timestamps—doesn't match what the server expects, it refuses to perform the operation. I like to call this "stale item metadata." The item looks fine to you, but Outlook knows something changed underneath.

[Your Action] → [Local OST/PST Copy] → [Sync Check] → [Server Copy]
                        ↓                    ↓
                   Metadata stale?     Metadata current?
                        ↓                    ↓
                   ERROR BLOCKED      Operation proceeds

Common Scenarios: Calendar Items, Email Replies, and Folder Moves

In my experience, this error clusters around three specific activities:

---

How to Fix the "Operation Cannot Be Performed" Error in Outlook

Let's get to the practical part. I've ordered these fixes from simplest to most invasive. Start with Fix 1 and work your way down—in my experience, about 70% of cases resolve by Fix 3.

Fix 1: Restart Outlook and Check for Multiple Instances

I know, I know—"have you tried turning it off and on again?" feels insultingly simple. But hear me out.

Outlook has a nasty habit of leaving background processes running even after you close the main window. These zombie instances can hold locks on data files, causing exactly this kind of error. Here's what I recommend:

1. Close all Outlook windows completely.
2. Open Task Manager (Ctrl+Shift+Esc) and look under the Processes tab.
3. If you see any OUTLOOK.EXE entries still running, right-click and select End Task.
4. Restart Outlook and try the operation again.

If the error was on a specific item—say, a meeting invite you were trying to accept—close that item's window first, then reopen it fresh. This clears the stale state that Outlook loaded when the item was first opened.

Fix 2: Disable Problematic Add-ins (Safe Mode Method)

Add-ins are the number one culprit I encounter in the field. They're useful when they work, but a poorly coded add-in can interfere with how Outlook processes items, leading to the "message has been changed" variant of this error.

Here's how to isolate the problem:

1. Close Outlook completely.
2. Press Windows + R to open the Run dialog.
3. Type Outlook /safe and press Enter.

If Outlook starts without the error in Safe Mode, you've confirmed an add-in is the problem. Now let's find which one:

1. Go to File > Options > Add-ins.
2. At the bottom of the window, find the Manage dropdown and select COM Add-ins, then click Go.
3. Uncheck all add-ins and click OK.
4. Restart Outlook normally. If the error is gone, go back into the Add-ins dialog and re-enable them one at a time, restarting Outlook after each one.

The last add-in you enabled before the error returned is your culprit. In my experience, the usual offenders are CRM plugins, email tracking tools, and older antivirus integrations. Once identified, you can either update the add-in or disable outlook add-ins permanently.

Fix 3: Turn Off Conversation Clean Up and Auto-Save Settings

This fix addresses the most common variant of the error: "The operation cannot be performed because the message has been changed." If you're seeing that specific wording, this is likely your solution.

Here's what's happening: Outlook's Conversation Clean Up feature and auto-save function can modify message metadata in the background. When you then try to reply to or move that message, Outlook detects the change and blocks the operation.

To fix it:

1. Go to File > Options > Mail.
2. Scroll to the Conversation Clean Up section.
3. Uncheck the box labeled "When a reply modifies a message, don't move the original."
4. Scroll down to the Save messages section.
5. Uncheck "Automatically save items that have not been sent after this many minutes."
6. Click OK and restart Outlook.

I've seen this single change resolve the issue for entire teams. In one case, a client with 40 affected users was back to normal within an hour of applying this across their organization.

Fix 4: Repair Your Outlook Data File (PST/OST) with SCANPST

If the error persists, the problem might be deeper—specifically, in your data file itself. Outlook includes a built-in tool called the Inbox Repair Tool (SCANPST.exe) that can fix minor corruption.

Here's how to use it:

1. Close Outlook completely.
2. Locate SCANPST.exe. It's typically in one of these locations:
   • C:\Program Files\Microsoft Office\root\Office16\
   • C:\Program Files (x86)\Microsoft Office\root\Office16\
   • (The "Office16" folder corresponds to Office 2016/365; adjust for your version)
3. Run the tool and click Browse to select your data file.
4. If you're not sure where your PST/OST file lives, check C:\Users\[YourUsername]\AppData\Local\Microsoft\Outlook\.
5. Click Start to begin the scan. If issues are found, click Repair.

A word of caution: SCANPST works well for minor corruption, but it has limitations. For severely damaged or very large files (over 20GB), it can struggle or even fail. We'll talk about alternatives in the prevention section.

Fix 5: Create a New Outlook Profile

Sometimes the problem isn't your data file—it's the profile that connects to it. A corrupted profile can cause all sorts of erratic behavior, including this error.

To create a new profile:

1. Close Outlook.
2. Open Control Panel and click Mail (you may need to switch to Large Icons view to see it).
3. Click Show Profiles.
4. Click Add and give your new profile a name.
5. Enter your email account details and complete the setup.
6. Back in the Mail Setup dialog, select Always use this profile and choose your new profile from the dropdown.
7. Click Apply and OK.

When you restart Outlook, it'll use the fresh profile. Your emails, contacts, and calendar items are all stored in the PST/OST file, so nothing gets deleted—the new profile simply reconnects to the same data. This is one of the most reliable ways to create new outlook profile and eliminate profile-related corruption.

Fix 6: Use the Microsoft Support and Recovery Assistant (SaRA)

If you're not keen on manual troubleshooting, Microsoft's automated tool can do the heavy lifting for you. The Microsoft Support and Recovery Assistant (SaRA) can diagnose and fix a range of Outlook issues, including sync problems that trigger this error.

1. Download SaRA from Microsoft's official site.
2. Run the tool and select Outlook from the list of applications.
3. Choose the specific issue you're experiencing (or select "I'm not sure" for a general diagnosis).
4. Follow the on-screen prompts. The tool will run diagnostics and apply fixes automatically.

In my experience, SaRA is particularly effective for Exchange and Microsoft 365 sync issues. It's not a silver bullet for every scenario, but it's worth trying before you resort to more invasive measures.

Fix 7: Advanced: Repair Office Installation or Use Registry Editor

If you've exhausted the above options, the problem might be with the Office installation itself. Here are two advanced approaches:

Repair Office Installation:

1. Open Control Panel > Programs and Features.
2. Locate Microsoft Office in the list.
3. Right-click and select Change.
4. Choose Quick Repair first. If that doesn't work, try Online Repair (this takes longer but is more thorough).
5. Restart your computer after the repair completes.

Registry Editor (Expert Users Only):

In rare cases, a specific registry key can cause this error. I'm including this for completeness, but I cannot stress this enough: back up your registry before making any changes. A mistake here can render your system unbootable.

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\[YourVersion]\Outlook\.
3. Look for any keys related to add-ins or profile settings that might be misconfigured.

Honestly, unless you know exactly what you're looking for, I'd skip this step and contact Microsoft Support instead. The windows registry editor is powerful, but it's also unforgiving.

---

Fixing the Error in Enterprise Environments: Group Policy and PowerShell

If you're an IT administrator dealing with this across multiple machines, the individual fixes above aren't scalable. Here's how to approach it at the organizational level.

Using PowerShell to Identify and Fix Sync Issues

PowerShell gives you granular control over mailbox items that might be causing sync conflicts. Here's a sample script to check for and clear the ReadOnly attribute on a user's mailbox folder:

Connect-ExchangeOnline

Get-MailboxFolderStatistics -Identity "user@domain.com" | 
    Where-Object {$_.ItemsInFolder -gt 1000} |
    Select-Object FolderPath, ItemsInFolder, FolderSize

Search-Mailbox -Identity "user@domain.com" -SearchQuery "Received:>01/01/2026" -EstimateResultOnly

This approach lets you identify problem folders and items without touching individual machines. For persistent issues, you can also use PowerShell to reset the target mailbox's sync state:

Set-Mailbox -Identity "user@domain.com" -ExchangeGuid $null

Configuring Group Policy to Prevent Add-in Conflicts

For organizations dealing with known problematic add-ins, Group Policy offers a centralized solution. You can block specific add-ins across all machines by setting registry keys via Group Policy.

---

Preventing the "Operation Cannot Be Performed" Error in the Future

An ounce of prevention is worth a pound of cure—especially when that cure involves SCANPST and registry edits.

Best Practices for Mailbox Maintenance

Here's a checklist I give to every client, and it's served them well:

• Archive regularly: Keep your PST/OST file size manageable by archiving emails older than 6-12 months. A bloated data file is more prone to corruption.
• Avoid multi-device overlap: If you have Outlook open on your desktop and laptop simultaneously, you're asking for sync conflicts. Close one before using the other.
• Stay updated: Ensure Outlook is always patched to the latest version. Microsoft frequently fixes sync-related bugs in updates.
• Know your PST location: Familiarize yourself with your outlook pst file location so you can back it up regularly. C:\Users\[Username]\AppData\Local\Microsoft\Outlook\ is the default.

When to Consider a Professional PST Repair Tool

SCANPST.exe is a decent first line of defense, but it has real limitations. It struggles with severely corrupted files, files larger than 20GB, and encrypted PSTs. In those cases, professional tools offer more advanced recovery options.

---

Frequently Asked Questions

What does it mean when Microsoft Outlook says the operation cannot be performed because the message has been changed?

This specific variant means the item's metadata—like read status or flags—has been altered by another process since it was loaded in your view. This is typically caused by a sync conflict (the same mailbox open on multiple devices) or an add-in modifying the item in the background. The most direct fix is adjusting your Conversation Clean Up settings as described in Fix 3.

Why is Outlook saying the operation failed?

The generic "operation failed" error is broader than the "operation cannot be performed" message. It often points to network connectivity issues, server problems, or a corrupted profile. If you're seeing this, start with Fix 5 (create a new profile) and Fix 6 (SaRA tool). If those don't help, check your network connection and server status.

How do I fix "you don't have appropriate permission to perform this operation" in Outlook?

This is a permissions-related error, distinct from the sync issues we've covered. It typically occurs in shared mailboxes or public folders. Check your folder permissions first—right-click the folder, select Properties > Permissions, and verify you have the appropriate access level. If you're in an enterprise environment, your Exchange administrator may need to adjust permissions via the admin center or PowerShell.

Will I lose my emails if I create a new Outlook profile?

No. Creating a new profile does not delete any emails. Your messages, contacts, and calendar items are stored in the PST/OST file, which remains untouched. The new profile simply reconnects to the same data file. Think of it as getting a new key to the same house—the house (your data) is still there.

---

Conclusion

The "operation cannot be performed" error in Outlook is frustrating, but it's rarely a sign of permanent data loss. In most cases, the root cause falls into one of three buckets: sync conflicts, problematic add-ins, or data file corruption.

Start with the simplest fixes—restarting Outlook, disabling add-ins, adjusting settings—and work your way up to more invasive solutions like repairing data files or creating new profiles. In my experience, this approach resolves the vast majority of cases without needing professional intervention.

If you've tried all seven fixes and the error persists, don't keep banging your head against the wall. Contact Microsoft Support or post in the Microsoft Tech Community with your specific Outlook version and the exact error message. Include any relevant outlook error codes you see in the details—they can be invaluable for diagnosis.

Don't let this error slow you down. Get it fixed today.