Some applications may use dynamically loaded DLLs, which could potentially issue calls to static DLLs before the application ...

Some applications may use dynamically loaded DLLs, which could potentially issue calls to static DLLs before the application is ready. This compatibility fix provides a workaround for this behavior by preloading the required static DLLs for the application. This compatibility fix takes a command line containing a list of the DLLs affected. They will be loaded in the order of the command line listing. This compatibility fix is similar to DelayDllInit, which works with statically loaded DLLs.

Some applications may call the ole32!OleUnitialize function in their DllMain. This worked on Windows 2000, but is no longer ... Some applications may expect the DirectPlay devices to be enumerated in a specific order. This compatibility fix enables ... Some applications may have difficulty adjusting to the differences in folder structure between Windows 9x and Windows XP. ... Some applications may lose focus and are unable to regain it due to Windows XP window manager changes. This compatibility ... Some applications may use dynamically loaded DLLs, which could potentially issue calls to static DLLs before the application ... Some applications may use static DLLs, which could potentially issue calls to APIs before the application is ready. This ... Some applications obtain the shell desktop folder and invoke the Release() method too many times, resulting in the object ... Some applications perform non-standard admin checks such as calling GetTokenInformation to retrieve TokenGroups then compare ... Some applications read the process performance data registry value to determine if they are the only instance of the application ...