Our Exchange Server SE queues are filling with messages in retry after the October Windows updates. A reboot clears the problem for a while, but it comes back. What should we check?
Exchange SE queues stuck in retry after the October Windows updates?
Answers
Check the queue's last error first. One reported pattern is a 432 4.3.2 STOREDRV error with MailboxOfflineException and MapiExceptionMdbOffline, even though the immediate symptom is a growing retry queue.
Microsoft has published guidance on Exchange instability after the October 2026 Windows updates, including a registry-based mitigation. Check the current guidance and confirm it applies to your servers before changing the registry. A reboot may get mail moving again, but it doesn't necessarily prevent the failure from returning.
Reply to this answer
Don't assume every retry queue is this update issue. Check database status and the queue error, then compare when failures started with the Windows update installation. Message tracking logs can help establish the timing and scope.
If mail is backing up quickly, open or escalate a Microsoft support case with the error details and update history. That gives support something more useful than just a queue count.
Reply to this answer
Be careful about treating skipped Windows updates as the fix. There was a report of an Exchange SE system without this problem where Exchange was updated but the underlying Windows Server was not. That's a useful clue, not proof that delaying Windows patches is safe or will prevent it elsewhere.
Weigh any deferral or rollback against the security exposure and your patching requirements. Check Microsoft's current mitigation guidance first.
Reply to this answer
Also check whether other Exchange services are affected. Outlook on the web failures were reported alongside this issue, so the queue may not be the only symptom worth monitoring after a reboot.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions