Skip to main content

High CPU usage when reconnecting an RDP session to a machine previously locked using kapowlock


Question / Problem: 

On a machine where Desktop Automation Service (DAS) is installed is possible to terminate an RDP session and lock the machine using kapowlock (i.e. the "Lock Screen" option from the system tray icon menu of DAS).

In some cases, when the RDP is connected back afterwards it will need a long time to establish connection and also high CPU usage can be observed.

Answer / Solution: 

This is a behavior that affects environments that use:

  • Windows 10 machines with AVC444 support enabled (i.e. Windows 10 version 1511 and later)
  • Kofax Kapow/RPA version 10.3.2.x and later (because in these versions kapowlock is based on FreeRDP who is affected by AVC444 support). See KB 3020180 for more details.

The solution to the high CPU usage is to install Microsoft  KB4522355.


Applies to:  

Product Version
RPA 10.3.2.x and Later