Could not write to \system32\drivers" while installing Interception driver - Secure Boot & Admin Issues #214
Description
Hi everyone,
I've been trying to install the Interception driver for AutoHotInterception (AHI) for the past 5 hours, but I'm stuck at the final step. Here is the technical breakdown:
The Error: Running install-interception.exe /install returns: "Could not write to \system32\drivers".
The Missing File: I've discovered that interception.sys is missing from my local folders. Even when I try to download it and manually move it to the drivers folder, Windows denies access.
Secure Boot: I suspect Secure Boot might be the culprit, but I need to know if disabling it is mandatory for this driver to write to the kernel.
Antivirus/Permissions: My Windows Security says "Managed by your organization," which prevents me from fully disabling real-time protection. I am running PowerShell as Administrator, but still getting "Access Denied" or "Could not write" errors.
Test Mode: testsigning on is already enabled and I have restarted my machine.
My Question: Has anyone encountered this "Could not write" error specifically because of Secure Boot or "Organization Managed" group policies? How can I force-copy interception.sys into the drivers folder or bypass this write restriction?
Yesterday, the Monitor.ahk was working correctly and showing the full device list with IDs (as seen in the documentation). However, today it only opens as a small window showing debug code/line numbers, and the device list is completely missing. This happened after the driver seemingly stopped responding, and now the installer keeps giving the 'Could not write' error. It feels like the driver was partially working but now the system is completely blocking it.
