keystroke encryption software and veracrypt

[Joris Hoven]

I use keystroke encryption software. Lately i've had to disable my keystroke encryption software because i can't open an encrypted container file with the password. If i disable the keystroke encryption software, then i can log in with the password of a container file? What is going on here? A month ago it all still worked with the keystroke encryption software enabled.

[Enigma2Illusion]

A month ago it all still worked with the keystroke encryption software enabled.

Are you still using the same version of VeraCrypt from a month ago?

If yes, then you should post your question on the vendor's support forum for the keystroke encryption software.

If no, then which version of VeraCrypt and which version of the OS platform?

[Joris Hoven]

I recently installed the latest version 1.26.7. Previously i used an older version. With the latter i had no problems with keystroke encryption software.

[Enigma2Illusion]

This could be the result of either the Memory Protection feature which can be disabled or the process mitigation policy which cannot be disabled.

In VeraCrypt, you can enable the option of Secure Desktop in Settings > Preferences which helps protect against input and output spoofing by presenting the credentials dialog box in a protected section of memory that is accessible only by trusted system processes.

Source:
https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-account-control-switch-to-the-secure-desktop-when-prompting-for-elevation

Process Mitigation Policy

Per the Release Notes:

Add process mitigation policy to prevent VeraCrypt from being injected by other processes

Detailed explanation:

The process mitigation policy (not to be confused with memory protection) was indeed introduced to enhance security by preventing unauthorized code injections into the VeraCrypt process.
While WindowBlinds is a legitimate software aiming to customize the appearance of the Windows UI, from a strictly technical perspective, its method of applying themes involves process injection. In the eyes of VeraCrypt's mitigation policies, it's indistinguishable from malicious attempts at code injection.
To maintain the security of VeraCrypt, I've made a deliberate choice not to allow exceptions or provide a method to disable the process mitigation policy. I understand this may impact the visual consistency of your OS interface, but I hope you recognize that this decision stems from the necessity of maintaining the highest level of security for VeraCrypt users.

Source:
https://sourceforge.net/p/veracrypt/discussion/general/thread/263a8d11aa/?page=3&limit=25#3084