CryptoPrevent v7.4.20 & On-Screen Keyboard

These forums are retired and read-only.
Forum rules
These forums are retired and read-only.
For support, please visit

CryptoPrevent v7.4.20 & On-Screen Keyboard

Postby UsernameIssues » Sun May 31, 2015 5:18 pm

According to Nick's post:

...CryptoPrevent doesn't block anything in %windir%\system32...

edit: so, it does no good to white list the exes involved.
Maybe there are exes or temporary files that I'm not seeing.

Turning on the BETA Filter Module causes a UAC\consent prompt when attempting to start Windows 7's On-Screen Keyboard. Clicking on Yes to that UAC prompt sends the computer into a rapid loop of opening/closing more UAC\consent prompts. Resetting (or remotely restarting) the computer seems to be the only way out.

Any ideas on how to allow Windows 7's native On-Screen Keyboard to open?

Launching osk.exe seems to involve an elevation of rights. It seems to be launched several times before the final process opens. Normally, the user does not see a UAC prompt when starting osk. In this test case, the user has admin rights.

CP.png (39.14 KiB) Viewed 2745 times

BETA Filter Module OFF
PE.PNG (6.92 KiB) Viewed 2745 times

BETA Filter Module ON
PM.PNG (76.99 KiB) Viewed 2745 times

The image above only shows a tiny part of the loop that the computer gets stuck in.

I failed to find the command line syntax needed to have utilman start osk.

Thanks in advance for any input on getting osk working with BETA Filter Module turned ON.
Posts: 1
Joined: Sun May 31, 2015 3:40 pm

Return to CryptoPrevent for Home Users