Imager Could Not Start Driver New [best] — Ftk

To turn this off later, simply run bcdedit /set testsigning off in an elevated command prompt.

The error "FTK Imager could not start driver" typically occurs when the application lacks the necessary administrative permissions or when Windows security features prevent the kernel-mode driver from loading Quick Solutions Run as Administrator ftk imager could not start driver new

If you have used other forensic tools (like OSFMount or older versions of FTK), they may have left behind a driver named dawidrv or ftkimager that is now conflicting. To turn this off later, simply run bcdedit

Here is how to fix it, ranked from the most likely solution to the least. To turn this off later