Those that never turned on “Hey, Cortana” (which is an awesome feature, btw) have never experienced this problem, hence why the issue exists for some and not others. This issue only exists for Excel and none of the other Office applications. I’ve yet to figure out why this is, but if you turn on the “Hey, Cortana” voice command feature after installing or upgrading to Windows 10, it bogs down Excel file execution. Why would the experience differ between Windows 10 users? And, that seems to eliminate an Excel issue and put the blame squarely on Windows 10, or at least a component of Windows 10. To further confound the wise, the issue doesn’t exist for everyone. So, it would seem that it’s an Excel issue, right? To make matters more confusing, if you open Excel first (which opens quickly on its own) and then open the file, the file opens blazingly fast. It doesn’t matter if the file is sitting in the Cloud, on a network share, or even locally – it just takes forever to load, even if the file contains no data. Running either Office 2013 or the latest Office 2016, when opening an Excel file from the file system, it takes close to 20 seconds for the file to open completely. I chalk it up to an errant bug Microsoft missed. The solution is a simple one, but makes absolutely no sense. Last night I had had enough and spent a good hour developing a solution. This is one of the issues that has plagued me since upgrading my systems to Windows 10, but due to a busy travel schedule and other miscellaneous work items, I just delayed digging in to figure out a solution.
0 Comments
Leave a Reply. |