A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
My version is Excel 2016 MSO (Version 2207 Build 16.0.15427.20166) 32-bit
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Win 10 version 21H2 Build 19044.1706
Excel 2016 Version 2204 Build 15128.20224
This problem occurs randomly and with only a few cells being copied. The spreadsheet locks up and the only way out is Save>Close and open the book again. Sometimes that doesn't work and I have to close Excel completely.
Sometimes the top ribbon completely greys out and I can't do anything.
This is becoming a significant problem.
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.
My version is Excel 2016 MSO (Version 2207 Build 16.0.15427.20166) 32-bit
I can hereby confirm that this glitch happens with the desktop version as well ;) The good news is that upgrading to the 2007 version seems to work and sorts this unpleasant issue out.
I already had these 2 directories. They basically contain a couple of desktop.ini files and nothing else.
Has anyone tried the solution I posted 10th August? If so, does it work?
Simply add these two directories to your system:
C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\Desktop
I already had one of them. The original poster then sugested removing them but I haven't and the problem has gone.
Since I created this thread on 18th May we have seen that this problem doesn't care what configuration you are running, or what operating system, or what version of Excel, or whether you use PowerShell, or whatever.
I am running Excel Pro 2016 standalone on a Win 10 PC. I have been running spreadsheet programs from all providers (Borland, Lotus, VisiCalc, IBM, . . .) since the early 70s so I think I have a bit of expertise and experience. Since Windows 3.11 I have never come across such an egregious problem as this.
Does anyone know how to escalate a problem in Microsoft??