I'm building a set of scripts to auto-configure Windows post-installation, and I need to modify certain registry values which seem to be locked by the Windows Defender process.
But the Windows Security UWP app itself can access and modify these values no problem.
Am I unable to modify these entries nor force kill the Defender process because of the Defender Driver that loads at boot?
Without the access to the source code one can only speculate but it could be enforcing extra security checks in the userland code.
All Windows Security processes run under the SYSTEM user as shown by the Task Manager:
But despite being the the nt authority\system user under MinSudo, I am incapable of affecting any Defender entries. I wonder how Group Policy does it, I suppose it writes to a different key.
I'm building a set of scripts to auto-configure Windows post-installation, and I need to modify certain registry values which seem to be locked by the Windows Defender process.
Example:
But the Windows Security UWP app itself can access and modify these values no problem.
Am I unable to modify these entries nor force kill the Defender process because of the Defender Driver that loads at boot?
Without the access to the source code one can only speculate but it could be enforcing extra security checks in the userland code.
All Windows Security processes run under the SYSTEM user as shown by the Task Manager:
But despite being the the
nt authority\system
user under MinSudo, I am incapable of affecting any Defender entries. I wonder how Group Policy does it, I suppose it writes to a different key.