Microsoft Confirms Outlook Crashing Bug: Temporary Fix Shared While Investigation Continues

A Growing Concern for Outlook Users

Microsoft has acknowledged a widespread issue impacting users of the classic Outlook email client, primarily those subscribed to the Monthly Enterprise Channel. A sudden wave of crashes began shortly after the release of Outlook Version 2504 (Build 18730.20122), frustrating users who found the application failing every time they tried to open or compose a new email. The culprit? Outlook’s inability to access its critical Forms Library—a component essential for email composition and rendering.

This crashing behavior is most frequently reported in Virtual Desktop Infrastructure (VDI) environments, where virtualized instances of Windows are commonly used by enterprise clients. Microsoft has already escalated the issue internally and assured users that updates will follow once a definitive fix is in place. Meanwhile, a temporary solution has been provided: users can manually create a missing “FORMS2” folder in a specific local directory on their system.

This is not the only bug afflicting Outlook lately. Another known issue from Version 2505 (Build 18827.20128) is causing mailbox folders to flicker or unexpectedly reposition themselves during the item move process. The temporary workaround is to disable caching of shared mailboxes by turning off the “Download Shared Folders” option, though this workaround may hinder performance.

Microsoft’s quick action is partially due to a similar pattern of crashes earlier this year, which affected email operations like replying, forwarding, or even simply opening messages. Back then, the company had issued both temporary and permanent fixes. The recurrence of these issues underscores the fragility of maintaining stability across various Outlook builds and environments.

Adding to the narrative, Microsoft recently addressed crashes in Outlook LTSC 2019 when handling messages from integrated services like Viva Engage, Yammer, and Power Automate. Each fix involves a delicate balance of user experience and back-end compatibility, especially in enterprise-grade systems.

These repetitive issues point toward a growing complexity in Outlook’s architecture, where minor version updates can unintentionally disrupt core functionality. It also highlights the urgent need for better pre-deployment testing in virtual and enterprise environments, especially with the evolving nature of hybrid work systems.

As IT professionals grow increasingly wary of such disruptions, many are turning to automation platforms to streamline patch management and incident response. Traditional patching, once synonymous with script-heavy workloads and long hours, is now being replaced with agile, automated approaches that reduce human error and enhance response time.

What Undercode Say:

The Crumbling Reliability of Enterprise Outlook

Microsoft’s announcement exposes an uncomfortable reality: even flagship software like Outlook is not immune to version-triggered instability. What makes this particular issue notable is how foundational it is. The inability to open or write emails—basic functions—isn’t just a glitch; it’s a significant productivity blocker, especially in professional environments that rely heavily on VDI setups.

The reliance on manual folder creation as a temporary workaround feels archaic for a company of Microsoft’s scale. In 2025, users shouldn’t have to navigate into hidden directories and manually build folders just to keep core functions from crashing. This situation reflects either rushed development cycles or a breakdown in quality assurance protocols.

The escalation of the issue and Microsoft’s commitment to investigate are positive signs, but they don’t entirely erase the impact on end-users. Every minute spent debugging Outlook is a minute lost on real work. Worse, these issues have a domino effect. Help desks get flooded. IT teams are stretched thin. CIOs lose confidence in centralized systems, and some organizations may start exploring alternative platforms.

Moreover, the repeated emergence of Outlook bugs across different builds hints at a larger architectural fragility. As Microsoft moves toward a more cloud-integrated, AI-powered Office ecosystem, it’s apparent that its legacy infrastructure—like classic Outlook—is struggling to keep pace.

It’s worth examining how the VDI environments specifically are affected. These setups are known for their layered complexity and limited user privileges, which can make even small fixes hard to implement at scale. In such contexts, a bug that breaks message composition is more than an inconvenience—it’s a business risk.

Then

Earlier crash issues—like those tied to Viva Engage or Power Automate—show a pattern: integrations are often the breaking point. Microsoft is encouraging the use of a broader ecosystem, but these integrations must be robust. A new Outlook update shouldn’t break email just because it links to a service like Yammer.

This creates a difficult landscape for IT administrators. The temptation to delay updates grows stronger each time a patch introduces bugs instead of fixing them. It’s no wonder automation is rising in popularity. Solutions like Tines that automate patch management are being welcomed not only for efficiency but for sanity.

Ultimately, while Microsoft continues to deliver fixes, the growing cadence of Outlook-related issues casts a shadow on its enterprise readiness. It’s a wake-up call—not just for Microsoft, but for any large-scale organization relying on traditional email clients in modern hybrid infrastructures.

🔍 Fact Checker Results:

✅ Confirmed: Outlook crashes when opening or composing emails post-Version 2504.
✅ Microsoft issued a temporary fix involving FORMS2 folder creation.
✅ Additional flickering bug reported in shared folders since Version 2505.

📊 Prediction:

With growing frustration over Outlook instability, especially in enterprise and VDI settings, Microsoft may accelerate the deprecation of classic Outlook in favor of its new web-first client. Meanwhile, organizations will increasingly invest in automated patching tools to mitigate the fallout of version-related disruptions. Expect greater scrutiny over future Outlook builds as enterprises demand higher reliability and transparency.

References:

Reported By: www.bleepingcomputer.com
Extra Source Hub:
https://www.linkedin.com
Wikipedia
OpenAi & Undercode AI

Image Source:

Unsplash
Undercode AI DI v2

Join Our Cyber World:

💬 Whatsapp | 💬 Telegram