: Open File Explorer and check these two folders:
: Modern Windows (10/11) may block the driver because its signing certificate was revoked or is considered legacy. You can temporarily disable this through the Advanced Startup menu to see if the driver loads successfully. ftk imager could not start driver new
The error "FTK Imager could not start driver new" can be caused by a variety of factors, including outdated drivers, insufficient privileges, and hardware issues. By following the recommended solutions and best practices outlined in this report, users should be able to resolve the error and successfully use FTK Imager to create forensic images. If the issue persists, further assistance from AccessData support or a qualified digital forensics professional may be necessary. : Open File Explorer and check these two
Try performing the capture on a native x86 Windows machine if possible. 3. Address Driver Signature Enforcement By following the recommended solutions and best practices
Modern security deployments heavily rely on and Memory Integrity (part of Core Isolation). These features use virtualization-based security to ensure that only verified, cryptographically secure drivers can execute in the Windows kernel space. If an installed version of FTK Imager uses a legacy driver that does not comply with the strict, modern Microsoft driver signing policies, Windows aggressively blocks it from executing. 2. Missing C++ Dependencies
When FTK Imager flags a driver initialization failure, the bottleneck is almost always a security policy or architecture mismatch within the host Windows operating system. 1. Core Isolation and Memory Integrity (HVCI)
If running as admin fails, Windows is likely blocking the driver’s signature. For a that disables signature enforcement: