Exchange Connection Problems

Fix Outlook Delegate WastebasketStyle Registry Key Not Working

Huma Ashraf ChHuma Ashraf Ch Oct 21, 2026 868 views

Question details

The user needs to fix an issue where deleted items from a delegate or shared mailbox are moved to the primary mailbox instead of the delegate mailbox's Deleted Items folder, despite configuring the DelegateWastebasketStyle registry value.

Fix Outlook Delegate WastebasketStyle Registry Key Not Working
Product
Microsoft Outlook and Exchange
Device & OS
not provided
Scenario
Managing and deleting emails within a delegate or shared mailbox in Microsoft Outlook.
Observed behavior
Deleted items bypass the shared mailbox's Deleted Items folder and move directly to the primary user's Deleted Items folder, even after updating the registry, Group Policy, and rebuilding the Outlook profile.
Before you start

Ensure you have administrator access to edit the Windows Registry and verify that your user account has been granted explicit Full Access permissions to the shared mailbox on the Exchange server.

Solution 1Recommended

Verify Registry Key Value and Exchange Permissions

Double-check the specific registry path for your Outlook version and ensure the Exchange permissions are correctly assigned, as configuration mismatches are the primary cause of this issue.

The DelegateWastebasketStyle registry key behaves differently depending on the exact build of Outlook and the Exchange server environment. The key must be placed in the correct version-specific folder, and the user must have 'Full Access' permissions rather than just 'Send As' rights.

1
Open Registry Editor

Press the Windows key + R, type 'regedit' in the Run dialog box, and press Enter to launch the Registry Editor.

2
Navigate to the Outlook Options Key

Navigate to 'HKEY_CURRENT_USER\Software\Microsoft\Office\[YourVersion]\Outlook\Options\General', replacing [YourVersion] with your version number (e.g., 16.0 for Outlook 2016/2019/365).

3
Check the DWORD Value

Locate the 'DelegateWastebasketStyle' DWORD value. Ensure it is set to '4' (moves deleted items to the shared mailbox folder) or '8', depending on your specific requirements.

4
Confirm Full Access in Exchange

Log into the Exchange Admin Center or use PowerShell to confirm your account has explicit 'Full Access' permissions to the delegate mailbox.

Verify Registry Key Value and Exchange Permissions
Caution with Registry Editing: Incorrectly modifying the registry can cause system instability. Always double-check the path and value data before saving changes.
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While specialized Exchange server issues require Microsoft-specific network troubleshooting, you can manage all your daily documents, spreadsheets, and presentations efficiently with WPS Office. It is a powerful, lightweight, and free alternative to Microsoft Office.

  1. 1. Visit the Official Website: Go to the official WPS Office website to access the latest free version.
  2. 2. Download the Installer: Click the 'Free Download' button to download the setup file for your operating system.
  3. 3. Install and Start Creating: Run the installer, follow the on-screen instructions, and start managing your office documents seamlessly.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight installation that runs smoothly on almost any computer without heavy resource usage.Familiar user interface allowing for a seamless transition without a learning curve.Built-in PDF editor and tabbed document viewing in one unified application.
QA img-9

Frequently Asked Questions

What does the DelegateWastebasketStyle registry key do in Outlook?

The DelegateWastebasketStyle registry key controls where deleted items go when a delegate deletes them from a shared mailbox. When properly configured, it forces deleted emails to move to the shared mailbox's Deleted Items folder instead of the delegate's primary Deleted Items folder.

Why do deleted items keep going to my primary mailbox despite the registry fix?

This commonly happens if the registry key is placed in the wrong version folder, if the user only has 'Send As' permissions instead of 'Full Access' on the Exchange server, or if a corrupted Outlook profile is failing to read updated registry policies.

Will creating a new Outlook profile fix this registry policy issue?

Sometimes. If the current Outlook profile is corrupted, it might ignore Group Policy updates and registry modifications. Creating a fresh profile forces Outlook to fetch the latest configurations, though it won't bypass underlying Exchange permission errors.