This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
If two (or more) instances of Excel are open, and one of them has the focus, when hovering the second one, scrolling is still applied to the first one. We need to steal focus from the first window of Excel and then scroll the second.
This seems like a bug and can be reproduced easily (more easily with two monitors).
Lets say you have two windows of Excel open : A and B.
You're working on A but you need to read B. hover your mouse over Excel B, scroll... the scrolling occurs in A ! You must click on B, scroll, then return on A.
Now, with focus on A, open another application (let's say Word), and, of course, set the focus to the newly open app. Be sure to see Excel A and B. Hover your mouse over B, scroll... Scrolling still happens on A.
This does not happen with Word or Outlook. If you open 2 windows of Word, the scroll occurs in the one that is hovered, as expected.
I don't think there's a solution, this is a bug and should be adressed by Microsoft.
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
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.
Fixed in insider build 17040. Now we just have to wait for it to be passed into the main release.
See the link below:
Definitely a problem with Excel/Windows 10. Such a useful feature, maybe I'll have to start using another spreadsheet app in the meantime. <sigh>
So we must still wait.. and wait...
==> I think situation is even worse. In first step the moderator must decide to inform a problem to the design groups. When I read the Moderator comment dated 20 February, I am not sure this first step is passed/done. The Moderator in the problem around 1 Excel window clearly said, I think 1.5 months after the problem was first reported on 1. November, not yet informed to Microsoft, because still checking for ..... (but he asked at least some specific checks - not so the moderator in this thread)
This thread problem was reported 19 February and by Windows 10 update around 28. October situation got worse (this means an additional problem was introduced instead of understanding and solving this thread problem and I believe all 3 problems are interrelated, this means understanding and correcting 1 problem will help strongly to correct the other 2 problems).
In a German speaking thread on this site the moderator said he has informed Microsoft and first feedback was to check if problem disappears when logging in as another/a fresh user.
All this shows, that Microsoft has not yet really understood that something is not only bad, but getting worse. And even when they now start to understand, the number of problems shows Microsoft has some greater problem in the Windows 10 module that manages all the different windows which will surely need stronger effort and time to correct.
So we must still wait.. and wait... and wait for Microsoft to repair the bug in Excel or Windows10.
Sad and disappointing story.
Is this 'trick' not working in 2010?
==> Correct, renaming the Excel 2010 exe-file results in error missing MSVCR90.dll
(Excel 2010 opens only when the exe-file is named EXCEL)