Install the application, ensuring you grant administrative permissions during setup.
Starting a driver requires SeLoadDriverPrivilege , which is only granted to administrative accounts. Even if you are logged in as an admin, UAC may still restrict the process token. Running as administrator explicitly elevates.
If running from a USB drive, ensure all required Microsoft Visual C++ Redistributable files (specifically mfc100.dll , mfc110.dll , etc.) are copied into the same folder as the executable. ftk imager could not start driver new
This disables a critical security feature. Use only for testing. If FTK Imager works, you have identified signature enforcement as the root cause. See Solution 6 for a permanent fix.
: Low-level device access requires deep operating system hooks. Running the application in a standard user context prevents the tool from instantiating kernel drivers. Running as administrator explicitly elevates
The application lacks the permission level needed to load or trigger a kernel-level hardware driver.
Even if you are an admin on the machine, FTK Imager requires that explicit elevation to load the kernel driver successfully. Use only for testing
If you previously ran a different version of FTK Imager, an older driver might still be installed but stopped, or pending deletion. This causes conflicts when the new instance tries to start.
If you cannot resolve the driver error and need immediate disk imaging, consider these alternatives that do not rely on problematic kernel drivers: