Using the Microsoft C Runtime with User-Mode Drivers and Desktop Apps
[This topic applies only to desktop drivers and not universal drivers.]
This topic provides information about distributing the C Runtime Libraries with applications and drivers for Windows 8 and Windows 8.1. It provides guidelines for user-mode driver and desktop application writers to compile their code, and package it for redistribution with the necessary C Runtime libraries.
The C runtime libraries (CRT) are no longer shipped as a Windows shared component
In the past, Microsoft distributed the C runtime libraries (CRT) as a Window shared system component. In previous versions of the WDK, you could link your code with the Windows System version of the CRT when you built your driver or traditional Windows app. With the release of Windows 8, the C Runtime libraries are no longer considered a system component, and you must ship a redistributable version of the CRT with your user-mode driver or desktop application. This topic discusses the reasons for this change, the new components of the C Runtime, and strategies for building your desktop app or driver and redistributing the CRT.
Why did Microsoft make this change?
There are now two separate versions of the C Runtime. One is an internal Windows component, and the other is for use by application and driver developers and ships with Visual Studio. The primary reasons for this change are for consistency and to support servicing of the CRT for customers.
In the past, applications were sometimes linked to versions of the CRT on computers that did not have the correct versions of the CRT DLL installed. Using a common public version of the CRT will help eliminate this problem.
In addition, servicing the CRT can be complex. The Visual C team plans to ship periodic updates of the CRT included with Visual Studio. By using the recommended redistribution strategies, you can easily pick up these changes for your application. Also, you will not have to worry about a change in the Windows System version of the CRT breaking your application.
The msvcrt.dll is now a system component owned and built by Windows. It is intended for use only by system-level components. The files msvcr110.dll (Visual Studio 2012) or msvcr120.dll (Microsoft Visual Studio 2013) are the new public versions of the CRT and are for use by Desktop application and user-mode driver developers.
Building your code with the C runtime
Visual C++ installs the latest version of the CRT in the System32 directory on a development system. This is installed as a convenience for the developer. Otherwise, all projects that are built with Visual C++ that link with the shared CRT require a copy of the DLL in the build directory for debugging and execution. The msvcr120.dll can be used for drivers that target Windows 8.1 and Windows 8 and previous versions of Windows (starting with Windows Vista).
Redistributing the C Runtime
When you build a user-mode driver or traditional Desktop application in Microsoft Visual Studio, and the application uses the C run-time libraries (CRT), you must distribute the appropriate CRT dynamic-link libraries.
The recommended strategy for redistributing the CRT depends on the type of application or driver you are building. For Windows 8 and Windows 8.1, Microsoft provides a Visual C++ Redistributable Package (VCRedist_x86.exe, VCRedist_x64.exe, VCRedist_arm.exe) that is included with Visual Studio. Developers can chain the redistributable package in with their other binaries. If you use the redistributable package, the C/C++ Runtime can be serviced on the customer's computer automatically. If you want to achieve isolation, you can either link statically, or copy the specific Visual C/C++ DLLs to the application local folder along with their other binaries. An application local folder is a folder that contains an executable application file. DLLs must be deployed to the application local folder.
The Visual C/C++ Redistributable Package (VCRedist_*.exe ) is serviced as an application. If your installation includes the redistributable package, the latest version is installed in System32 upon initial setup, and updates are enabled using the Microsoft Update service, as a complete package. All components of the Visual C/C++ Redistributable Package are updated as a single unit.
If you copied individual CRT components to System32, without using redistributable package, these would not be serviced automatically, and may be overwritten accidentally.
A potential problem exists if a driver copies CRT components to System32 and another program runs the redistributable package, the version installed by the driver will be overwritten. The opposite case is also a potential problem. If a program ran redistributable package and a driver copies an earlier version of CRT components into System32, this might break the application. The INF installation process simply checks the version number of the library to install against the one already in System32, and overwrites it if they are different.
Use the following strategies when redistributing the C/C++ run time components with your drivers and applications.
For applications installed under Program Files:
- Use the Visual C++ Redistributable Package (VCRedist_x86.exe, VCRedist_x64.exe, VCRedist_arm.exe), which deploys the CRT under System32. In this case, the redistributable package can be updated automatically.
- Alternatively, install the DLL(s) to the application local directory (copied directly to the directory where the application is installed), or link statically to the CRT. In this case, the CRT would need to be serviced manually.
For printer drivers:
- These drivers should include the required CRT files in the INF, so the CRT files are copied to the driver store as part of the driver payload.
- V4 print drivers cannot use a co-installer for setup, so the INF must copy relevant binaries of the C/C++ runtime library to the driver store. To do this, you should reference the appropriate files in the [COPY_FILES] section of the driver package.
- V3 print drivers should not use co-installers for setup, as they are not run during Point and Print connections. These drivers should reference the appropriate files in the [COPY_FILES] section of the driver package.
The following is an example of how to include the CRT binaries in the [COPY_FILES] section of an INF:
For UMDF drivers:
- Statically link your driver against the CRT to include the runtime in the binary. In this case, you do not need to redistribute the CRT.
Linking your code with the C Runtime libraries
The following libraries contain the C run-time library functions.
Debug version of C runtime. No redistribution allowed.
Debug version of C++ runtime. No redistribution allowed.
To determine which DLLs you must redistribute with your application, you should collect a list of the DLLs that your application depends on. One way to collect the list is to run Dependency Walker (depends.exe).
When you have the list of dependencies, compare it to the list of files described in Redistributable Code for Visual Studio 2013 Preview and Visual Studio 2013 SDK Preview. For more information, see Determining Which DLLs to Redistribute and Choosing a Deployment Method.
You cannot redistribute all of the files that are included in Visual Studio; you are only permitted to redistribute the files that are specified in Redistributable Code for Visual Studio 2013 Preview and Visual Studio 2013 SDK Preview. Debug versions of applications and the various Visual C++ dynamic-link libraries are not redistributable.
Summary - What you need to do
Use the Visual C++ Redistributable Package (VCRedist_x86.exe, VCRedist_x64.exe, VCRedist_arm.exe)VCRedist.msi as part of your installation process, if at all possible.
For printer drivers, use desktop application local deployment of the CRT to the driver store.
For UMDF drivers, use static linking of the CRT with your driver code.
- Determining Which DLLs to Redistribute
- Redistributable Code for Visual Studio 2013 Preview and Visual Studio 2013 SDK Preview
- Choosing a Deployment Method