Hello Thao (and anyone at Microsoft reading this),
I appreciate the new link, and did go out to view it, but the way the post reads, I should have already gotten that update through Windows Update (I am current when I check for updates). I did look to see if there was any way to tell if I already had the
update, but the only thing I found about a DisplayLink driver was for Office 2013, and the file listed for verification (dlumd32.dll) does not exist in either my System32 or SysWOW64 directories. I also was not experiencing the specific issues cited in the
post, and reading the DisplayLink web page, this appears to be a USB display driver, and I am using an ASUS widescreen display connected to an NVIDIA card. Add Michael's experience trying the new driver, and I would rather wait for Microsoft to figure this
out. Michael's experience with this bug seems to parallel mine, unlike several other issues in this thread, so I'm not comfortable with introducing another change that may not be necessary. If you can tell me how to determine if the driver I need has already
been updated by Windows Update, please let me know.
Let me add a little more information to help any true troubleshooters who may read this.
- The problem does not appear to be dependent on the file extension. I get the same issue with an xls, xlsx, or xlsm file.
- If I launch Excel to create a new file, then minimize the display prior to doing anything else, the splash screen is there - before Excel knows what type of file it will be. However, if you perform a "Save as", the splash screen will go away because any
secondary dialog in Excel clears the splash screen as I have documented in an earlier post. This is really just a confirmation of my first point that the extension is not the factor.
- I noticed that if I launch a file which was created by an earlier version of Excel, I do not experience the problem. This is the case for earlier version files with or without formulae to be recalculated. This tells me that something in the "previous
version check" code is either bypassing the problem code or ensuring a proper branch is taken down the road.
I hope someone is reading this who can actually get it to a diagnostician. Michael and I have made significant efforts to provide details of the issue and have tested numerous attempts to isolate the problem. Thanks to all who are trying to help.
Jack