Microsoft has a bug on its hands, and the company's response suggests it isn't taking it seriously enough. A user recently documented a maddening issue: resizing a column in Excel automatically changes the zoom level, and after that, you cannot select any columns on the sheet until you click away and back. The only workaround, switching sheets and manually restoring the zoom, is a productivity killer, not a solution. Microsoft's official reply to a related query offered generic troubleshooting steps that ignore the pattern of reports, treating it as an isolated incident rather than a systemic problem introduced by recent updates.
This matters because Excel is the backbone of countless workflows. For anyone who regularly adjusts column widths, data analysts, financial modelers, project managers, this bug doesn't just annoy; it breaks flow. The user tried to write a macro to preserve the zoom level by hooking into workbook events like `Workbook_SheetSelectionChange` and `Workbook_WindowResize`. But resizing a column doesn't trigger any of those events. Even if the zoom could be saved, the inability to select columns after a resize means the worksheet is effectively locked until you navigate away and back. That is not a minor glitch. It is a fundamental breakdown of spreadsheet interaction.
The core problem is not just the zoom change. It's that a routine action, dragging a column boundary, cascades into two separate failures: the zoom resets to an unintended level, and the sheet becomes partially unresponsive. Microsoft's silence on the scope of the issue leaves users to fend for themselves, stitching together macros that can't even target the right event. The community's best hope is that enough people report it to force a fix. Until then, the only reliable mitigation is to avoid resizing columns, which is impractical for anyone doing real work.
Our take is plain: Microsoft should acknowledge this bug publicly and prioritize a patch. The behavior did not exist before recent updates, and the growing number of reports makes it clear this is not a corrupt workbook or user error. For now, users are left with a spreadsheet that punishes them for adjusting layout. That is not acceptable from a tool that defines modern data work.