Forum Discussion
Excel not working properly since updating to Windows 11
I managed to get rid of the issue by going to - Options/Advanced/Display/ and tick the 'Disable hardware graphics acceleration'. Excel seems to be working as normal now with it disabled, it was unusable before, slow and unresponsive and it didn't register where the cursor was on the screen.
- PDAmanJul 05, 2022Copper ContributorIt appears that that option was removed from all office apps last year. So your 365 must not have been updated for some time?
- davidlaughterJul 05, 2022Copper ContributorPDAman, not sure where you are getting your information, but i am running the latest version at Microsoft® Excel® for Microsoft 365 MSO (Version 2205 Build 16.0.15225.20278) 64-bit. I even just hit "update now" on the account page, and it reports back i am running the latest version.
- PDAmanJul 05, 2022Copper Contributor
I have the exact same version and I do not see the 'display hardware acceleration option under display in any of the office apps!
https://www.msoutlook.info/question/disable-hardware-graphics-acceleration
https://www.mrexcel.com/board/threads/cannot-find-option-to-disable-hardware-acceleration.1178466/My graphics driver is NVidia. So my guess is that Office recognized my graphics driver as not in the problem list and removed that option meaning that it is always on.
For graphic drivers that are not yet in the cleared list, that option is still alive so that the user can see it and disable it if needed.
In my case, the problem started from day 1, and I am guessing that the hardware accelation was on by default and there was no option to disable it.
However, I tried the regedit method just now:
https://www.msoutlook.info/question/disable-hardware-graphics-acceleration
I had to create the Graphics folder and set the value to 1.
I am hoping that this is the way that can disable hardware acceleration for Excel.
I will report back if this fixed it
UPDATE:
Unfortunately, adding the registry hack to disable hardware acceleration did not work at all. I am still looking for solutions.