Selecting a cell in Excel goes to an incorrect cell

Chris,

Tom and I are having the issue. There is nothing custom about the spreadsheets and yes I am using it locally.

To get it reproduce the problem:

1. open a blank workspace (spreadsheet)
2. click on View
3. click on page layout
4. add data anywhere
5. click FILE-PRINT
6. change the margins to something else
7. set "No scaling" to "Fit all columns on page"
8. go back to the spread sheet and add a full page of data so the screen scrolls.
9. add header/footer information
10. copy entire lines and "insert" them.
11. add header/footer information

At this point, if you click on the edge of a cell instead of the center, it will select a cell at the very top. Then if you select a cell somewhere else, the cell highlighted will be offset.

WORK AROUND:

Add another sheet to the workspace and then randomly click in the cells a few times. When you go back to the original workspace, it seems to correct itself.

So consequently, when I'm working on a large spreadsheet, I have to add another blank sheet to occasionally switch to in order to remedy the issue.

This is a very annoying problem and it only happens on office 365 version of excel.

I hope this helps to narrow down the issue

Chris, I don't seem to have the option to send feedback from Excel.

To answer your questions, yes, desktop version only. No add-ins I'm aware of and no customisations. I'm using normal view.

I note the new info added (thanks, Joshua); my workaround is often to scroll the page dramatically, quickly and widely up and down a few times, this sometimes works. This morning I was on a call and the offset using the small laptop screen meant I couldn't easily communicate what I needed to; it's a massive problem and has been for nearly a year for me. My local IT team provided me a different laptop and the is, if anything, worse. Plus it's Win 11 with far more issues and bugs than my Win 10 machine, and the touchpad has its own jumping cursor issue (known issue for nearly two decades) - so it's a miserable and genuinely stressful experience when working on anything important.

There seem a lot of users with the issue, just by making general internet searches.

I hope this can finally be resolved soon.

Thanks,

Tom

Hello Tom,

I was able to find your original feedback. At the time you submitted it, you were running the Feb 2023 update (16227.20318).

Are you still on that version, or have you been able to install a new update? The Oct 2023 version is available and Nov is in the process of rolling out.

One other question: You're not running Excel in a virtual environment, like remote desktop, are you?

Thanks,

Chris

Hi Chris,

This is an employer issued device and they handle all updates. I imagine we've had numerous updates since then, certainly I see Windows behaviour changing on a continual basis. As mentioned, we've tried different laptops and Windows O/S versions, we've also tried changing the build within O/S version. I'm not using anything like remote desktop, it's a very basic, simple setup.

There are dozens of cases on your own forums and other forums, so it I hope it will be possible to replicate your side. I'm not the only one in my organisation to encounter it but not everyone reports such things.

Note: this issue occurred very suddenly, out of the blue. So for me, that would be about a year ago. So perhaps it is possible to evaluate the changes made to Windows versions at that time and narrow down from there?

Please keep trying, and thanks for your assistance -

Tom

Tom,

Just curious, when excel starts "acting up" as I like to call it, are you in PAGE LAYOUT mode? I have also notice if I scroll down and then back up, the header is only partially shown. I have to click in the header to make it visible.

Also when it starts acting up, open a new sheet in the current work book and click in the blank cells randomly a few times. When you go back to the original sheet, does it temporarily correct it?

I'm going to do some more testing on my end to see if I can narrow it down to a particular instance to see if it will help Chris and Microsoft figure it out.