Using classic Outlook for Windows in business environments
Nope. Mine is still exactly the same
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The vertical scroll bar on the far right of my Outlook.com window keeps jumping to the bottom of the screen whenever I click on one of my folders or an email. Then I can't see the ribbon above my emails. I push the scroll bar back to the top, but as soon as I click on a folder again, it jumps back to the bottom of the screen. It happens whether my zoom is at 100% or higher. I tried the repair option and restarting. I contacted Outlook Support and after 40 minutes, they said it's how Outlook is designed and can't be fixed. But it wasn't always this way and just started jumping. I see there was a related issue that was fixed in Feb 2025: https://answers.microsoft.com/en-us/outlook_com/forum/all/issue-with-the-inbox-scrolling-bar/ce34dda6-7f02-4222-8c44-62b2d2ea485d
I am using a laptop. The issue is present in Chrome and Edge.
Using classic Outlook for Windows in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Nope. Mine is still exactly the same
I have been using a mouse on my chromebook. I disconnected the mouse, rebooted - the issue still exists.
Thinking out loud - is this scrolling issue related to the Outlook version that has ads. Are those that have the Outlook without ads having the same issue?
It is reproducible. Two of us in this chat can reproduce it by opening a message or a folder. That's the experience of the OP, and it's my experience.
Helpful reply at a curiosity level. I wish we would get some MS help at an operational level. Anyway, thanks.
I too am having this trouble. My best guess is that an occasional mouse-scroll signal is being sent to some process which *isn't* supposed to be receiving these signals (because it's not the owner of the currently active window). Closing all other windows seems to be a workaround but I'm not sure it's 100%. Rebooting the OS also seems to be sufficient but the problem arises again.
My best guess is that on *my* platform, the scroll-signalling issue started with an installation on the 12th of June of "2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems". The update record links to June 10, 2025—KB5060842 (OS Build 26100.4349): https://support.microsoft.com/en-us/topic/june-10-2025-kb5060842-os-build-26100-4349-47ff300b-2a04-440c-9476-2860d04fce8d
Microsoft Update currently informs me of what is *probably* a later version of "2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems". Searching online, I found an MS website which helpfully provides a catalog. Quite possibly what's on offer to me is an 11th of June out-of-band versioning of this update:
However this update is offered to me without a link (or even a KB number) to inform me of what I would be agreeing to "Download & Install", if I dared to click on that affordance! And the 11th June version was apparently released to fix some fatal problem with some other app causing Windows to restart. Its file listing (in CSV format) has a bazillion dlls... so I guess it might resolve my mouse-scroll issue.
My best guess is that this update is mucking around in what we used to call "DLL hell".
If so, then things could get easily worse rather than better if I try installing the 11th June version of the 2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based systems! So... I think I'll wait a few more days for more folks to do the alpha-testing on the current version of this update. Early reports are sour, and furthermore others have been complaining of mouse-scrolling issues for months on *their* Windows installation. As always, YMMV. There are bazillions of different constellations of drivers, and of versions of apps, in our Windows installations... I'm sure glad I'm not working QA in Windows, I'd surely go crazy trying to build and maintain a test suite with reasonable coverage of these!