Try the following methods in order, testing FTK Imager after each.
Check:
Get-SystemDriver -Name ADImagerDriver | fl *
Look for Signer – if missing or "Test Sign", modern Windows blocks load. ftk imager could not start driver
Open Command Prompt as Administrator and run:
sc query FTKDriver
Check if it exists. If not installed:
cd "C:\Program Files\AccessData\FTK Imager\"
FTKDriver.exe -install
Then start it:
sc start FTKDriver
If it fails with an error (e.g., 1275 – driver blocked), check the next steps. Try the following methods in order, testing FTK
For professional forensic work, maintain a dedicated forensic workstation with:
If all else fails, contact AccessData support or migrate to alternative imaging tools like Guymager, Tableau Imager, or DD (via WSL or standalone). Check: Get-SystemDriver -Name ADImagerDriver | fl *
Version Information: This guide applies to FTK Imager 4.x and 7.x on Windows 10 and 11. The error may not appear on Windows 7 or older systems due to relaxed driver signing requirements.
Open Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational Look for Event ID 3033, 3076, 3089 – shows driver blocked due to signature.