By default installation and deinstallation of CBFS Direct files (kernel-mode drivers) can be performed from the user account which belongs to Administrators group. This is a security measure of Windows operating system. You can change this behaviour on the target system by adjusting the list of users and groups who have the right to install and uninstall the drivers. This can be done in Control Panel -> Administrative tools -> Local Security Settings -> Local Policies \ User Rights Assignment (tree branch), there you need to change "Load and Unload device drivers" item. No need to say that by default, you can change the security settings if you are system administrator.
Notes for Vista and later versions of Windows
If you have UAC (User Account Control) enabled, Vista and later versions of Windows will run applications started by you with limited rights even when you are logged in as administrator or m7ember of Administrators group.
If you install or uninstall the drivers by calling the above mentioned functions in your code, you need to elevate privileges of your application so that it's started with truly administrative rights.
To elevate privilages for your application, you must start it with Run As Administrator option. In Windows Explorer this is done using Run As Administrator command in context menu for the application. Alternatively you can set the corresponding option in the Properties window shown for your executable module.
One more option is to use the manifest.
The manifest file can be placed next to the executable of your application or embedded into the executable.
If you decide to keep the manifest in a separate file, it must be named <EXEName_with_extension>.manifest, eg.
for MyApp.exe the manifest should be called MyApp.exe.manifest.
You can use the following manifest:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<description>elevate execution level</description>
<requestedExecutionLevel level="requireAdministrator" uiAccess="false"/>
The driver to be deployed is rawdsk3.sys. Note, that the drivers are different for Win32, x64 (AMD 64-bit architecture) and IA64 (Itamium 64-bit architecture) platforms.
The debug versions of the drivers are located in "<CBFSDirect>\Drivers\Debug\32bit" or "<CBFSDirect>\Drivers\Debug\64bit" folders (for Win32 and Win64 platforms). The debug version should be used only during development of your application. It creates a log file on disk C:. If the driver is loaded and "chkdsk c:" is scheduled for boot time, the log file will prevent the disk from being checked. This is not a bug, but specifics of the debug version of the driver.
The release version of the driver is located in "<CBFSDirect>\Drivers\Release\32bit" or "<CBFSDirect>\Drivers\Release\64bit" folders (for Win32 and Win64 platforms). You can use the release version of the driver for both development and final deployment.
64-bit version of the driver is available for x64 (AMD64) processor architecture used by most modern 64-bit processors and IA64 (Itanium) processor architecture used by some Intel-produced server processors.
Installation of the drivers to the target system is described here.