Here's the paths to the files being accessed by TaskbarX and the COM Surrogate, respectively:Ĭ:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\Office16\MSO.DLLĬ:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\MSO.DLL The laptop's internal screen is a 4K screen, if that matters. Curiously, the disk usage drops by about half if I disconnect the external monitor. I'm running Windows 10 version 2004 on a Dell XPS 15 9500. The portable version was actually slightly worse and was reading from disk at about 5 MB/s.
I tried the free portable version of TaskbarX as well and it exhibits the same behavior. I am running TaskbarX version 1.6.1.0 from the Microsoft Store. This disk usage occurs regardless of if any Microsoft Office apps are running (or any apps at all). In addition, on my other laptop the TaskbarX process does not have an associated COM Surrogate as far as I can tell. It's mostly the COM Surrogate accessing the DLL but TaskbarX.exe is doing it as well to a lesser extent. I can't imagine why TaskbarX would need to access an Office DLL at all, let alone at 2-3 MB/s constantly. As far as I can tell, MSO.DLL is only used by Microsoft Office. TaskbarX.exe and its associated COM Surrogate (dllhost.exe) are constantly reading from MSO.DLL at ~2-3 MB/s (see Task Manager and Resource Monitor screenshots). TaskbarX is running and functioning as expected except for its disk usage. I'm not sure if this is actually a bug or expected behavior but this does not happen on my other laptop running TaskbarX.
0 kommentar(er)
