Large application/file load-time-Collection of common programming errors

Windows’s memory manager is actually pretty slick — it services memory requests AND acts as the disk cache. With enough free memory on the system, lots of files that have been recently accessed will reside in memory. Until the physical memory is needed, those DLLs will remain in cache — all ala the CacheManager.

As far as how to help, look into Delay Loading your DLLs. The advantages of LoadLibrary only when you need it, but automatic so you don’t have LoadLibrary/GetProcAddress on all of your code. (Well automatic, as far as just needing to add a linker command switch):

http://msdn.microsoft.com/en-us/library/yx9zd12s.aspx

Or you could pre-load like Office and others do (as mentioned above), but I personally hate that — slows down the computer at initial boot up.