On November 11, IT Home gleaned from a BornCity blog post that certain Windows 11 users have encountered a problematic scenario: when utilizing the classic iteration of Microsoft Outlook, index files (Windows.db) undergo complete reconstruction multiple times daily. This leads to a sharp spike in CPU utilization and a dramatic surge in SSD write volumes, subsequently impacting system performance and potentially truncating hardware longevity. Users can verify this issue by observing the Windows.db file situated on the system disk (path: C:ProgramDataMicrosoftSearchDataApplicationsWindows). Typically, this file hovers around 3.5GB in size; however, due to the bug, it can balloon to between 5.5GB and 9.5GB before reverting to its normal dimensions. This anomaly typically manifests within ten minutes post-system restart or shortly after initiating the classic version of Outlook. It can also be triggered even in the absence of file modifications and after the completion of indexing tasks. Initially reported to Microsoft's official Q&A forum in September 2025, a moderator acknowledged it as a bug. From October 20 to 28, the bug seemed to vanish, coinciding with the monthly updates for Windows 11 and Microsoft 365. Observers speculated that Microsoft had covertly rectified the issue; however, it resurfaced on October 29 and has persisted ever since. Despite multiple user reports, no effective official response has been forthcoming. Although the bug does not precipitate system crashes or functional impairments, the elevated CPU load escalates device power consumption, while the continuous SSD writing expedites flash memory particle degradation, thereby curtailing the hard drive's lifespan. Given Microsoft's intention to sustain support for the classic version of Outlook until 2029, the magnitude and duration of this issue's ramifications should not be trivialized.