If the error persists, a previous FTK Imager instance may have left a locked driver.
This error effectively renders the software useless for forensic acquisition. But don't panic. This is a common issue, usually related to Windows security permissions, outdated drivers, or service conflicts. ftk imager could not start driver new
Starting a kernel driver requires . If you are running FTK Imager as a standard user, Windows will refuse to start the driver, generating this error. If the error persists, a previous FTK Imager
: The FTK Imager.exe or its associated .sys driver files may be corrupted. A fresh reinstall from the Exterro Download Page often resolves this. This is a common issue, usually related to
If you disabled driver signature enforcement or Memory Integrity just to run FTK Imager, you will have to repeat those steps after each reboot. That is burdensome. Here is the permanent professional solution:
A: This likely distinguishes the newer 64-bit, digitally-signed driver from the legacy 32-bit driver used in ancient versions (e.g., FTK Imager 2.x). The "(new)" driver uses updated kernel APIs.