While analyzing Talos xperf data, jmaher noticed that dwrite.dll would intermittently appear in the logs for main thread I/O during startup. Given that we spin up a separate thread to load this DLL, my suspicion is that when this problem happens, the background thread's priority is so low that it is starved, loses the race with the main thread, and dwrite.dll ends up being loaded out of necessity by the main thread anyway. I have no proof to confirm this theory.